We built the email
infrastructure we couldn't buy.

Password resets, receipts, onboarding, campaigns—email shows up in every product we ship. The options never felt right. Pay a proprietary vendor and trust routing logic you can't read. Or roll your own SMTP and pray deliverability holds when traffic spikes.

Bills climbed. Black-box routing stayed black-box. At 2 a.m. with failed sends, the only thing to debug was a status page. We wanted what you probably want too: production-grade email you can audit, self-host, and actually understand.

Two engineers, one bet: build the full stack—not a thin API wrapper. Transactional sends, campaigns, SMTP relay, webhooks, analytics. The same capabilities as closed platforms, released under Apache 2.0 from the start.

No stealth mode. No pitch deck. Issues on GitHub, progress in Discord, code anyone could clone and run. If we were going to fix email, we were going to do it where you could watch—and verify.

APIs and SDKs. Docker-based self-hosting. Agent inboxes for AI workflows. Deliverability tooling with logic you can trace in source. Every feature landed in one codebase—whether you deploy it yourself or use reloop.sh.

Reloop Labs maintains that codebase and runs the hosted service. Same software, your choice of deployment. That wasn't a marketing line. It was the requirement.

Sign up and send 3,000 emails per month free—or clone the repo and run it on infrastructure you control. No enterprise fork. No features held for a sales call. Read every routing decision before you trust it.

We're a team of two, shipping weekly, with a public roadmap. Early days—but the foundation is open, the stack is real, and we're not going back to closed email.