Open source, for real
MIT licensed. No open-core split, no enterprise edition, no delayed releases. The cloud runs the same code you can read.
License
CamelMailer is released under the MIT license. You can use it commercially, modify it, embed it, and redistribute it. The only requirement is keeping the license notice.
Heritage
CamelMailer began as a ground-up Rust rewrite of Postal (also MIT), the long-standing open-source mail platform. We kept its proven protocol behaviour — the SMTP state machine is a line-for-line port, verified by the original test suite — and replaced the runtime: one Rust binary, one PostgreSQL database with row-level-security tenant isolation, and a new API surface focused purely on transactional mail.
What "the same code" means
- Every feature on the cloud exists in the repository. There is no private fork with the good parts.
- Migrations, the dashboard, the template library, the OpenAPI spec — all in the open.
- If we ever disappear, your exit is
git clone+docker compose up.
Contributing
- The workspace is a standard Cargo monorepo; the frontend is Vite +
React.
cargo testruns the whole suite — PostgreSQL integration tests included whenCAMELMAILER_TEST_DATABASE_URLis set. - Every behaviour is covered by tests; contributions are expected to keep it that way (the project was built test-first).
- CI enforces
cargo fmt,clippy -D warningsand the full test suite.
Security
Report vulnerabilities privately to security@camelmailer.example. We ask for reasonable disclosure time and credit reporters in release notes. Please do not test against the cloud without permission — spin up your own instance instead; it's the same code.
Trademarks
"CamelMailer" and the camel logo identify the project and the managed cloud. Run your own instance under any name you like; just don't imply your service is operated by us.