Self-host Sendvery free, forever
Every line of code is public. Run it on your own server with one docker-compose command — no limits on domains, users, or features. Or let us run it for you.
Self-host in 60 seconds
Three commands. Then open http://localhost in your browser.
Clone the repo
Grab the source. Anything you see on the hosted site is in this tree — no closed-source bits.
git clone https://github.com/janmikes/sendvery.git && cd sendvery
Configure your .env
Copy the template and fill in a database URL plus your inbox credentials. Defaults work locally out of the box.
cp .env .env.local && $EDITOR .env.local
Boot the stack
One command brings up the app, PostgreSQL, and the Messenger worker. Open http://localhost and sign in with the magic link sent to Mailpit.
docker compose up -d
Self-host vs Hosted
Same product. Pick the deployment model that fits.
| Self-host | Hosted (sendvery.com) | |
|---|---|---|
| Cost | Free forever — your server, your bill. | From $0/mo (Free plan, 1 domain). |
| Time to set up | ~60 seconds with Docker. | ~2 minutes (signup + add domain). |
| Auto-updates | You pull new images on your schedule. | Always on the latest release. |
| Backups | Your PostgreSQL, your backup strategy. | Daily managed backups included. |
| AI insights key | Bring your own Anthropic API key. | Included on AI plan tiers. |
| Support | Community via GitHub issues. | Email support; SLA on Business. |
| Data ownership | 100% on your infrastructure. | On our infrastructure; export anytime. |
Why AGPL-3.0?
The same license that protects Grafana, MongoDB, and Nextcloud — picked deliberately.
AGPL-3.0 grants you four freedoms: use the software for anything (including commercially), study how it works, modify it, and share it. The one obligation it adds is reciprocity: if you offer a modified version of Sendvery to other people as a network service, you have to publish your modifications under the same license.
In plain language — what you can do:
- Self-host privately for your company, team, or yourself — no obligations to anyone.
- Fork and modify for your own use — even commercially, as long as the modifications stay with you.
- Embed it inside other internal tooling, agencies, MSP stacks — all fine.
What AGPL does NOT let you do:
- Take Sendvery, modify it, and resell it as a closed-source SaaS without publishing your modifications.
- Strip the copyright headers or relicense the source under a more permissive license.
For 99% of users this means absolutely nothing changes: download, run, use. The license exists so that a competitor can't take this work, close-source their fork, and turn around to sell it — that's the whole reason it's possible to give the code away for free in the first place.
What's in the repo?
A quick tour of the codebase. Tests are the spec — 100% line coverage is enforced in CI.
src/
Application code — CQRS commands and queries, Doctrine entities, Twig components, Stripe + Stimulus + Turbo wiring.
docs/
Architecture decisions, features roadmap, monetization model, pricing implementation plan. Every product decision is documented before it ships.
tests/
Unit + Integration tests. Behaviour-driven — the test names are the business requirements. Mutation testing via Infection.
Pick your path
Self-host stays free forever. Hosted saves you the infrastructure work.
Source on GitHub: https://github.com/janmikes/sendvery