Everything Mailbase ships — one focused tool per page.
We didn't build a marketing suite. We built the email primitives a builder actually needs: A/B testing, a real reply inbox, MJML templates, and an MCP server for AI clients. Each one has its own page.
Prospecting that starts from the French company register
Name your customer. Mailbase finds every matching company in the register, finds who to write to, verifies the email, writes one email per person, and sends a few a day — after you approve.
Read the pageA/B testing that picks the winner for you
Pilot a slice of the audience, let Mailbase choose the winner by reply rate, roll the winner out to the rest in one click.
Read the pageRead every reply, sorted the way an inbox should be
A real inbox for outbound email: hot leads, needs reply, auto-handled, with tags you actually control.
Read the pageAI that answers where you're working
Ask for a reply and the draft lands in the reply box. Ask for campaign copy and it lands in the composer. Nothing sends until you press send.
Read the pageMJML templates with a live preview that's actually live
Visual section editor, MJML source view, brand kit, version history, content checks — and a preview that renders the same MJML your recipients will receive.
Read the pageMailbase keeps these pieces in one workflow so they reinforce each other: campaigns and A/B tests share the same MJML templates and brand kit, the reply inbox threads responses back to the contact who got the send, and analytics, suppression, and deliverability controls apply on every send automatically. Nothing here is a bolt-on — it’s one tool that understands the whole lifecycle of an email.
The prospecting engine sits in front of all of it: name your customer, and every matching company in the French register is found, its email verified on its own site, and one email written per person — then the replies land in the same inbox. Every capability is also reachable over the REST API, so you can drive the same workflow from your backend. Use managed Mailbase sending, or bring your own useSend stack when you want to own delivery.
New here? The fastest way to understand Mailbase is to open the feature closest to your current pain — subject-line testing, a clogged reply inbox, fragile templates, or wiring email into an AI workflow — and read how that one piece works. Each page shows the real surface, the controls you get, and where it connects to the rest of the stack. Start free with managed sending, or point Mailbase at your own useSend instance whenever you’re ready to own delivery.
Open the one closest to your problem.
Every feature is free to try on the starter allowance — managed sending, no card, and your own useSend whenever you want it.