Skip to content

📧✨ Beautiful email. For everyone.

README

inlark

Beautiful email. For everyone.

A fast, keyboard-first desktop mail client for the accounts you already own.
JMAP and IMAP, Linux, Windows and macOS. No hosted service, no subscription, no telemetry.

Download · Features · Connect an account · Build from source


inlark's unified inbox, showing conversations from several accounts in one list, each marked with its account colour.

Why inlark?

If you run your own mail server, or just have a few accounts at small providers, your choices are usually an email client that looks like it was designed for Windows XP, one that wants a monthly fee, or one that routes your mail through someone else's cloud. inlark is the fourth option: a calm, modern client that talks straight to your server and then gets out of the way.

  • One inbox for every account. Personal, work and the side project you swear you'll finish all land in one timeline, each marked with its account. Replies go out from the address the message was sent to, so you stop accidentally emailing your landlord from your work address.
  • Your keyboard, first. J/K to move, E to archive, R to reply, / to search, and Ctrl K for everything else. Every action works with a mouse, too.
  • Undo for everything. Archive, trash, move, star or mark as spam, then press Z. It works even if another client changed the mailbox in between.
  • Search that goes all the way back. Searches run on your server across every folder and every year, narrowed by sender, recipient, subject, date or attachment.
  • Big mailboxes stay fast. A quarter of a million conversations in the unified inbox still scroll smoothly, because only the few dozen on screen are ever drawn.
  • Sending you can trust. Drafts survive crashes. If a send's response gets lost on the way back, inlark marks the message unconfirmed and doesn't retry it on its own, so nobody gets your message twice.
  • Private by design. inlark connects directly to your mail server. There's no inlark account, no sync service and no analytics.
  • Dark and light, with equal care. Both themes get the same attention to detail, and rich HTML mail keeps the look its sender designed.
  • At home on your desktop. Native notifications, a tray icon with your unread count, and inlark can be your default mailto: handler. Launch automatically when you sign in, quietly in the tray or with an open window.
A conversation open in inlark's reader, with reply, reply all and forward below the message. inlark's command palette listing actions and folders, each with its keyboard shortcut.
A focused reader, without the clutter Ctrl K: every action, folder and account in a few keystrokes

[!NOTE] inlark is an early preview. The everyday essentials work, but it's young. Keep your server's webmail bookmarked for now, just in case.

Install

Grab the latest build from the releases page:

Native installers check for updates in the background. When an update downloads successfully, inlark installs it after you quit, so it never interrupts your work. If the automatic update fails, inlark links to the download page for a manual install. Flatpak and Nix installations use the update steps below.

Platform Download
Windows Installer (x64)
macOS DMG or ZIP, for both Apple Silicon and Intel
Linux AppImage, .deb, .rpm or Flatpak (x64), or Nix

Flatpak

Install Flatpak using your distribution's instructions, then download the .flatpak bundle from the latest release. From the download directory, run the following, replacing <version> with the downloaded version:

flatpak install --user ./inlark-<version>-x64.flatpak
flatpak run com.inlark.Inlark

Confirm adding Flathub when asked: it supplies the shared runtime. inlark itself is distributed through GitHub Releases and does not require a Flathub listing.

Updates are manual. Download the new bundle, quit inlark, and install it with flatpak install --user --reinstall ./inlark-<new-version>-x64.flatpak. This keeps your Flatpak accounts, drafts and settings. flatpak update updates the shared runtime, but does not fetch new inlark bundles. The native installer updater is disabled in Flatpak.

Flatpak stores app data separately, under ~/.var/app/com.inlark.Inlark/config/Inlark. Switching from an AppImage, .deb, .rpm or Nix installation does not import existing accounts or drafts. The internal Flatpak ID and Inlark data directory keep their original spelling for compatibility.

Nix and NixOS

Install from the flake:

nix profile install 'github:inlark/inlark#inlark'

Or enable the NixOS module in your flake configuration:

{
  inputs.inlark.url = "github:inlark/inlark";

  outputs = { nixpkgs, inlark, ... }: {
    nixosConfigurations.my-host = nixpkgs.lib.nixosSystem {
      system = "x86_64-linux";
      modules = [
        inlark.nixosModules.default
        { programs.inlark.enable = true; }
      ];
    };
  };
}

The package includes the desktop entry, icon and mailto: handler, for x86_64 and aarch64 Linux. These examples follow the latest code on the default branch.

To update a profile installation, run nix profile upgrade inlark. For NixOS, run nix flake update inlark from your system configuration directory, then sudo nixos-rebuild switch --flake .#my-host (replace my-host with your host name). Nix keeps the installed revision until you update it; removing the release tag does not enable automatic updates.

Connect an account

Open Settings → Accounts → Add account and type your email address. inlark looks up what your domain publishes and shows you the protocol, servers, ports and security it found before it asks for a password. Set up manually is always there if you prefer.

  • JMAP is preferred when your server offers it. inlark finds it through DNS SRV or /.well-known/jmap.
  • IMAP/SMTP settings come from your domain's autoconfig file or DNS SRV records. Only if your domain publishes nothing does inlark ask Thunderbird's public settings directory, and then it sends just the domain.
  • Encryption is required. inlark uses implicit TLS or required STARTTLS, always with certificate verification and never a plaintext fallback. Your password is never tried against a server you didn't choose.
  • Self-signed certificates are trusted one at a time. When a certificate can't be verified, such as Proton Mail Bridge's on 127.0.0.1, the connection check shows who it's issued to, how long it's valid and its SHA-256 fingerprint before any password is sent. You can trust exactly that certificate for that server. If it ever changes, inlark stops before signing in and asks again. Expired certificates are never accepted.
  • Passwords go into your OS keyring when one is available. Without a keyring, you decide whether to remember a login on this device. If you do, the password is stored unencrypted in an owner-only file.

IMAP accounts build a local index in the background, newest Inbox mail first. Until it catches up, lists tell you that older mail may be missing, and search still runs on the server. If your server can't do an action safely, such as a move without MOVE or UIDPLUS, inlark turns it off and tells you why rather than guessing.

Gmail and Microsoft sign-in (OAuth) aren't supported yet.

Optional OpenPGP email encryption is available for each sending address under Settings → Encryption. Read the encryption guide for setup, backups, protected drafts, key discovery and device transfer. Cross-platform and Thunderbird release checks remain required before publishing this feature.

Build from source

You'll need Node 24 and pnpm 12.3.4.

pnpm install --frozen-lockfile
pnpm dev          # the desktop app
pnpm dev:web      # browser preview with sample mail, no real accounts

Add ?stress=1 to the browser preview's URL for five synthetic 50,000-message inboxes, or run pnpm dev -- --demo for a sample workspace in the desktop app. On NixOS, run nix develop path:. first. The shell provides a compatible Electron.

The desktop UI uses Tailwind CSS v4 through the Vite plugin, with its CSS-first theme in packages/ui/src/styles.css. Put styling directly in React className props, using cn for conditional utilities and component variants. Keep utility names complete so Tailwind can detect them. Reserve regular CSS for global defaults, theme variables, keyframes, and editor-generated HTML; use inline styles for runtime values such as account colors and measured sizes. Colors follow the app's appearance setting, and spacing uses a fixed 4px unit to preserve the desktop's 14px typography.

Checks, packaging and releases
pnpm check             # formatting, types, tests and a production build
pnpm test:stalwart     # real JMAP, IMAP and SMTP against a disposable Stalwart server (Podman or CONTAINER_RUNTIME=docker)
pnpm test:packaged-crypto # bundled worker encryption and locking smoke test
pnpm test:crypto-interop # independent GnuPG verification of inlark output
nix build path:.       # Nix package in ./result/bin/inlark
pnpm package:linux     # AppImage, .deb and .rpm in apps/desktop/release
pnpm package:flatpak   # standalone .flatpak bundle (x64 Linux)
pnpm test:flatpak      # isolated Flatpak installation and native IPC/SQLite smoke test
pnpm test:deb          # Debian packaging smoke test (Podman)

The Nix build is pinned by flake.lock, pnpm-lock.yaml and the dependency hash in nix/package.nix. After changing dependencies, replace that hash with the one Nix reports.

Flatpak packaging also needs flatpak and flatpak-builder; its smoke test needs Xvfb and xauth. See the Flatpak packaging guide for release automation and desktop validation.

To smoke-test the Nix package without opening a window:

INLARK_DATA_DIR="$(mktemp -d)" ./result/bin/inlark --smoke-test --ozone-platform=wayland

Normal app data lives in Electron's userData directory, usually ~/.config/Inlark. The legacy directory name and OS credential-storage identity are preserved so existing accounts, drafts and settings remain available after the lowercase branding change. INLARK_DATA_DIR overrides both the app-data and session-data directories.

How the repository is organised
Location What lives there
apps/desktop/src/main Network access, credentials, drafts and the send journal, discovery, IMAP indexing, native lifecycle
apps/desktop/src/preload The small, validated bridge between the app and the system
apps/desktop/src/renderer The React app: lists, reader, composer, preferences
apps/marketing The Astro landing page, deployed as static Cloudflare Workers assets
packages/core Platform-independent types, validation, search and merge logic
packages/jmap The JMAP provider
packages/imap The IMAP/SMTP provider
packages/mime Shared composition and parsing of complete mail messages
packages/crypto OpenPGP, authenticated local vault, PGP/MIME and discovery rules
packages/ui Shared components and the Tailwind theme
tests Domain, protocol, storage and real-server tests

Built with Electron, React, TypeScript, Tailwind CSS, Base UI, TanStack and Turborepo.

What's not here (yet)

inlark tries to make everyday email excellent before adding more features. AI, snooze, scheduled sending, rules, calendars, a full address book and mobile apps are all deliberately out of scope for now. If you need your email client to also be your calendar, your CRM and your life coach, this isn't that client. Yet.

Credits

inlark stands on the shoulders of two products that showed how good software can feel:

  • Linear, for its restraint, clear hierarchy and obsessive attention to detail, the bar for inlark's visual design.
  • Superhuman, for proving email can be fast, focused and driven from the keyboard, the bar for inlark's workflows.

inlark isn't affiliated with either. We just admire their work.

License

Copyright © 2026 Paul Koeck. inlark is free software under the GNU Affero General Public License v3 (AGPL-3.0-only). The bundled Inter font is under the SIL Open Font License; the outlined Hanken Grotesk wordmark is also under the SIL Open Font License.