Your mail stays with your provider and works locally
Brev keeps the working state it needs on your device. Your provider remains the authoritative mail service, and brevmail.com never receives mailbox content.
Current Brev architecture
A local working copy
Brev stores account-scoped mail metadata and device state in SQLite. Fetched message bodies and attachments live as content-addressed files. The interface reads immutable views built from that local model.
Your provider stays in charge
Gmail, Fastmail or the relevant provider continues to receive and store mail. Brev synchronizes directly through the approved provider API or protocol. New messages, uncached content and sending still require a network connection.
Long-lived credentials stay in Keychain
The Mac app stores provider refresh tokens in the native credential store, never in the mail database. Short-lived access tokens remain in memory. Command-line arguments and JSON output never contain stored credentials.
The app and CLI use one mail model
The graphical app and versioned command-line API operate on the same local mail model. Scripts do not need to scrape the interface or send a second mailbox copy to Brev.
CLI access is explicitly delegated
A separate script or agent receives one human-approved finite profile for one Account, optionally with an expiry. Current profiles range from status-only and search-only access to one exact mailbox, draft work or sending. Search permission does not silently grant access to open message bodies or attachments, and custom policy shapes remain future work.
Local search has an offline engineering gate
Brev's reproducible search benchmark publishes 50,000 synthetic messages across three provider-shaped Accounts through the canonical SQLite path, then checks body and attachment-text coverage, restart behavior and Account provenance while the operating system denies network access. It is an internal regression gate, not a speed comparison with another mail client or an end-to-end UI benchmark.
Portable core does not mean every platform is available
Brev keeps provider, search, draft and command behavior outside the Mac renderer. The supported native client and credential boundary are currently macOS only. There is no Windows or Linux download.
What Brev services can see
The current product architecture does not require a Brev server to hold your mailbox. The website stores preview responses and optional anonymous page and conversion events. It does not receive addresses, subjects, bodies, attachments or search queries from the mail app.
Bring the mailbox you actually use
Tell us your platform, providers and current client. Mac preview invitations are matched to supported account combinations.
Join the private previewAvailable by invitation on macOS