Compare
Three tools that don't know your business. One that does.
Inboxes, transactional sending, and newsletters usually mean Gmail, Resend, and Mailchimp: three subscriptions, three logins, and not one of them knows a thing about your store, your customers, or your rules — because none of them is yours to teach. Tinbox runs all three on your own Cloudflare account, where the data and the sending keys stay. Take all three at once, or swap in just the send API and migrate the rest when you're ready.
The cage
You don't rent a worse inbox. You rent a stranger.
Gmail looks identical for a law firm and a Shopify store, even though they need opposite things from it. That's not a missing feature — it's the deal. A hosted inbox is sealed: it can't read your orders, can't surface the customer's account, can't draft from the way you actually answer, and you can't open it up and make it, because you don't own it. So every thread starts from zero.
You read the order number, switch tabs, look it up in the admin, switch back, and type the reply by hand — a hundred times a week, forever. The inbox is the most important system you run, and it's the one you have the least say over.
Tinbox runs on your account and your data, so it isn't a stranger. An order email renders the live order, a ticket pulls the customer's account, a refund button sits right in the thread — and an agent works the queue before you sit down. That's the difference the price tag never shows: not a cheaper Gmail, a legible one.
The matrix
The same job, four ways.
Yes, no, or partial — with a word of context where it matters. The hosted columns are good at the one row they were built for. Tinbox is the only one that holds the whole table on an account that's yours.
| Capability | Tinbox | Gmail / Workspace | Resend | Mailchimp |
|---|---|---|---|---|
| Shared team inboxes (support@, billing@) | Yes | Yes | No | No |
| Transactional sending API | Yes | Partial | Yes | Partial |
| Newsletters / broadcasts | Yes | No | Partial | Yes |
| Renders your live data in the thread | Yes | No | No | No |
| Agent / MCP access | Yes | No | No | No |
| Your own domain | Yes | Yes | Yes | Yes |
| Data + keys live in your own account | Yes | No | No | No |
| Self-host on your own account | Yes | No | No | No |
| Pricing model | Usage (~$0) + one-time license | Per seat / mo | Per email / mo | Per contact / mo |
| Lock-in / export | git clone | Export / migration | Export project | Export / migration |
Trade-offs, not a teardown. The hosted tools are genuinely excellent at being hosted — zero setup, someone else on call. Tinbox is for teams who'd rather own the thing than rent it, and who want the two rows in the middle no hosted tool can give them: an inbox that renders their live data and an agent that runs it.
The git clone export assumes the opt-in git archiver is enabled; without it, you still own everything — export the D1 database and pull the raw R2 objects straight from your account.
The catch
The free plan is the bait. The meter is the trick.
That's how it gets you: the entry price you researched isn't the price you pay by year two. Add a second sending domain, cross a contact threshold, invite one more teammate — and the meter starts ticking. The feature you need is always the one behind the upgrade wall. Tinbox has nothing to gate, because it runs on your account: every domain, contact, and seat is just yours.
A second sending domain
A premium add-on on most send plans
Tinbox
Every domain you run, included
Your list crosses a contact threshold
Bumped to the next per-contact tier
Tinbox
Your list, your size — no per-contact fee
One more teammate in the shared inbox
Another per-seat charge, every month
Tinbox
Bring the whole team — no per-seat billing
Drop the branding or lift a limit
Upgrade to unlock it
Tinbox
It's your code — change anything
There are no tiers to climb and no thresholds to cross, so there's nothing to outgrow. The only bill is your own Cloudflare usage — and that brings us to the one number this whole page comes down to.
The cost
One bill that recurs. One that doesn't.
The usual stack
Google Workspace seats, Resend volume, and a Mailchimp contact plan — three subscriptions that grow with your team and your list, every month, for as long as you run a business.
Tinbox
You pay only your own Cloudflare usage (usually about $0/mo for a small team) plus an optional one-time $249 lifetime license. No seats, no per-contact fees, no renewals.
Why one of these can be a one-time price and the other can't. A subscription rents you software that rents you AI — the inference cost recurs, so the bill has to. Tinbox runs the AI on your keys: a cheap model for autocomplete, a frontier one where it matters, no markup on the intelligence. You own the stack and you hold the bill, so the price is paid once. That's not a discount — it's the honest shape of owning the whole thing. The last email tool you'll ever buy.
The full math — estimate your real usage bill against your team size and volume — lives on the pricing page →
Head-to-head
Deep dives, tool by tool.
The matrix is the summary. Each comparison below goes the full distance: where the hosted tool wins, where Tinbox does, and what switching actually involves.
Stop renting a stranger.
Everything email — inbox, sending, newsletters, outreach — in one owned stack on your own Cloudflare account. The suites do “everything” too, but closed and frozen on a rented seat; yours runs where your data already lives, so it becomes your everything, not theirs. It renders your live orders, drafts your replies, and runs your campaigns — one deploy, three subscriptions gone, the copy you keep yours for good. Start free and run your own copy first; buy the license when you're ready to own the source.