Dedicated IP Setup Guide
Buy, assign, warm, and manage a dedicated IP from the Superkabe dashboard.
Before you start
- ▸Dedicated IPs only apply to custom-SMTP sends. Gmail and Outlook OAuth mailboxes always send through the provider's own IPs.
- ▸You need an active subscription on any plan (Starter and up). The dedicated IP is an add-on, not a replacement.
- ▸The IP needs 4–8 weeks of warm-up before it reaches full sending volume. Plan accordingly.
Step 1 — Purchase the add-on
Open the dashboard and navigate to:
Settings → Billing → Add-onsClick Add a dedicated IP. You'll be redirected to the billing portal to confirm the $39/month charge. After payment, the IP is provisioned on AWS SES — typically within 2–10 minutes.
Step 2 — Assign it to a workspace
A dedicated IP isn't doing anything until you bind it to a workspace. The cardinality is strict: 1 IP : 1 workspace.
From the dashboard:
- Go to Settings → Dedicated IPs.
- Find the IP with status Available (just-provisioned or unassigned).
- Click Assign and pick the target workspace.
- Confirm. The workspace's custom-SMTP sends are now routed through the IP.
Step 3 — Warm up the IP
Superkabe sets the throttle automatically. You don't have to do anything for the default schedule to run.
The default curve
- Week 1–2: 50–100 sends/day
- Week 3–4: 1,000–5,000 sends/day
- Week 5–6: 10,000–50,000 sends/day
- Week 7+: Full volume (up to your plan's monthly cap)
The send queue enforces this cap automatically. If your campaigns try to send more than the daily limit, the excess is queued for the next day rather than blasting and burning the IP.
Editing the throttle
If your campaign timing requires a faster ramp, you can override the schedule:
- Open the IP's detail page in Settings → Dedicated IPs.
- Click Edit warm-up schedule.
- Adjust the daily cap for any week.
- Click Save. A warning modal appears.
- Read the warning. Confirm only if you've thought it through.
Why the warning?
Aggressive ramps are the single most common cause of permanent IP burn. Mailbox providers see "new IP, sudden volume" as a textbook spam signal and flag it in days — and that flag can stick for months. The warning isn't bureaucratic; it's the most expensive lesson in deliverability, given to you for free.
Step 4 — Monitor reputation
Once the IP is warming, monitoring runs automatically. You see the data in two places:
In the dashboard
- • Current daily cap and how much of it's been used
- • Bounce rate, complaint rate (24h, 7d)
- • DNSBL status across the major lists
- • Postmaster Tools / SNDS reputation tier (once data populates)
In your alerts inbox
You're paged automatically (Slack, email, or webhook — whatever you've configured) when the IP is listed on a DNSBL, complaint rate breaches 0.1%, bounce rate breaches 2%, or the IP enters the healing pipeline.
Step 5 — Respond to alerts
If the IP gets flagged, Superkabe takes the first action automatically: sends pause, the IP enters Phase 1 of healing. You then have two choices:
Let auto-healing run
Recommended for most cases. The 5-phase pipeline cools the IP, validates DNS, re-tests reputation, and graduates it back to active when it's clean. No manual work needed.
Investigate manually
If the cause is obvious (a bad list import, a misconfigured campaign), pause the offending campaign first, then let healing finish. Removing the cause speeds graduation.
Common situations
My IP is "Warming" but campaigns aren't sending fast enough.
That's the throttle working as intended. During warm-up, the daily cap is below your full plan limit. The send queue holds excess sends for the next day. If you genuinely need faster ramp, edit the schedule — but read the warning first.
I bought an IP but didn't assign a workspace yet. Am I being charged?
Yes. The IP is provisioned and reserved as soon as you purchase, regardless of assignment. If you don't plan to use it within a week, cancel and re-purchase later — the warm-up state will reset anyway.
Can I move my IP to a new workspace mid-warm-up?
Yes. The warm-up state is tracked at the IP level, so reassigning doesn't reset the curve — the new workspace continues from wherever the IP left off.
I want a dedicated IP across all my workspaces. Cheapest path?
One IP per workspace is the rule, so the cheapest answer is one $39/mo subscription per workspace. If you have 5 workspaces and only 2 actually need isolation, only buy 2 IPs — the other 3 use the shared pool.
My IP got blacklisted. What now?
Auto-healing runs on it. You'll see status transitions in the dashboard: PAUSED → QUARANTINE → WARM_RECOVERY → ACTIVE. The pipeline includes a delist request to the major DNSBLs. If the listing is severe (e.g., Spamhaus SBL), we'll surface a manual remediation playbook.