About Reloop Labs
We build open-source email infrastructure—use our hosted service or self-host. Transparent, developer-first, free from vendor lock-in.
What we stand for
Six pillars
we live by.
These aren't slogans—they're the decisions we make when we write code, review PRs, and design APIs.
Radical simplicity
Email infrastructure that just works. One API, clear SDKs, and a stack you can understand—not a maze of opaque services.
Open by default
Every line of code is public under Apache 2.0. Audit it, fork it, use our hosted service, or self-host on your servers.
Your choice of deployment
Use Reloop hosted by us or run it on your network. No vendor lock-in—same open-source platform either way.
Developer-first
Type-safe SDKs, predictable APIs, and documentation written for engineers shipping real products.
AI-ready
Agent inboxes, structured parsing, and webhooks built for autonomous workflows—not bolted on later.
Community-driven
We're in the early days, building in public. Issues, discussions, and contributions shape what comes next.
Our story
Built out of frustration.
Refined in the open.
Developers shouldn't have to choose between expensive proprietary vendors and opaque self-hosted setups. Reloop is our answer—the same service as proprietary platforms, with an open-source codebase you can use hosted or self-host.
We started
Reloop Labs began in September 2025 with one goal: open-source email infrastructure that's transparent and self-hostable.
Building in the open
We've been heads-down on the codebase—APIs, self-hosting, agent inboxes—and sharing progress on GitHub and Discord.
Still shipping
We're not done yet. The product is actively in development, and we're polishing everything for launch.
Launching next month
Public launch is planned for July 2026. Follow along on GitHub—or get started with hosted or self-hosted builds today.
Questions? Reach us at reloop.sh@gmail.com.
Join us in the open
Contribute on GitHub.
Star the repo, open an issue, or join our Discord community—we're building Reloop together.