The cold email infrastructure market has produced a lot of terminology: private infrastructure, distributed infrastructure, dedicated pools, managed mailboxes, sending networks.
Underneath it there are only two questions that change your outcomes. Who else sends from your IP, and who controls your domains. Everything else is an implementation detail or a marketing word.
Here is what each architecture actually means.
The four architectures
Mainstream mailboxes (Google Workspace, Microsoft 365)
Real mailboxes on the platforms businesses use for internal email.
IPs: large shared pools with essentially open enrolment. Anyone with a credit card is on them. Reputation: the platform’s, plus your domain’s. You cannot isolate yourself from other senders. Cost: highest per mailbox, because you are paying a per-seat licence designed for employees. Best for: low volume, where platform trust outweighs control, and for enterprise recipients who respond differently to a familiar sending platform.
Shared pool infrastructure
Purpose-built cold email infrastructure where senders share IPs.
IPs: shared, but the pool quality varies enormously — this is the crucial point. A vetted pool with sender screening, enforced ramps and complaint monitoring is a different product from an unvetted one, even though both say “shared”. Reputation: partly yours, partly the pool’s. Cost: lowest of the purpose-built options. Best for: senders below roughly 1,500 to 2,000 emails per IP per month, where there is not enough volume to build a dedicated IP’s reputation. The reasoning is in the shared versus dedicated piece.
Distributed infrastructure
Sending spread across many IPs and domains, with volume deliberately kept low per sender.
IPs: many, often shared, with the design principle being that no single IP or domain carries enough volume to attract attention. Reputation: diffuse by design. Hard to build, and also hard to damage badly in one place. Cost: typically mid-range. Best for: high volume where the strategy is spreading risk rather than building a reputation asset.
The honest trade-off: distributed sending limits the damage from any single problem, and it also means you never accumulate the sender reputation that makes deliverability predictable. You are optimising for resilience over reputation. That is a legitimate choice, and it is a different choice from the one private infrastructure makes.
Private infrastructure with dedicated IPs
An IP reserved for one sender.
IPs: yours alone. Reputation: entirely yours to build, and entirely yours to damage. Cost: modest premium over shared. Best for: consistent volume above roughly 5,000 per IP per month, and anyone who needs to debug deliverability rather than guess at it.
The two questions that matter
Who else sends from your IP?
Nobody — dedicated. A vetted, monitored group — a managed pool. Anyone with a card — mainstream platforms. Many, deliberately diluted — distributed.
The answer determines whether your placement problems are yours to fix or somebody else’s to cause.
Who controls your domains?
If domains are registered to you on an account you control, the reputation you build is an asset you keep. If they belong to the provider, it is rented, and it disappears when you leave. This is covered at length in the domain ownership piece and it is the question most often left unasked.
Every other distinction — pool naming, “distributed” versus “private”, managed versus self-service — is downstream of these two.
The vocabulary decoded
| Vendor phrase | What to verify |
|---|---|
| “Private infrastructure” | Private IPs, or just a private tenant on shared IPs? |
| “Dedicated pool” | Dedicated to you, or to a group you are in? |
| “Distributed sending” | Across your own domains, or across a shared network? |
| “Managed mailboxes” | Who owns the domains at the end? |
| “Sender network” | Usually a shared pool. Ask about vetting. |
| “Unlimited warmup” | Unlimited per mailbox, or per plan? |
“Dedicated pool” is the phrase that most often means something other than what a buyer assumes.
Matching architecture to volume
| Monthly sends | Sensible architecture |
|---|---|
| Under 10,000 | Mainstream mailboxes, or a managed shared pool |
| 10,000–50,000 | Managed shared pool, or dedicated if volume per IP supports it |
| 50,000–250,000 | Dedicated IPs, segmented by campaign type |
| 250,000+ | Multiple dedicated IPs, separated by risk or client |
| Agency, any volume | Separate IP sets per client, whatever the total |
That last row overrides the rest. An agency running 30,000 sends across twenty clients should still isolate clients, because one client’s aggressive list should not affect another’s placement.
The mistake in both directions
Buying dedicated too early. A dedicated IP at 800 sends a month has no history and never accumulates any. It performs worse than a warm, well-managed pool. This is the most common overspend in the category and it is sold as an upgrade.
Staying on unvetted shared too long. At 50,000 sends a month, sharing IPs with unscreened senders means your deliverability is partly determined by strangers and you cannot debug it. The symptom is unexplained placement drops that resolve on their own.
The crossover is roughly 1,500 to 2,000 sends per IP per month, and consistency matters more than the total.
What to ask any provider
- Are the IPs dedicated to me, or shared — and if shared, how are senders vetted?
- Will domains be registered in my name, on my account?
- Can mailboxes be used with another sending tool over SMTP and IMAP?
- Is warmup capped, and at what?
- Who handles a blocklisting, and on what timeline?
- Can I move between shared and dedicated without rebuilding?
Question two is the one with the largest long-term consequence and the one buyers most often skip.
The short version
Four architectures, two real questions. Who else sends from your IP, and who owns your domains.
Below roughly 1,500 sends per IP per month, a well-managed shared pool beats a dedicated IP you cannot generate enough volume to warm. Above about 5,000, dedicated gives you a reputation you build and problems you can isolate. Distributed sending trades reputation-building for resilience, which is a real choice rather than a better one.
And whatever you choose, get the domains in your own name. That is the part you keep.
Next: shared versus dedicated IPs, or infrastructure cost at 10, 100 and 500 mailboxes.
Frequently asked questions
What is private email infrastructure?
Sending infrastructure where the IPs are reserved for one sender rather than shared. It gives you reputation you build and keep, and the ability to isolate deliverability problems to your own sending.
What is distributed email infrastructure?
Sending spread across many IPs and domains with deliberately low volume on each, so no single sender or domain carries enough volume to attract attention. It trades reputation-building for resilience.
Is shared IP infrastructure bad?
Unvetted shared pools are risky because your placement moves with senders nobody screens. A monitored pool with sender vetting and enforced ramps is a reasonable place to send from, and below roughly 1,500 sends per IP per month it outperforms a dedicated IP.
What should I ask a cold email infrastructure provider?
Whether IPs are dedicated or shared and how senders are vetted, whether domains are registered in your name, whether mailboxes work over SMTP and IMAP with other tools, whether warmup is capped, and who handles blocklist delisting.