Isolate your email reputation on dedicated IPs and pools.

Take full control of your high-volume sender reputation and keep promotional blasts from delaying critical password resets or order receipts. Group dedicated IP addresses into isolated pools for transactional and marketing traffic, while automated 30-day warmup ramps new IPs gradually so Gmail, Outlook, and Yahoo do not throttle your mail.

A reputation of your own

Dedicated IP pool

Sending pool

Customer updates

Warming up

Start small

Build consistent volume

Your IPs

192.0.2.10
192.0.2.11

Your traffic

Defined by your pool

Conceptual warmup curve, not a volume target. Your sending history and audience quality matter.

Start on managed shared IPs, and move to dedicated pools as volume grows.

A dedicated IP pays off when you send consistent daily volume to keep its reputation warm with mailbox providers. On the Bird Email API, new workspaces start on a managed shared pool so lower-volume and irregular senders get reliable inbox delivery from day one without extra setup. As your sending volume grows, you can provision dedicated IPs so Gmail, Outlook, and Yahoo evaluate your mail on your own track record, and split traffic across separate pools so a large campaign blast does not slow down password resets.

Built to scale sender reputation without manual warmup schedules.

Isolate sending streams by traffic type, ramp new IPs safely, and protect live traffic with built-in routing guards.

  1. 01

    Separate pools for transactional and marketing mail.

    Group dedicated IPs into named pools so promotional campaigns and newsletters do not share an IP reputation with password resets, login codes, and receipts. Route individual sends to a specific pool or let routine traffic use your default pool.

  2. 02

    Automated 30-day warmup with shared-pool overflow.

    Sudden high volume from a brand-new IP triggers throttling at Gmail, Outlook, and Yahoo. Bird gradually increases the share of traffic your new IP carries over roughly 30 days and routes the remaining volume through the warmed shared pool.

  3. 03

    Default-pool safeguards that protect live traffic.

    Ordering a dedicated IP leaves your current default pool untouched so live traffic does not land on a cold address. Built-in routing guards also prevent anyone from canceling or moving the last active IP out of your default pool.

  4. 04

    Self-serve provisioning with reverse DNS configured.

    Purchase dedicated IPs from the dashboard or CLI within your plan quota. Bird assigns each address to your organization with its reverse-DNS (PTR) hostname configured automatically, ready for corporate allowlists that filter by sending hostname.

  5. 05

    Flexible pool reassignment and end-of-cycle cancellation.

    Reassign dedicated IPs between your pools with a single command as your email streams evolve. If you cancel an IP, it remains active in its pool through the end of the monthly billing period you paid for instead of dropping traffic mid-cycle.

Track warmup progress and pool assignments from the dashboard or CLI.

Manage your dedicated IPs and pools in the Bird dashboard or from the terminal with the Bird CLI. Inspect each address to see its current status, how far along its 30-day warmup ramp is, and which pool it belongs to before you switch your default pool or launch a high-volume send.

bird email dedicated-ips list
bird CLI
$ bird email dedicated-ips list | jq -c '.data[]
    | {address, status, warmup_progress, ip_pool_id}'

{"address":"192.0.2.10","status":"active","warmup_progress":100,
 "ip_pool_id":"ipp_01krdgeqcxet5s7t44vh8rt9mg"}
{"address":"198.51.100.7","status":"warming","warmup_progress":38,
 "ip_pool_id":"ipp_01ks3n8qv2wd6r9m4txf7hb0pc"}

Ramp new IPs over 30 days without throttling your production sends.

Sending full production traffic from an unfamiliar IP address triggers rate limits and spam filtering at Gmail, Outlook, and Yahoo. Bird warms each new dedicated IP from 0% to 100% over roughly 30 days, gradually increasing the share of mail it carries as its reputation builds. While the IP is warming, excess messages automatically overflow through Bird's warmed shared pool so your application keeps sending at full speed. Once warmup reaches 100%, the IP switches to active and carries your pool's full volume on your own sender reputation.

Explore the dedicated IP and warmup guides.

Follow the dedicated IPs and pools guide to purchase IPs, organize transactional and marketing pools, and select a pool per message at send time, or read the IP warmup guide to monitor warmup progress and learn when to switch your default pool.

Questions about dedicated IPs

When should I move to a dedicated IP, and do I have to warm it myself?
Consider a dedicated IP when you send consistent volume and need control over your own IP reputation. A low-volume or irregular sender may be better served by the shared pool. Bird warms a new dedicated IP automatically over roughly 30 days, with overflow routed through shared infrastructure during the ramp. Review your sending pattern with an email specialist before choosing.
Can I separate transactional and marketing traffic?
Yes. Group IPs into pools and route each traffic type to its own pool. This separates the IPs carrying your campaign and transactional streams. Authentication, domain reputation and recipient engagement still matter for both.

Scale without
losing control.

Organize teams in workspaces, control API access, and trace changes through audit logs.

Start with Email.
Build across channels with Bird.

Start building with Bird in minutes.