CherAmiOwn your email engine.
Cold outreach, newsletters and lifecycle automation from one platform on your own server: through your domains, your mailboxes and the sending providers you already use.
- Status
- In development · closed beta 2027
Overview
CherAmi runs cold outreach, newsletters and lifecycle automation from one platform. It installs with Docker Compose and keeps contacts, templates and send history in an embedded SQLite database on a server you control.
Cold mail goes out through your own mailboxes; newsletters and automation through SendGrid or Amazon SES. Replies from every mailbox come back to one Unibox, the way a homing pigeon finds its loft. The name comes from one: Cher Ami, the pigeon that kept flying in 1918.
What it does
Many mailboxes, one platform
Connect SMTP/IMAP mailboxes in bulk from a CSV file or link Google Workspace with OAuth. SendGrid and Amazon SES carry newsletters and automation.
Pacing and guardrails
Sends are paced per sender and interleaved by recipient provider. A sender pauses itself when its bounce or complaint rate crosses your threshold.
Preflight checks
A campaign can’t start with broken merge tags, a missing unsubscribe path or other blockers. The report shows exactly what to fix.
Previews that tell the truth
Spintax and Liquid merge tags, chosen deterministically per recipient, so the preview is what gets sent. Seed tests and a preview matrix before anyone receives it.
Sequences and one Unibox
Multi-step sequences stop when a contact replies, and out-of-office answers don’t count. Every reply lands in one inbox.
Automation and API
Event-driven flows, behavioural segments and RFM lifecycle stages, plus a REST API with scoped keys for your app or CRM.
How it’s built
TypeScript end to end: Node.js on the server, React in the browser and an embedded SQLite database, shipped as Docker Compose behind a reverse proxy with automatic HTTPS.
- TypeScript
- Node.js
- React
- SQLite
- Docker
Where it stands
Built
Sending, sequences, Unibox, automation and analytics.
Now
Hardening, testing and running it on our own infrastructure.
2027
Closed beta with a small group of teams and agencies.
2027
Public launch planned.
Why I’m building it
I’ve run sending for hundreds of domains and thousands of mailboxes, on self-hosted tools and managed platforms side by side, and compared them on deliverability, control, data ownership and operating cost. CherAmi is what I took from that comparison: the infrastructure, the data and the rules should stay with whoever does the sending.
What it isn’t (yet)
- Not a warm-up network: reputation comes from your own sending.
- Not a lead database: bring your own lists.
- Not a hosted service: you run it on your server.