Dedicated IP vs shared IP for cold email — when you actually need one

What "shared" and "dedicated" actually mean

A shared IP is a sending address used by many senders at once. Your provider — Gmail, an ESP like SendGrid, or a cold email platform's upstream relay — pools customers onto a fleet of IPs. Reputation is collective. If a hundred other senders on the same IP have clean lists, you benefit. If they're scammers, you suffer.

A dedicated IP is reserved for one sender. You control 100% of the sending behavior; your reputation reflects your decisions and nothing else. That isolation is the value proposition. Everything else — warm-up, monitoring, Postmaster Tools — is operational machinery to actually realize the isolation.

The OAuth caveat nobody mentions

Here's the part that disqualifies most cold email setups before the conversation even starts: if you connect a Gmail or Outlook mailbox via OAuth, you cannot use a dedicated IP. Period. Google and Microsoft send your email through their own infrastructure, on their own IPs, regardless of which platform initiated the send. No code change, no add-on, no upgrade tier changes that.

Dedicated IPs only apply when you're sending through a custom SMTP server — yours, your platform's, or a relay like AWS SES. If your cold email stack is 100% OAuth (a lot of agency stacks are), the dedicated IP question is moot. Stop reading. Spend the $39/month on better lists.

If your stack mixes OAuth and custom SMTP, dedicated IPs only affect the SMTP leg. You can't consolidate Gmail-connected sends onto an IP you control.

When shared IPs win

Shared pools are usually the better choice. They have three structural advantages most teams underweight:

• 1.No warm-up. A shared pool already has months or years of established reputation. You start sending at full plan volume the day you sign up.
• 2.Free or bundled. Sharing infrastructure is the entire economic model of every cold email platform's base tier. The marginal cost to you is zero.
• 3.Zero ops burden. When an IP gets listed, the provider handles delisting and rebalancing. You never know it happened.

The classic counter-argument — "but other senders can hurt my reputation!" — is mostly theoretical at well-curated platforms. Reputable providers actively monitor their pools and eject bad senders before they contaminate IPs at scale. The risk exists; it just isn't large enough to justify $39/month plus 4–8 weeks of warm-up for low-volume senders.

When dedicated IPs genuinely win

A dedicated IP is the right choice when at least two of these are true:

Volume-based decision matrix

Industry consensus splits roughly along these volume bands:

Warm-up reality — 4 to 8 weeks of throttled output

A fresh dedicated IP has no sending history. To Gmail and Microsoft, it looks like a brand-new sender that just appeared out of nowhere — exactly the signature of a spam operation spinning up burner infrastructure. To prove otherwise, you have to ramp up volume slowly while building a positive engagement signal.

The industry-standard curve, which AWS SES enforces automatically and Superkabe applies by default:

You're paying $39/month from day one but can only send a few hundred emails per day for the first two weeks. Worth budgeting for. Aggressive ramps — "I have a launch next week, push to 5K/day immediately" — are the single most common cause of permanent reputation damage on new IPs. Mailbox providers see "new IP, sudden volume spike" as a textbook spam signal and flag it within days. That flag can stick for months.

How Superkabe does dedicated IPs

Our model is deliberate and simple, and tells you what we won't do:

• ▸1 IP per workspace. Strict cardinality. If you run three workspaces and want all three on dedicated infrastructure, you buy three IPs. We don't share an IP across your workspaces — that defeats the entire point.
• ▸$39/month per IP. Same price as Smartlead. About a third of what SendGrid and Mailgun charge for the equivalent service.
• ▸Provisioned on AWS SES. Industry-standard infrastructure. We're not running our own relay; we don't want to be in the IP delisting business at 2 AM.
• ▸Default warm-up enforced. The schedule above is applied automatically. You can override it from the dashboard, but only after reading a warning modal that explains why aggressive ramps cause permanent IP burn.
• ▸Reputation monitoring at the IP level. The same DNSBL scans, Postmaster Tools sync, and 5-phase healing pipeline that protects shared-pool sends runs on your dedicated IP. If it's listed, we pause and heal automatically.

Full setup walkthrough lives in the Dedicated IP setup guide. Technical reference is in the Dedicated IP docs.

What a dedicated IP does NOT fix

This is the part most upsell pages skip. A dedicated IP solves exactly one problem: the "blame other senders" problem. It does not improve any of these:

• Bad lists — high bounce rates burn dedicated IPs faster than shared ones, because there's no other senders to dilute your signal
• Bad copy — spam-trigger language and over-aggressive personalization tokens score the same regardless of IP
• Aggressive cadence — sending 500 emails in 5 minutes from one mailbox looks like spam from any IP
• Missing DNS records — SPF, DKIM, and DMARC failures tank you on dedicated IPs just as fast
• Domain reputation — Gmail tracks your domain's reputation independently of your IP's. A burned domain is a burned domain

If your bounce rate on a shared pool is over 5%, fix list hygiene first. The IP change won't save you. We mention this because we've seen too many teams buy a dedicated IP, change nothing else, and complain a month later that deliverability is the same. It is. Because the IP wasn't the problem.

The bottom line

For most cold email teams, the right answer is the boring one: start on the shared pool, stay on the shared pool, and only upgrade when you cross 50K consistent monthly sends or hit a regulated-industry requirement.If you cross those thresholds, the $39/month is worth it — but go in understanding that you're buying isolation, not a deliverability fix.

And if you're sending through OAuth-connected Gmail or Outlook mailboxes, skip the question entirely. Dedicated IPs aren't available to you, regardless of platform. Spend the budget on better lists or better copy instead.