One message, many voices
Nestiel comes from 'nest' — every team exchange coming home to one clear, orderly conversation.
About Nestiel: Team Email by an Independent Developer
Why Nestiel
Nest is the idea. Email should not be a pile of isolated messages but an orderly home where everything comes to roost: every reply, every recipient, every bit of context settling into one clear conversation thread, kept on the record. That's where the name Nestiel comes from.
The biggest pain in team email is lost and fragmented context. So threading is a default capability — plus-tag and References together turn exchanges into threads automatically, and whoever picks one up sees the full story.
Data ownership matters equally. Email metadata lives in your own Postgres, attachments in the object storage you configure, and all IO goes over the Resend HTTP API — rather than handing your inbox to a black box you cannot see into. Your data and infrastructure stay yours.
The idea extends further today: from one intent, AI writes each recipient their own version — bulk efficiency with one-to-one density. One message, many voices.
Data ownership
Metadata in your own Postgres, attachments in the object storage you configure — your data always stays with you.
Conversations as a network
Exchanges thread automatically, context is visible to all, and email turns from isolated messages into an interconnected network.
Personal density at scale
Per-recipient personalization is a default: one intent becomes distinct wording and greeting for each recipient.
Start your team's email workflow
Connect your own domain and Resend account to begin. Data stays with you; capabilities scale with your org.