Run a custom-domain inbox with Resend and S3.
Resend Inbox keeps the same operator workflow but swaps Cloudflare bindings for Resend receiving/sending APIs, S3-compatible storage, and a Dockerized Node runtime.
Build and run the Docker image from source.
Use the GHCR image once the repository is published.
Deploy on any container host with HTTPS for the Resend webhook.
Point Resend email.received webhooks at /webhooks/resend.
Resend Receiving webhooks
Receive inbound messages through Resend and verify every webhook before fetching content.
Resend Email API
Send forwards, replies, and magic-link auth messages through the same provider.
S3-compatible storage
Store raw EML, normalized JSON, attachments, reply aliases, and inbox settings.
Docker runtime
Run the Waku Node server anywhere that can provide env vars and object storage.
Best for non-Cloudflare deployments
Pick this version when you want Resend's receiving/sending workflow and the freedom to run the inbox on any container host.
Bring your own object storage
Use AWS S3, Cloudflare R2's S3 API, MinIO, or another compatible bucket for the inbox archive.