One platform for
every client domain.
Each client gets their own workspace, so their mailboxes, analytics and suppression lists never mix. Switch between clients in one keystroke and bill them all from a single account.
Your whole client roster, one login.
Every client gets a workspace of their own, with separate mailboxes, warmup and analytics. Open any client from the switcher, and bill them all from one account.
One client never touches another.
It's not a dashboard filter. Each of these is a real boundary in how the data is stored, so a problem in one client's account can't reach another's.
Sender pool
mailboxes + workersEach workspace owns its mailboxes, its warmup-pool membership and its worker assignment. Nothing is shared across clients by default.
Warmup pairing
premium poolA mailbox that trips the quarantine band recovers inside its own workspace and never warms against another client's inboxes.
Suppression
per workspaceBounces, complaints and unsubscribes are stored per workspace, so one client's do-not-contact list can never block another client's sequence.
Analytics + API
per workspaceSends, replies, placement and complaint rate, plus API keys and webhooks, are scoped to the workspace. Each client sees only their own numbers.
Shared premium pool, or dedicated IPs per client.
Every paid workspace warms and sends on the shared premium pool. When a client grows big enough to want its own IPs, move it onto dedicated workers, each on its own machine, sending only that client's mail.
Shared premium pool
Clients warm on the vetted premium pool and send through shared premium workers, so the volume is spread across many machines and IPs from day one. Nothing to set up.
- Vetted, monitored premium warmup pool
- Volume spread across many worker IPs
- Quarantine bands protect the shared pool
Dedicated workers & IPs
Give a client its own workers, one per machine, each with its own IP, sending only their mail. Their sending reputation stands on its own.
- One worker per machine, its own IP
- Safe volume = the sum of that client's mailbox caps
- Rebalance or migrate mailboxes without downtime
Spreading sends across many machines, each with its own IP, is safer than pushing everything through one.
Every client starts on safe sending limits.
The conservative defaults are on for every workspace, and the platform keeps them there. Raising a limit takes a deliberate change, so one mailbox or one client can't quietly drag down everyone else's deliverability.
You pay per workspace, not per seat.
Billing is per client workspace, and seats are free, so adding a BDR, an AE or a QA reviewer never changes what you pay. You set the client's price; we invoice you per workspace.
One subscription per client. Agency owner pays, marks up however they want.
Add the BDR, the AE, the QA reviewer. Seat count never changes the bill.
Each plan sets how many mailboxes a workspace gets. Add more workspaces to add capacity across clients.
Every paid workspace warms on the premium pool, under the same quarantine bands as the rest of your clients.
You bill the client, we bill you per workspace, and the difference is yours.
You take one workspace per client, on whatever plan that client needs. Charge the client whatever your contract says, and keep the difference.
Questions agencies ask first.
Still have questions? Talk to our team about rolling this out across your clients.
No. Workspaces are sender-pool isolated. A mailbox that hits the quarantine band drops into recovery inside its own workspace and never participates in warmup pairs against mailboxes from a different client workspace.
As many as you subscribe to. Each client is its own workspace with its own subscription, and workspaces stack, so capacity scales with the roster instead of with a seat count.
You own every workspace subscription as the agency. Clients do not see a Warmbly invoice unless you transfer ownership. Mark up whatever you want at the agency level.
Yes. By default every paid workspace shares the premium warmup and worker pool. For a client that needs its own reputation surface, you can move it to dedicated workers, each its own machine and IP, carrying only that client's mail.
It steps down the health ladder (Healthy, Watch, Quarantined, Blocked) and is pulled from the shared pool well before mailbox providers penalize it, acting around 10% spam placement rather than 80%, then recovers inside its own workspace.
Yes, on Grow and Business. Roles let you invite the client read-only or scope them to just their workspace, while keeping billing and worker config on your side.
Run every client's outbound from one account.
Connect a mailbox, warm it up, send your first campaign today.