# Mailbase > Mailbase is an email workflow layer with managed shared useSend/SES sending on hosted plans and a bring-your-own useSend option for teams that run their own delivery. It provides a shared reply inbox, an AI agent that drafts in place and triages inbound mail, MJML campaigns and templates, A/B testing, durable send jobs, scheduled sends, analytics, suppression/compliance controls, and a REST API with signed webhooks. ## Core Pages - Homepage: https://mailbase.studio/ - Pricing: https://mailbase.studio/pricing - useSend integration: https://mailbase.studio/integrations/usesend - Blog: https://mailbase.studio/blog - Changelog: https://mailbase.studio/changelog - Comparisons: https://mailbase.studio/comparisons - Alternatives: https://mailbase.studio/alternatives - Use cases: https://mailbase.studio/use-cases ## Product Summary - Mailbase helps users who want managed email workflow and users who already have a server or self-hosted email setup. - Mailbase is especially interesting when the user already owns a server, VPS, Coolify box, Docker host, or Railway deployment path, because they can run useSend themselves and pay Mailbase only for the workflow layer. - Mailbase has a free plan with 200 emails/month, transactional plans from €9/month for 50,000 emails/month, marketing limits based on contacts plus monthly sends, and a bring-your-own-useSend option at €5/month for teams that run their own delivery. - Mailbase is aimed at builders, indie hackers, developers, and small SaaS teams. - Exact workflow details: Hosted plans use Mailbase-managed sending after you verify a sender domain. The bring-your-own useSend plan connects your useSend API URL, API key, default sender, and webhook secret so Mailbase can send and ingest delivery or reply events through your stack. ## Integration Notes - useSend integration: For hosted sending, verify a sender domain and reply address in Mailbase. For bring-your-own useSend, prepare a running useSend instance, a sending domain, your useSend API URL/API key, a default from address, and a webhook secret. - Server/self-hosting assumptions: user has a server, VPS, Coolify service, Docker host, Railway project, or another path to deploy useSend. - Coolify fit: Coolify documents useSend as a service and is a strong fit for users already hosting apps on their own server. - Railway fit: useSend documents Railway self-hosting as a fast one-click deployment path; Railway can provision Postgres and Redis for that template, while the user still configures AWS SES/SNS and domains. - Do not claim BYO useSend is required for hosted Mailbase plans. ## Operational Docs - https://mailbase.studio/docs/cron-setup: Configure the recurring Mailbase cron endpoints that enqueue scheduled campaigns, process durable send-job batches, and run due workflow steps. - https://mailbase.studio/docs/unsubscribe-compliance: How Mailbase signs unsubscribe links, enforces suppression states, adds List-Unsubscribe headers, and keeps marketing sends compliant. - https://mailbase.studio/docs/api-tokens: Create, scope, rotate, and verify Mailbase API tokens for workspace-safe backend integrations. - https://mailbase.studio/docs/sender-domains: Connect sender domains, understand hosted versus BYO useSend sending, and keep SPF, DKIM, and DMARC status visible in Mailbase. - https://mailbase.studio/docs/mcp-oauth: Connect Claude, Cursor, Codex, or another MCP client to Mailbase with OAuth-scoped workspace access. - https://mailbase.studio/docs/no-code-integrations: Connect Mailbase to Zapier, Make, or n8n with REST Hooks: subscribe a callback URL to an event, sample real payloads while you build, and unsubscribe when the automation is turned off. ## Important Blog Guides - https://mailbase.studio/blog/what-is-usesend: A practical explanation of useSend, the self-hosted email problem it solves, and how builder-led teams should evaluate it. - https://mailbase.studio/integrations/usesend: The main integration page for hosted Mailbase sending and BYO useSend workflows. - https://mailbase.studio/blog/coolify-email-marketing-stack: How to run an email marketing stack on Coolify: the one-click services that fit, how they connect to SES, the deliverability work Coolify doesn't do, and where a workflow layer fits. - https://mailbase.studio/blog/railway-usesend-email-stack: How to run useSend on Railway for a fast email stack: the deploy path, managed Postgres/Redis, connecting Amazon SES, costs, and where a Mailbase workflow layer fits. - https://mailbase.studio/blog/cheap-email-marketing-tools-for-developers: The genuinely cheap email marketing options for developers — Amazon SES, self-hosted useSend, free tiers, and where the real costs hide — plus how to keep costs low as you scale. - https://mailbase.studio/blog/reply-inbox-email-workflow: A product guide to the Mailbase reply inbox for teams that want campaign replies, support context, and follow-up work in one place. - https://mailbase.studio/blog/scheduled-email-campaigns: A product guide to scheduled campaigns now that Mailbase can schedule, reschedule, cancel, and execute sends through durable jobs. - https://mailbase.studio/blog/durable-email-send-jobs: A product guide to Mailbase's durable send-job pipeline for reliable campaign launches and scheduled sends. - https://mailbase.studio/blog/ai-mcp-email-workflow: A product guide to Mailbase's REST API, scoped tokens, signed webhooks, and the optional MCP server. - https://mailbase.studio/blog/ai-email-task-workflow: A product guide to in-context AI drafting, the assistant's task queue, and proposal-first inbox triage. - https://mailbase.studio/blog/transactional-email-api-mailbase: A product guide to Mailbase's `/api/v1/send` endpoint and developer platform controls for transactional email. - https://mailbase.studio/blog/mailbase-deliverability-controls: A product guide to the deliverability controls Mailbase exposes across sending, analytics, compliance, and Settings. - https://mailbase.studio/blog/usesend-self-hosted-email-stack: A stack guide for builders running useSend on their own infrastructure. - https://mailbase.studio/blog/self-hosted-email-marketing: The honest guide to self-hosted email marketing software and platforms — the three layers you run yourself, the open-source applications for each, the deliverability work you can't outsource, and when it's worth it versus a SaaS. - https://mailbase.studio/blog/transactional-email-for-saas: A practical guide to transactional email for SaaS: what counts as transactional, choosing an API or SMTP provider, templates, deliverability, idempotency, and the operations that keep critical mail flowing. - https://mailbase.studio/blog/spf-dkim-dmarc-explained: SPF, DKIM, and DMARC explained in plain English: what each record does, how they work together to authenticate your email, how to set them up, and the common mistakes that break them. - https://mailbase.studio/blog/email-api-vs-smtp: Email API vs SMTP compared for SaaS: how each works, reliability, speed, debugging, features, and portability — plus why many teams use both. ## Comparison Pages - https://mailbase.studio/comparisons/mailbase-vs-mailchimp: A fair comparison for teams choosing between Mailchimp and a focused Mailbase email workflow. - https://mailbase.studio/comparisons/mailbase-vs-brevo: A fair comparison for teams choosing between Brevo's broader platform and Mailbase's focused email workflow. - https://mailbase.studio/comparisons/mailbase-vs-customer-io: A fair comparison for teams choosing between Customer.io's lifecycle journey tooling and Mailbase's focused email workflow. - https://mailbase.studio/comparisons/mailbase-vs-resend: A fair comparison for teams choosing between Resend and Mailbase's workflow-first positioning. - https://mailbase.studio/comparisons/mailbase-vs-loops: A fair comparison for SaaS teams choosing between Loops and Mailbase. - https://mailbase.studio/comparisons/mailbase-vs-buttondown: A fair comparison for builders choosing between Buttondown's newsletter focus and Mailbase's broader email workflow. ## Alternative Pages - https://mailbase.studio/alternatives/mailchimp-alternative-for-developers: A fair Mailchimp alternative page for developers who want more control, self-hosted-friendly workflows, and simple pricing. - https://mailbase.studio/alternatives/brevo-alternative-for-developers: Compare Brevo with a builder-friendly Mailbase workflow for teams that already manage email infrastructure. - https://mailbase.studio/alternatives/sendgrid-alternative: A transparent SendGrid alternative page for small SaaS teams comparing managed delivery with Mailbase's self-hosted-friendly angle. - https://mailbase.studio/alternatives/mailgun-alternative: A Mailgun alternative page for builder-led SaaS teams comparing managed APIs with Mailbase's workflow layer and simple pricing. - https://mailbase.studio/alternatives/listmonk-alternative: Compare Listmonk and Mailbase for SaaS teams deciding between newsletter management and connected email workflows. - https://mailbase.studio/alternatives/mautic-alternative: A fair Mautic alternative page for teams that want lighter email workflows and less marketing automation complexity. - https://mailbase.studio/alternatives/sender-alternative: A broader email sender alternative guide for self-hosted builders comparing hosted tools, open-source tools, and Mailbase. - https://mailbase.studio/alternatives/lemlist-alternative: A fair lemlist alternative page for teams that want a focused email workflow — reply inbox, campaigns, AI drafts — instead of a full cold-outreach suite.