Start with useSend: the strongest Mailbase integration page for teams choosing hosted Mailbase sending or a BYO useSend stack.
Mailbase is built to sit on top of the sending layer you choose instead of locking you into one. The integration pages below explain how Mailbase connects to email infrastructure in practice: use managed Mailbase sending after you verify a sender domain, or bring your own useSend instance — self-hosted on Docker, Coolify, or Railway and backed by Amazon SES — when you want to own the delivery layer outright. Either path gives you campaigns, a shared reply inbox, analytics, and suppression on delivery.
The useSend integration is the best starting point for most teams: it pairs a Resend-style developer experience with infrastructure you control, then layers Mailbase’s workflow on top. Each page below covers what you need to wire up — API keys, domain authentication, and SES event handling — so you can move from first send to a production-ready stack without guessing.
Picking a sending model is reversible, so you don’t need to get it perfect on day one. Many teams start on managed Mailbase delivery to ship quickly, then move to a bring-your-own useSend stack once volume and deliverability matter enough to own outright — the workflow on top stays identical either way. The pages below walk through domain authentication, SPF, DKIM and DMARC records, API keys, and Amazon SES event handling, so whichever path you choose, the setup is documented end to end.