MELTEMIpre-release · macOS

A desktop email client

Email that moves the way you do.

Meltemi is the dry summer wind of the Aegean — and a keyboard-first mail client built with Tauri and Rust. Six ways to see one inbox, an experiment lab where the interface earns its place, and AI whose every call is on the record.

In development — no builds published yetTauri 2 · Rust · React 19 · SQLite

Six inboxes. One archive.

Press v and the same mail rearranges itself around how you want to work right now.

Classic

Three panes, zero friction. The inbox you know, faster than you remember it.

Focus

One thread at a time. Everything else leaves the room.

Kanban

Mail as work: To triage, Waiting, Done. Drag threads like cards.

Timeline

Your day as a river. Mail lands where time actually put it.

Zen

A paper page and a keyboard. Triage as a calm ritual.

Split

Correspondence on the left, the noise on the right.

The keyboard is the interface

Gmail, Outlook, or Mutt keymap presets — rebindable per action. One action registry drives the keys, the ⌘K palette, the cheat sheet, and the hint bar, so nothing can drift.

AI you can audit

Every AI call is stamped into a local ledger: model, prompt version, tokens, and an honest cost estimate. Violet marks everything AI touched. A pause switch and a monthly budget sit above every provider.

Local first, keys in the keyring

Mail lives in SQLite on your disk. API keys live in the OS keychain, never in preferences or the database. Ollama runs models on your own machine; the cloud is optional.

An experiment lab, not a settings swamp

Two dozen interface experiments ship behind switches with keep/kill verdicts. You decide what survives — the product is grown in the open, not decided in a meeting.

This site is also the sync backend.

Alongside this page, this codebase carries the device-scoped API the desktop app will talk to: AI usage ledger aggregation across machines, and preference snapshots. Devices authenticate with hashed bearer tokens; nothing here pretends to be a login screen it isn't. The schema and routes are real — /api/devices, /api/ledger, /api/prefs — and documented in the README.