Dedicated IP vs shared pool: when the upgrade matters

Dedicated IPs get sold as a deliverability upgrade, and sometimes they are one. They're also, honestly, not a fix for a fundamentally low-quality sending pattern, and at low volume they can be a worse choice than a well-managed shared pool. Worth being specific about which situation you're actually in.

What a dedicated IP actually gives you

Your own sending reputation, isolated from every other customer on the platform. On a shared pool, your deliverability is partly a function of how well-behaved everyone else sharing that pool is; a provider with good suppression and abuse controls (checked in the migration guides on this blog) limits that risk, but doesn't eliminate it entirely. A dedicated IP removes that dependency. It's available as an add-on on Envello's Scale tier.

Why it's not a magic fix

A dedicated IP with no sending history has no reputation at all, which mailbox providers treat with more suspicion than an established shared pool, not less. Moving to a dedicated IP resets you to zero and requires its own warmup process (gradually ramping volume so mailbox providers build trust in the new IP) before it performs as well as the shared pool you left. If your volume is too low to warm an IP properly, a dedicated IP can sit under-warmed indefinitely and underperform a shared pool that already has years of established reputation.

How the warmup actually works on a dedicated IP

A reasonable ladder ramps from a few hundred emails a day in week one up to full volume by week three or four, prioritizing your most engaged recipients early (accounts that reliably open and interact) since positive engagement signals build reputation faster than raw volume alone. Skipping the ladder and sending full volume from day one is the single most common way a dedicated IP underperforms expectations in its first month.

The actual decision point

• High, consistent volume: a dedicated IP is worth considering, since you have enough sending to warm it properly and maintain reputation
• Low or spiky volume: a shared pool on a provider with good hygiene is usually the better choice, you benefit from established reputation you didn't have to build
• Specific compliance or contractual requirements for IP isolation: this overrides the volume calculus, get the dedicated IP regardless of whether it's the deliverability-optimal choice

A rough volume threshold

There's no universal number, but as a practical guide, most senders under roughly 50,000 emails a month don't generate enough consistent volume to keep a dedicated IP meaningfully warm, and are better served by a shared pool. Above that, and especially with steady day-to-day volume rather than sporadic bursts, a dedicated IP starts to earn its cost. Sporadic high-volume sending (a monthly newsletter-style spike with quiet weeks between) is a worse fit for a dedicated IP than steady daily transactional volume at the same monthly total, since reputation decays during quiet periods.