Zexr is the platform for email warmup and cold outreach. Everything that decides whether your email lands in the inbox is documented, and every decision it makes about a mailbox comes with a reason.
For years the main tools for cold email have charged by the mailbox while keeping their warmup logic, sending rules and abuse thresholds closed. You paid for volume. You never got to see how decisions about your reputation were made.
We started Zexr to change that. The warmup pools, the sending limits and the health rules are documented, and they hold every mailbox to the same standard.
So when Zexr slows a mailbox down, the dashboard says why in a full sentence, and says what has to change for it to recover. The figure beside this is a real one: the reason a throttled mailbox shows.
Founders, agencies, sales teams, recruiters and fundraisers get unlimited mailboxes and warmup on every paid plan, and stop paying a tax on every mailbox they add.
We are a small team. We say what we are working on, we don’t invent numbers, and every change that ships lands in a dated changelog.
When deliverability breaks on a platform that gives no reasons, you can’t see what went wrong. You can only write to support and wait.
These aren’t values for a slide. They are built into the product, and a feature that breaks one doesn’t ship. Each pair below sits next to the screen or the record that shows it.
Every health state, suppression and pool block comes with a reason you can read in the dashboard, and the rules behind them are documented.
The changelog is public and dated, and every entry is a change that reached production. We don’t invent metrics or pretend to be bigger than we are.
A safe day of sending is the sum of what each mailbox can safely send. We will not ship a feature that pushes a mailbox past its own limits to make a chart look better.
Our thresholds for the shared warmup pool are stricter than the points where Google or Amazon SES start penalising a sender. By the time a provider would act, the mailbox has already been slowed down.
Mailbox credentials are encrypted with a dedicated credentials key, and message content with a data key that belongs to your workspace alone.
Export your whole workspace from Settings at any time, as one archive.
Adding capacity means adding small workers, not growing one giant server. Your mailbox provider delivers the mail, so a worker is only where your mailbox signs in from, and Zexr keeps that stable.
The backend and consumer hold your data, decide which mailbox sends what and when, and assign each mailbox to a worker.
Commands go out on a topic per worker and results come back on one shared stream, over NATS or Kafka.
They sign in to your mailboxes, send, sync and report back. They hold no database connection, so one that goes away is simply replaced.
| Zexr | Other tools | |
|---|---|---|
| Decisions | Every pause, suppression and block shows its reason. | A status flag and a support ticket. |
| Replies | An AI agent answers from your playbook, or drafts for review. | Often a separate tool. |
| Health rules | Documented, and stricter than provider enforcement. | Undocumented until something goes wrong. |
| Changelog | Public and dated, one entry per shipped change. | Announcements on a marketing schedule. |
| Pricing | Per workspace, with unlimited mailboxes and warmup. | Often per mailbox or per seat. |
This describes how Zexr is built. We don’t speak for any other company’s plans or pricing.
Start free on Zexr Cloud. Connect a mailbox and start warming it today.
