Dedicated IP
Send through your own isolated IP address. One IP per workspace, automatically warmed, $39/month.
What is a dedicated IP?
A dedicated IP is an internet address used exclusively by one workspace to send email. No other Superkabe customer — and no other workspace inside your account — sends from it. The IP's sender reputation is shaped only by your sending behavior.
By default, Superkabe sends through the IPs of your connected mailbox provider (Gmail, Outlook, or your custom SMTP). That's a shared pool — fast to set up and free, but reputation is partly out of your hands. The dedicated IP add-on routes the custom-SMTP send path through an isolated AWS SES IP that's yours alone.
How it works in Superkabe
1 IP, 1 workspace
Each dedicated IP you purchase is bound to exactly one workspace. If you run multiple workspaces and want each on its own IP, you purchase one add-on per workspace. This keeps reputation cleanly isolated and avoids cross-workspace contamination.
Provisioned on AWS SES
We allocate your IP from Amazon Simple Email Service's dedicated IP pool. This gives you industry-standard infrastructure, automatic DKIM signing, and access to AWS's deliverability stack. From your perspective it's a single line item; Superkabe handles the SES configuration set, IP binding, and bounce/complaint feedback loop.
Automatic warm-up
A fresh IP has no sending history, so mailbox providers throttle it aggressively. Superkabe applies a default 4–8 week warm-up curve — starting at 50–100 sends/day and ramping up weekly. The throttle is enforced at the send queue, so you can plan campaigns without worrying about overshooting.
Editable throttle (with a warning)
You can override the default warm-up schedule from the dashboard if you have a specific campaign window. We surface a confirmation modal first because raising volume too quickly is the most common cause of permanent reputation damage on new IPs. If you accept the warning, the new schedule applies immediately.
Reputation monitoring + healing
The same monitoring stack that protects your shared-pool sends runs at the IP level on your dedicated IP: DNSBL scans, Gmail Postmaster Tools, Outlook SNDS, and ESP-aware routing. If the IP gets listed or the reputation slips, the IP enters the 5-phase healing pipeline — and Superkabe pages you immediately.
Default warm-up curve
Superkabe's default schedule mirrors the deliverability industry consensus and what AWS SES's built-in auto warm-up enforces during the first 45 days:
| Week | Daily cap | What you should do |
|---|---|---|
| 1–2 | 50–100/day | Send to your highest-engagement segments only. Watch bounce rate stay under 2%. |
| 3–4 | 1,000–5,000/day | Begin running your normal lead lists. Validate every list before sending. |
| 5–6 | 10,000–50,000/day | Full campaign cadence. Postmaster Tools data should now be populating. |
| 7+ | Full volume | IP is fully warm. Throttle is removed; you send up to your plan limit. |
When to choose dedicated
A dedicated IP is the right call when at least two of these are true:
- ▸You consistently send 50,000+ emails per month from one workspace.
- ▸You operate in a regulated industry (finance, healthcare, legal) where reputation isolation is contractual.
- ▸You want access to Gmail Postmaster Tools and Outlook SNDS data, which require an IP you control.
- ▸You've been burned by a shared pool before and want a clean restart on infrastructure you fully own.
If none of those apply, the default shared-pool send path is almost always better. Most teams sending under 50K/month see no deliverability gain from a dedicated IP and pay $39/month for psychological comfort. We'll happily tell you when you don't need it.
Pricing
Add-on, billed monthly. Stacks on top of any plan (Starter, Pro, Growth, Scale, or Enterprise). No setup fee. Cancel anytime — the IP is reclaimed at the end of the billing period.
See pricingFAQ
Does a dedicated IP work with Gmail / Outlook OAuth mailboxes?
No. OAuth-connected Gmail and Microsoft mailboxes always send through Google's and Microsoft's own IPs — that's a fundamental property of OAuth-based sending and no platform can change it. Dedicated IPs only apply to the custom-SMTP send path. If your workspace is OAuth-only, a dedicated IP is not useful for you.
How long does provisioning take?
After purchase, the IP is allocated from AWS SES typically within 2–10 minutes. It then enters the warm-up phase immediately. You'll see it in your dashboard with status Warming and a real-time progress bar showing the current daily cap.
What happens if my IP gets blacklisted?
The same way any other piece of your infrastructure is treated: the IP is moved through the 5-phase healing pipeline. We pause sending, run DNS and reputation checks, validate against major DNSBLs, then graduate the IP back to active state once it's clean. You're notified at every transition.
Can I assign one IP to multiple workspaces?
No. The whole point of a dedicated IP is reputation isolation — sharing one across workspaces defeats that. If you have three workspaces that each need dedicated IPs, you purchase three add-ons.
Can I edit the warm-up throttle?
Yes, but you'll see a warning modal first. Raising the daily cap faster than the recommended curve is the single most common cause of permanent IP burn — we surface the warning so you confirm intent. If your campaign timing requires a faster ramp, you can override.
What if I cancel?
Cancellation is effective at the end of the current billing period. The IP is returned to AWS SES's pool and the workspace falls back to the shared send path. Your sending history on that IP is gone — if you re-purchase later, you'll get a fresh IP that needs warming again.