Sending infrastructure

Domains, mailboxes, and warmup bought in one place

Cold email infrastructure is normally four purchases and three dashboards. Here domains, mailboxes, warmup, and placement monitoring sit inside the workspace that does the sending.

try
Start freeRead the docs

Sending infrastructure is where outbound quietly dies. The domain is registered in one place, DNS is half right, mailboxes come from a second vendor, warmup from a third, placement checks from a fourth. Nobody owns the whole chain, so a bounce spike takes a week to explain and a month to recover from.

The fix is not a better vendor, it is one ledger. A managed order buys a domain and its mailboxes together, DNS arrives as a diff you read before applying, warmup attaches on provisioning, and health is reported per mailbox instead of per campaign, so the answer to a drop is an account name.

Example searches

Ask for it the way you'd say it

Each example is a request in plain words, with what it returns underneath.

  • Plan the DNS before touching it

    show me exactly which spf, dkim, dmarc and mx records this domain still needs

    The plan returns a create, update, keep, and conflict diff plus a hash, so applying it is a decision rather than a guess.

  • Buy the pool as a subscription

    order two more sending domains with four mailboxes each for next quarter

    Managed inboxes are provisioned as a monthly subscription, with warmup attached unless a mailbox opts out.

  • Find the mailbox hurting you

    rank my sending accounts worst first and tell me which ones to pause today

    Fleet health rolls the pool up by reputation and shows the per-mailbox scores behind the summary.

Plays

Three motions you can run this week

Each one is a chain of OXYGEN primitives — the same hosted objects your workspace already has, composed.

  • Stand up a pool that survives

    A new sending pool exists with correct DNS, attached warmup, and monitoring from day one.

    1. Sequences
    2. Observability
    3. Dashboards
    1. 1Subscribe to a managed domain with its mailboxes and let warmup attach on provisioning.
    2. 2Leave it warming for weeks before a sequence ever points at it.
    oxygen managed-inboxes subscribe

  • Get the DNS right the first time

    Records are compared against what the provider needs before anything is written at the registrar.

    1. Sequences
    2. Observability
    1. 1Run the plan and read the conflicts, which is where a half-migrated domain shows itself.
    2. 2Apply only once the diff says what you expected it to say.
    oxygen domains dns plan

  • Pull a bad mailbox before it spreads

    One degraded account is paused and rotated out instead of dragging the whole pool's reputation down.

    1. Observability
    2. Sequences
    3. Messages
    1. 1Read fleet health worst first and check the bounce evidence behind the score.
    2. 2Pause or rotate the sender, then let the rest of the pool carry the cadence.
    oxygen mailboxes health

Capabilities

What you get

  • One workspace, not 4 vendors

    Domains, mailboxes, warmup, and monitoring are bought and billed inside the workspace, in the same credits as everything else you run here.

  • DNS as a reviewable diff

    The record plan is read-only and returns create, update, keep, and conflict entries with a hash of what it saw. Applying it is a separate, approved step bound to that hash.

  • Warmup that ramps the sender

    A new mailbox builds history before it carries volume, and the sender's daily cap rises with it. A cadence cannot borrow capacity the mailbox has not earned.

  • Health you can act on

    Bounce thresholds pause a mailbox as product state. External placement scores sit beside that as advisory evidence, clearly labelled as directional rather than a verdict.

Boundaries

What Sequences does not own

Sequences owns sending and the infrastructure under it. It does not own the conversation, which is Messages, and it does not build your list: sourcing, enrichment, and qualification are Tables. Buying capacity never implies permission to send.

Data sources

Data sources and CRM connections

  • Mailforge

    Managed cold-email domains and mailboxes bought inside the workspace instead of from a registrar plus a separate mailbox vendor.

  • Primeforge

    Google Workspace mailbox provisioning for a pool you want on Google rather than a dedicated cold-email host.

  • Zapmail

    A second provisioning path for domains and mailboxes when a pool should not sit with one supplier.

  • OXYGEN Warm-up

    Warm-up on connected sending accounts, so a fresh mailbox builds a history before it carries a campaign.

  • Warmforge

    Warm-up on the Forge stack, attached to managed orders by default unless a mailbox opts out.

  • OX

    OXYGEN deliverability

    Placement tests and reputation monitoring per mailbox, which turns a vague deliverability worry into a named account.

Use managed credits where available, or connect a supported provider key on an eligible paid plan. Your provider bills its calls; OXYGEN adds a per-call platform fee. Signed-in CRM connections such as HubSpot have no per-call fee. Connected sending accounts reserve monthly credits. See pricing and supported integrations.

Limits

Where this stops

  • External placement data is directional, not a ruling. Bounce-driven auto-pause is authoritative product state you can act on; a placement score is evidence you weigh against it.
  • Buying infrastructure costs credits. A free workspace can plan DNS, read fleet health, and buy domains, warm-up or placement tests with credits; adding a mailbox, bought or your own, needs a paid plan.

FAQ

Questions people ask first

Do I have to buy domains through OXYGEN?
No. Register mailboxes and domains you already own in bulk and they behave like managed ones for warmup, health, limits, and sequences. What a bring-your-own mailbox does not escape is the monthly connection fee every sending mailbox pays, listed on the pricing page. Buying here removes the vendor sprawl and the second invoice, not the per-mailbox cost.
What does a managed mailbox cost per month?
It is a monthly price in credits with warm-up included, and optional deliverability monitoring adds to it. The pricing page lists both, and the order preview shows the recurring commitment in full before you buy.
How long should a new mailbox warm up?
Weeks, not days. Warmup runs per mailbox with a ramp, and the sender's daily cap rises as it matures. Pointing real volume at a cold mailbox is the fastest way to burn a fresh domain.
What happens when a mailbox starts bouncing?
Bounce thresholds pause it automatically and the pause is visible on the sender as state, with the evidence behind it. Sequences keep running on the healthy part of the pool rather than stopping outright.
Can I check DNS without changing anything?
Yes. The plan is a read: it returns create, update, keep, and conflict entries with a hash of what it observed. Applying those records is a separate, approved step.
Can I leave without losing the domains?
Yes. The exit path stops every OXYGEN renewal on a managed domain at the end of the period you already paid for and leaves the domain, its mailboxes, DNS, and warmup state exactly as they are, while a person coordinates the registrar handoff with the vendor. Cancelling is the other command and does tear the inboxes down, so read the plan before choosing. Sending history and provenance stay in your workspace either way.

Run domains, mailboxes, and warmup bought in one place on your own workspace

Sign up, get a working workspace with a one-time credit grant, and run the first play from the web app, the CLI, or your AI assistant over MCP.

Start freeSee pricing