Integrations
Cladiant + Bison
Real enterprise mailboxes wired into your own EmailBison instance.
Bison (EmailBison) is a self-hosted-style cold email sending platform run on your own sending domain.
Bison gives you a self-hosted sending layer; Cladiant gives it real, authenticated mailboxes. We provision Google Workspace, Microsoft 365, and Azure Entra accounts, verify DNS and authentication on every domain, and wire them into your Bison instance by URL.
Because the mailboxes are real enterprise accounts on dedicated Azure tenants, your Bison sending sits on infrastructure built for deliverability, not a shared pool you cannot see into.
The handoff
How Cladiant hands off to Bison
Cladiant connects mailboxes to Bison with the username, password, API key, workspace, and your Bison platform URL, so provisioning lands on your own EmailBison instance.
Division of labor
Two layers, zero overlap
Bison runs the campaign. Cladiant runs the infrastructure it sends from. Neither does the other's job, which is exactly why they fit together.
Cladiant handles
- Google Workspace, Microsoft 365, and Azure Entra mailboxes
- Domain purchase plus SPF, DKIM, and DMARC on every domain
- A dedicated Azure Entra tenant per domain
- Deliverability monitoring that pulls a bad inbox to warmup
- Month-to-month billing on one invoice
Bison handles
- Sending from your own EmailBison instance
- Step-level A/B testing and spintax
- Placement testing before launch
- Unified reply management and full API
Setup
From order to sending
- 01
Tell us your volume
Say how many emails a day you need to send. We size the mailboxes and domains so no single inbox or domain is overloaded.
- 02
We provision and authenticate
Real Google Workspace, Microsoft 365, and Azure Entra mailboxes, with SPF, DKIM, and DMARC written and verified on every domain before anything sends.
- 03
Connect to Bison
We hand the accounts to Bison using the credentials it expects, including a Microsoft OAuth link for Azure inboxes, so they land in your workspace ready to send.
- 04
Set safe limits and launch
Cap daily volume per mailbox, keep warmup running, and keep bounces low. Your campaigns run; we keep the infrastructure healthy underneath.
Sizing it
How many mailboxes you need
A safe cold-email cadence is 20 to 40 sends per mailbox per day across a few mailboxes per domain, with new mailboxes warmed up over two to four weeks and bounce rate kept low. A target of 1,000 sends a day works out to roughly 30 to 40 mailboxes across a dozen or so domains, and Bison rotates across them for you.
What you get
Infrastructure built for the inbox
01
Three real providers
Google Workspace, Microsoft 365, and Azure Entra in one order, not a single-source SMTP relay.
02
Authenticated before sending
SPF, DKIM, and DMARC written and verified on every domain before a mailbox goes live.
03
Dedicated Azure tenants
Every Azure domain in its own tenant, so your reputation is never pooled with other senders.
Troubleshooting
When something goes wrong, who fixes it
Most cold-email problems are either a sequencer problem or an infrastructure problem. Here is how to tell them apart, and which layer owns the fix.
| Symptom | Likely cause | How it gets fixed |
|---|---|---|
| Emails landing in spam on seed tests | A DNS or authentication gap, or a blacklisted domain | Cladiant re-checks SPF, DKIM, DMARC and reputation, then remediates or replaces the domain |
| Reply rate declining over several weeks | Domain or inbox reputation wearing down | Cladiant rotates sending to rested mailboxes and warms the affected ones back up |
| Bounce rate climbing above 2 to 3 percent | List quality, not infrastructure | Pause and re-verify the list before sending more; suppress hard bounces in the sequencer |
| Good deliverability but low replies | Copy or targeting, not infrastructure | A/B test messaging in your sequencer; if a plain-text version also lands in spam, it points back to infrastructure |
| A sudden drop across many inboxes at once | A shared-reputation or tenant-level problem | Isolated Azure tenants contain the blast radius, so Cladiant investigates only the affected tenant |
FAQ
Bison + Cladiant, answered
Does EmailBison come with mailboxes?
No. EmailBison is the sending layer that runs on your own instance; it does not provision mailboxes. Cladiant supplies real Google Workspace, Microsoft 365, and Azure Entra accounts, authenticated end to end, and wires them into your Bison instance.
How do I connect mailboxes to my EmailBison instance?
Cladiant connects mailboxes to Bison using the username, password, API key, workspace, and your Bison platform URL, so provisioning lands on your own EmailBison instance rather than a shared account.
Can I run Outlook and Azure Entra inboxes on EmailBison?
Yes. Cladiant provisions Microsoft 365 and Azure Entra alongside Google Workspace, so your Bison sending is not locked to a single provider. Each Azure domain runs in its own dedicated tenant for isolation.
How many mailboxes do I need for EmailBison?
EmailBison is built for higher volume, and a safe cadence is still 20 to 40 sends per mailbox per day across a few mailboxes per domain. Our free volume calculator turns your daily target into a mailbox and domain count.
Does Cladiant handle warmup for EmailBison?
Cladiant provisions and authenticates the mailboxes and monitors deliverability; warmup runs through your warmup tool or EmailBison alongside it. New mailboxes should warm for two to four weeks at a 2-to-1 ratio before full-volume sending.
Why use real mailboxes instead of shared infrastructure with EmailBison?
EmailBison markets double-isolated infrastructure, and it is only as strong as the accounts behind it. Cladiant gives you real enterprise mailboxes on dedicated Azure tenants, so your Bison sending sits on infrastructure built for deliverability rather than a pool you cannot see into.
Ready to run Bison on real infrastructure?
One order. One invoice. Mailboxes provisioned across three providers and connected straight into Bison.