Why we build local-first

Most software treats your data as the price of admission: hand it over, and we'll do something useful with it. We think that trade is backwards. Your inbox, your contacts, and your accounts should work for you — on your device, on your terms.

What local-first means

It means the core of each product runs where your data already lives: on your device. Message bodies, contact records, vault entries, search indexes — they stay local. The network is something your data crosses only when you decide it should, with the exact payload shown to you first.

What you get

• Speed. Local data is instant. No round trips to render your inbox or search your archive.
• Availability. Your data works offline, because it was never somewhere else.
• Control. Cloud features are opt-in and disclosed. Consent is recorded as an event you can review and revoke.
• No brokering. There's nothing to sell when the data never sat on our servers in readable form.

Why it's worth the difficulty

Local-first is harder. You sync encrypted state instead of trusting a central database. You design consent into every boundary crossing. You give up the easy telemetry. We think that difficulty is exactly the point — it's the work that keeps your data yours. It's the only way we're willing to build.