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
Volume ramps daily for 14–21 days and nothing is handed over early. A fleet that skips warmup 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 volume and ramps up over 14 to 21 days, with sends, opens and replies that look like normal correspondence to the receiving providers. Handover only happens once the fleet holds its reputation at target volume.
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.