Every cold-email tool you've looked at makes the same promise: dedicated sending. Read the fine print and almost none of them mean what a deliverability engineer means by that word. Shared IPs behind dedicated-looking UIs, one MTA serving thousands of tenants, DNS you can't touch, credentials you can't export. The word "dedicated" has been stretched until it doesn't mean anything at all.
This article is the technical version of that gap. If you're deciding between a shared SaaS mailbox and your own VPS, these are the moving parts that actually determine whether your campaigns hit the inbox.
What "shared" usually means
Most "dedicated inbox" providers run a single mail server cluster and hand you a slot inside it. You get a mailbox, a webmail login, maybe an SMTP endpoint. What you don't get is a dedicated IP, dedicated DNS records, or isolated reputation.
Concretely, shared platforms typically mean:
- One pool of IPs rotating across many tenants. When your neighbor sends a spam blast, the blocklist operator flags the IP, and your inbox placement drops with theirs.
- Shared MTA sending queues. A backlog from another tenant can push your mail into deferred retries.
- DNS records managed in a provider namespace (the SPF include chain points at them, DKIM keys live in their zone). You have no direct control, and if they rotate keys your validation silently breaks.
- No export path. Cancel the subscription and you lose the mailboxes, the warm-up history, and any IP reputation you accumulated.
None of this is visible from the marketing page. It's visible the first time you run a deliverability test against the raw mail server and see the RDNS point at a hostname you don't control.
What "dedicated VPS" actually gives you
A dedicated VPS with a production-grade mail server is a completely different structural model. Your tenant is you. The IP belongs to your account. The MTA, the DNS records, the TLS certificate, and the webmail all sit on compute you rent directly from the upstream provider.
That changes four things in ways that compound over time:
1. IP reputation isolation
Your IP's reputation is a function of your sending behavior — volume, bounce rate, complaint rate, engagement — and nothing else. No one else can burn it. This sounds obvious, but on a shared platform the single most important deliverability signal is outside your control.
2. Authentication you actually own
SPF, DKIM, DMARC, and DANE/TLSA records live in DNS zones you control. You can rotate DKIM keys on your schedule, align DMARC with your business rules, and publish DANE records tied to your own certificate chain. Shared platforms make some subset of these configurable; VPS gives you all four.
3. Real SMTP logs
A dedicated server exposes the full log stream: connection attempts, rejections, deferrals, bounce codes from each remote MTA. On shared platforms you get campaign-level metrics — opens, clicks, replies — and no visibility into why a specific remote rejected you. When something breaks, the difference between a log line like 550 5.7.1 [email protected] Message rejected due to content or environment and "message bounced" is the difference between a ten-minute fix and a week of guessing.
4. Portability
The mailboxes are standard IMAP/SMTP accounts. You can export them, migrate them, point any sending tool at them, or walk away with everything intact. The VPS is your asset, not a rental.
The economic shape of the difference
At low volume — under 10 mailboxes — shared platforms are often cheaper per seat. They win the sticker price.
At real volume, the math inverts. Shared platforms price per mailbox or per user because that's how their upstream Google Workspace / Microsoft 365 relationship is priced. A 50-mailbox cold email operation on Google Workspace is $300/month just for the seats, before any dedicated infrastructure. A dedicated VPS with 50 mailboxes on a production-grade mail server is flat-rate — the marginal cost of the 51st mailbox is zero.
This is why agencies running multi-client outbound end up migrating off Google Workspace around the 20-30 mailbox mark. The per-seat pricing model punishes the operators who are best at the job.
When shared is the right answer
To be fair: if you're sending 500 emails a month from one mailbox, a shared provider is fine. The failure modes above don't kick in at that volume. The technical gap only matters once you care about IP isolation, reproducible authentication, and SMTP-level debugging — which is almost always the moment you scale past one mailbox.
The takeaway
Deliverability is 80% infrastructure. The word "dedicated" on a marketing page means nothing until you check three things: is the IP yours alone, are the DNS records in your zone, and can you read the SMTP logs? If the answer is no to any of them, you are on shared infrastructure with a dedicated-looking skin. The rest of this blog is mostly about what changes when the answer is yes.
If you can't rotate your own DKIM key and read your own bounce codes, you don't have dedicated infrastructure. You have a nicer UI on top of someone else's.