Deliverability

Built to stay out of spam

Deliverability isn't a feature bolted on afterwards — it's the reason the infrastructure is shaped the way it is. Here is everything standing between your sequences and the spam folder.

The stack

Six layers between you and the junk folder

Dedicated IPs, never shared

Every customer sends from their own IP, signs with their own DKIM key, and bounces and tracks on their own domains — none of it shared with another customer. The reputation objects receivers actually score are yours alone, which is not true of shared-pool providers.

Authentication on every domain

SPF, DKIM, DMARC and custom tracking DNS are set on each domain before it sends a single email, following current provider guidance from Google and Microsoft.

Managed warmup, no shortcuts

Every mailbox starts on a low daily cap that we raise only while the signals stay clean — bounces, complaints and where your mail actually lands. A domain is cleared for full volume after it holds 90%+ inbox placement across three checks. A fleet that skips the ramp lands in spam, which defeats the point of paying for infrastructure.

90+ blacklists watched continuously

Every domain and IP is checked against 90+ public blacklists. A listing is caught by monitoring, not by your reply rate falling off a cliff a week later.

Auto-pause and swap when a domain burns

The moment reputation dips, the affected domain is paused and a fresh, warmed replacement is rotated in. You keep sending on the healthy remainder.

Enforced sending caps

Per-mailbox caps are enforced at the server, not left to discipline. Blowing through safe volume is the fastest way to burn a fleet, so the platform simply doesn't allow it.

FAQ

Deliverability questions

Why do dedicated IPs matter for cold email?

On a shared IP pool your deliverability depends on the worst sender in the pool. One spammer can get the whole range throttled or blacklisted, and you inherit the damage. With a dedicated IP per customer, your reputation is built by your sending alone — and protecting it is a matter of following the ramp and caps, which we enforce.

What does the warmup actually involve?

Each mailbox starts at a low daily cap and sends your real campaign from day one. We raise the cap step by step — never more than 20% a day, and only while bounces, complaints and placement stay clean — and test where your mail lands every few days against real Gmail and Microsoft 365 inboxes. We do not fake opens or replies: providers detect manufactured engagement and it can leave a domain worse off than no warmup at all. Full volume typically arrives in 2–3 weeks.

How do you know when a domain is burning?

Continuous checks across 90+ blacklists plus reputation signals from the receiving providers. When a domain trips a threshold it is paused automatically and a warmed replacement joins the rotation — you don't have to notice the problem yourself.

Will this protect my main company domain?

Yes — that's the core of the model. All cold volume goes through lookalike domains we buy on your behalf, so your primary domain never touches a cold list. If a lookalike burns, it's swapped; your main domain's reputation is never in play.

Does deliverability depend on which sequencer I use?

The infrastructure is sequencer-agnostic. Logins are handed over ready for Instantly, Smartlead or any tool that connects over standard protocols. Sending caps and monitoring stay enforced at our end regardless of what you plug in.

Sending infrastructure that defends itself

Pick a mailbox count and we'll set up domains, DNS, warmup and monitoring — then hand over the logins.