Compare Dedicated IP Warmup Options Across Email Services

Three warmup models email services offer — compared

Every email service handles dedicated IPs and warmup differently. Strip away the marketing and three models emerge. Knowing which one a provider uses tells you more than any feature checklist:

Mails.ai uses the first model — warm shared pool — by default, with a dedicated IP available on request on the Scale plan when volume justifies it. We would rather tell you which option fits your send profile than sell a feature that hurts delivery below a certain threshold.

The shared rail — warm from message one

Every agent on Mails.ai sends from an address on the shared sending domain (agent.yourworkspace@send.mails.ai), on infrastructure with an established record. There is no ramp period, no seed network to subscribe to, and no warmup schedule to manage.

What keeps that rail warm is the traffic on it, not a tool: every send is checked before it leaves, and every agent carries its own reputation score. The mail that moves through the shared infrastructure is real transactional and agent mail with low complaint rates — and that record is what your agent inherits on its first send.

• No warmup wait before your first message
• No seed-network subscription alongside your email plan
• Per-agent reputation scoring keeps individual agents from affecting each other
• Custom domains get a DKIM keypair automatically — publish one DNS record and sends switch to your brand domain once it verifies

Dedicated IPs — when they help and when they do not

A dedicated IP isolates your sending from every other sender on the platform. Your placement cannot be hurt by another sender’s behaviour — and also cannot be helped by the warm record they have built. You start from zero.

Getting from zero to a stable reputation requires sustained volume. The floor the industry usually publishes is around 300,000 messages a month. Below that, a dedicated IP has too little traffic to establish or hold a reputation with mailbox providers. At low to mid volume, dedicated usually delivers worse than shared — not better.

At high and consistent volume, isolation becomes an asset: your placement is entirely yours to control. If that describes your send profile, a dedicated IP is available on request on the Scale plan.

What the warmup process actually involves

If you do move to a dedicated IP, the ramp is built from your real mail — not from a seed schedule. Any provider quoting you a fixed number of days is quoting a schedule; mailbox providers weight opens, replies and complaints from real recipients, and only real traffic produces those. What throttling a ramp schedule does is avoid tripping rate-heuristics while your volume builds. It does not create reputation on its own.

On the shared rail there is no warmup to manage at all — the infrastructure is already sending at scale and your agent inherits that record:

# Send from your agent — no warmup state to wait on
curl https://api.mails.ai/v1/messages \
  -H "Authorization: Bearer $MAILS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "agent": "hello",
    "to": ["customer@example.com"],
    "subject": "Your request is ready",
    "body_text": "Here is what you asked for..."
  }'

# Check your domain's verification state
curl https://api.mails.ai/v1/domains/dom_123 \
  -H "Authorization: Bearer $MAILS_API_KEY"

# {
#   "id": "dom_123",
#   "domain": "mail.yourapp.com",
#   // pending -> verifying -> verified
#   "status": "verified",
#   "provider": "ownmetal",
#   "dns_records": [
#     /* each with "verified": true */
#   ],
#   "fail_reason": null
# }

Choosing between shared and dedicated

A quick heuristic: if you are sending under 100,000 messages a month, the shared rail delivers better than a dedicated IP would from the same starting point. Between 100,000 and 300,000 the answer depends on your complaint rate and sending patterns — ask and we can look at the data with you. Above 300,000 consistently, isolation starts to pay for itself.

Either way, the mechanics of sending do not change. Same workspace, same API, same dashboard — a dedicated IP is a routing change under the hood, not a product migration. And you can move back to the shared rail at any time.

Why a single platform beats cobbling two products together

When you compare dedicated IP warmup options across email services, a common pattern emerges: buyers end up with a sending provider plus a separate warmup tool on top. Mails.ai does not offer a warmup tool — because the shared rail is already warm and a dedicated IP warms through your real traffic, not a seed loop.

What you get from a single platform instead of two:

• No warmup dashboard to manage. The shared rail has an established sending record before your first message. Dedicated IPs warm through your actual send volume — there is no parallel seed service to run.
• Reputation tracking in one place. Per-agent scores, complaint rates, and suppression lists live in the same workspace as your IP configuration.
• No product migration when you scale. Moving from the shared rail to a dedicated IP is a request, not a re-integration. The API, SDK, and dashboard stay the same.
• Clean by default. Every send is checked before it leaves and every agent’s reputation is scored on its own — that is what keeps the shared rail’s record clean. You do not need to manage the hygiene of a warmup loop on top of it.

For the full arithmetic on dedicated IPs: see Dedicated IP — how it works and when you need it. For why most senders skip standalone warmup tools: email warmup service. For the short version on why free email warmup tools are unnecessary on a warm shared rail: For the ramp mechanics in detail: Automated Dedicated IP Warm-Up — And Why You Probably Should Not. For a provider comparison with a regional angle: Compare providers for dedicated IPs and managed warmup — Hong Kong.

Four questions that expose the real differences between providers

When you compare dedicated IP warmup options across email services, these four questions cut through the marketing and surface what each provider actually offers:

• Is the shared pool warm on day one, or do I have to ramp it? A shared rail that requires a warmup period is either new infrastructure or a pool that has not been carefully gated. Mails.ai’s shared rail has an established record because every send is checked before it leaves and every agent is scored on its own complaint rate.
• Is a dedicated IP self-serve, or is there an honest qualification step? A provider that sells dedicated IPs to anyone — including senders under 100,000 messages a month — is selling you a cold IP that will deliver worse than the shared pool. The right answer is “on request, and we will check your volume first.”
• Does the warmup happen through real mail or a seed network? Seed networks generate artificial engagement signals. Mailbox providers weight opens, replies and complaints from real recipients; seeds can fill a schedule but do not build a reputation. A dedicated IP warms through the traffic you actually send.
• Is IP routing a migration or a config change? If moving to a dedicated IP requires a new integration, you are looking at a different product tier — not a routing change. On Mails.ai it is a request; the API, SDK and dashboard stay identical.