Repository navigation
FAQ
Inbix is an open-source disposable email platform that runs entirely on Cloudflare Workers. It lets you generate temporary email addresses, receive emails, and read them in a modern web dashboard — all without managing SMTP servers, Docker containers, or VPS instances.
Yes. Inbix is MIT-licensed open source. Cloudflare's free tier provides 100K Worker requests/day, 5M D1 reads/day, and 10GB R2 storage — more than enough for personal or small-team use.
Most disposable email services are hosted by third parties. You don't control the data, the domain, or the uptime. Inbix is self-hosted on your own Cloudflare account — you own the data, the domain, and the infrastructure.
Basic Cloudflare knowledge helps (creating a D1 database, R2 bucket, enabling Email Routing). The deployment guide walks through every step. If you can run git clone and pnpm deploy, you can run Inbix.
Yes. Cloudflare Email Routing requires a domain managed by Cloudflare DNS. You can register a domain through Cloudflare Registrar or transfer an existing domain.
Yes. Add domains via the API (POST /api/domains) or configure them in the dashboard. All domains must have Email Routing enabled and pointed to the Inbix Worker.
By default, 24 hours. You can customize the TTL when creating an inbox (1 minute to 7 days). Expired inboxes and their messages are automatically deleted.
Attachments are stored in Cloudflare R2 (object storage). Metadata (filename, content type, size) is stored in D1. Attachments are downloadable via the API and dashboard. Max size: 10MB per attachment, 20 attachments per message.
Yes. All HTML is sanitized through a custom pipeline that strips scripts, dangerous CSS, and unsafe URLs. The sanitized HTML is rendered in a sandboxed iframe with a strict Content-Security-Policy.
The dashboard uses Server-Sent Events (SSE). When a new email arrives, the Worker stores it in D1, and the SSE connection polls for new messages and streams them to the dashboard instantly.
Yes. The REST API is fully functional standalone. Use it for automation, CI/CD pipelines, or custom integrations.
Yes. The API is designed for automation. Generate an inbox, use it in your test suite, poll for messages, and delete it when done — all via the REST API.
Not currently. Inbix is Cloudflare-native by design, using D1, R2, KV, and Email Workers. A version with alternative backends (PostgreSQL, S3, etc.) is on the roadmap.
For most users: $0/month on Cloudflare's free tier. For high-volume usage, Cloudflare Workers paid plan is $5/month and includes 10M requests.
Authentication is available via Clerk (for dashboard access) and API keys (for automation and MCP). For admin-level restrictions or network-level access control, you can also use Cloudflare Access (Zero Trust).
git pull origin main
pnpm install
pnpm db:migrate
pnpm deployAll data is in your Cloudflare account. D1 (metadata), R2 (attachments), and KV (cache) — nothing is sent to third parties.
D1, R2, and KV encrypt data at rest. Data in transit uses HTTPS/TLS. Cloudflare handles all encryption.
Cloudflare processes emails through Email Routing and Workers. While Cloudflare's infrastructure handles the data, your Worker code controls what is stored and how. Inbix only stores email content in your D1/R2 — no analytics, no logging of content.
Delete the D1 database, R2 bucket, and KV namespaces via Wrangler. Or set very short TTLs and let auto-expiration handle it.
See the Roadmap for the full plan.
Clerk authentication is available today. API key authentication is also implemented for automation and MCP. Admin dashboard with granular role-based access is planned for v1.0.
Webhooks for inbox and message events are already supported. You can create webhooks via POST /api/webhooks or the dashboard.
Yes, full-text search across messages is planned for v0.3.