Self-host inboxes
Run the full stack on your own server. Same product as the cloud version - your data never leaves your infrastructure.
git clone https://github.com/inboxesnet/inboxes.git && cd inboxes
cp .env.example .env
docker compose up -dWhy self-host?
Data ownership
Your emails, your API keys, your database. Everything stays on your infrastructure.
No lock-in
Open source, standard Postgres. Export your data anytime. Leave whenever you want.
No recurring cost
Run on a $5/month VPS or a spare machine in a closet. No per-seat pricing.
Runs anywhere
Docker Compose on any Linux server, Coolify, Railway, bare metal - your choice.
Why inboxes?
API key stays on your server
Your Resend API key is encrypted at rest and never leaves your instance. We never see it.
Auto-poll mode
No public URL? No problem. Enable auto-polling to sync emails from Resend without webhooks.
Invite-only by default
No open signup page. You control exactly who has access to your instance.
Same features as cloud
Threading, search, scheduled send, undo send, snooze, rules, signatures, the MCP server - everything works.
Cloud or self-hosted. Same product.
Self-Hosted
Your server, your data
Ready to deploy?
Follow the deployment guide for step-by-step instructions. Takes about 5 minutes.