Principles we build by.
Not taglines we hide behind.
Reloop is built on absolute transparency. These six principles guide every feature we design, the code we open-source, and how we protect your developer independence.
How we decide
what ships.
No poster on a wall. Rules we use when choosing features, defaults, and what stays open source.
Show the work
Source code, pricing, and routing logic you can read—not trust on a sales call.
Ship what you ask for
GitHub issues and community PRs drive the roadmap—not a closed quarterly plan.
Never stop at good enough
Every release should make sending email faster, simpler, or easier to debug.
Security you can verify
Open code, self-hosting, and auditable routing—because email is critical infrastructure.
Complexity is a bug
If it's hard to deploy, debug, or leave—treat that as a defect, not a feature.
Built for builders
Typed SDKs, clear docs, and SMTP that works with the stack you already run.
In practice
Promises you can
check in GitHub.
Three ways these values show up in the product—not just on this page.
Open source by default
The product and the process are public.
- Apache 2.0 codebase on GitHub
- Issues and PRs in the open
- Same code—hosted or self-deployed
You steer the roadmap
We prioritize what teams actually need in production.
- Feature requests tracked publicly
- Bugs filed and fixed in the open
- Outside contributors welcome
Trust through visibility
You shouldn't wonder how email leaves your app.
- Routing logic readable in source
- Deploy on your own servers
- Clear logs when a send fails
See the principles in code
not a slide deck.
3,000 emails per month free—or clone the repo and run Reloop on infrastructure you control.