About
We're spoiled, honestly. Deploy to the edge in seconds, spin up a database with one command, add payments in an afternoon, drop in auth as a library. Every layer of the stack got reinvented for the people who build on it. Except the one that runs your business.
Why we built it
We're spoiled, honestly. The last decade handed builders incredible tools: deploy to the edge in seconds, spin up a database with one command, add payments in an afternoon, drop in auth as a library. Great defaults, great docs, pricing that makes sense. Every layer of the stack got reinvented for the people who build on it.
Except email. To run it you still wire together a mailbox built for 2005, a sending API metered by the thousand, and a marketing tool that charges by the contact. Paradigms from twenty years ago, priced like it — per seat, per contact, per domain — and none of it yours to shape. So much great, affordable infrastructure everywhere you looked, and for email: nothing modern, nothing affordable, nothing a builder could actually build on.
It also turned out to be the wrong moment to be stuck. Mail is becoming something agents read and write, not just humans — triaging threads, drafting replies, running searches — and that only works if the mailbox is legible to software and you hold the keys. Renting your inbox behind a thin API doesn't get you there; owning the stack does.
So we built the email stack we wanted: one self-hosted deployment on your own Cloudflare account, programmable with Skills and run by agents, free to self-host and yours to change. Infrastructure you depend on should be infrastructure you control — and email had been left behind.
What that buys you
Here's the moment the whole idea pays off. A customer emails: "where's order #1234?" In a rented inbox that's a dead string — you copy the number, switch to Shopify, find the order, switch back, type the status from memory. In Tinbox the same email is the live order: status, items, tracking, and a click straight into the admin, rendered right there in the thread, because the inbox is reading your store on a key you hold. Nobody configured a "Shopify integration" you could buy off a shelf — you wired one Skill to your own store, and from then on every order email stopped being a receipt and started being the thing it's about.
That's what we mean by an inbox that knows your business. Not "context-aware" as a feature bullet — the actual live order, rendered on your data, because the stack is yours to reach into. A rented inbox can't show you that. It doesn't have the keys, and you can't give it any.
What we believe
Your mail, your sending credentials, and your archive live only in your Cloudflare account, never in a vendor's database. There's no Tinbox server in the path of your mail — nothing upstream to breach, subpoena, or hold hostage — and a lifetime license ships the full readable source, so the code is yours even if we're not around. Ownership here isn't purity for its own sake. It's the property that makes the other two possible.
Because the whole stack runs on your account, you can teach it your business: render the live order, add the column you actually need, wire a refund button to your own Stripe, write the rule for how you really work. The engine stays locked and stable; everything around it is yours to reshape. Customization isn't a paid add-on bolted onto someone else's product — it's the product.
A CLI, an MCP endpoint, and an in-app assistant share one typed tool manifest. Agents do the reversible work — search, draft, annotate, triage — freely; anything irreversible needs a scoped capability token or a human-merged change. A read-only token literally cannot send. The agent does the grunt work; you stay one yes away from in control.
Who it's for
It's a sharp tool for a specific kind of team, not a one-size-fits-all mailbox. Here's where it fits and where it doesn't.
Who it's for
Teams comfortable on Cloudflare who want to own the whole stack (data as plain files, sending on their own zone, every line of code theirs to change) and who want agents to help run it under human supervision. If you'd rather control your mail than rent it, this is built for you.
When a host is the better fit
If you want a zero-config consumer mailbox with a polished phone app and a human support line to call, a hosted provider will serve you better. Tinbox asks you to be comfortable on Cloudflare and happy to let agents do the grunt work — that's the trade for owning everything. We'd rather tell you that now than sell you the wrong thing.
Who's behind it
Tinbox is built and maintained by a small, hands-on team that runs its own mail on it. We're not VC-backed and we don't sell a subscription — the lifetime license is what funds the work, which keeps our incentives pointed at the people who own a copy, not at quarterly growth.
And because the license ships the full readable source, you're never depending on us alone. The continuity isn't a promise — it's a property of where the code runs: on your account, in your hands, auditable line by line. How we handle data and credentials is laid out on the security page.
The stack
The whole engine runs inside your own account — nothing to patch, no infrastructure of ours in the path of your mail.
One deploy, no servers
The whole engine — inbox, sending, lists, search — is one bundled app on your account. Nothing to patch, nothing of ours to trust.
Your data stays put
Mail and attachments live in your account, never cached upstream. Export anytime; no egress fees to get your own data back.
Reliable at any size
From a single receipt to a 4,000-recipient newsletter, sends are queued and retried — and a UNIQUE(message_id, recipient) row in the send ledger means a retry can never double-send, so every recipient gets exactly one copy.
Deliverable from day one
Inbound on your domain and outbound with SPF, DKIM, and DMARC aligned on your zone — the authenticated path the big providers use.
The engine, the workers, and the deploy script run on your own Cloudflare account. Buy the lifetime license to own the source, or stand it up free first — npx tinbox.
Prefer to run it yourself first? Run it free first →
And that's one of three subscriptions gone — Gmail, Resend, Mailchimp, replaced by one stack you own.
