Invite-only early access — apply below

Email infrastructure your product can rely on

Send and receive transactional email over your own verified domain. A clean HTTP API, live delivery tracking, a real test mode — and deliverability treated as a first-class feature.

Request an invite See pricing

POST /api/v1/emails

curl https://console.mailflo.dev/api/v1/emails \
  -H "Authorization: Bearer mf_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "from": "hello@yourdomain.com",
    "to": "user@example.com",
    "subject": "Welcome aboard",
    "html": "<p>Thanks for signing up!</p>"
  }'

Everything email, one console

MailFlo covers the full lifecycle of product email — from DNS setup to the moment a reply lands back on your webhook.

Send over your own domain

Every project maps to a domain you verify once. MailFlo generates the exact SPF, DKIM and DMARC records to paste into your DNS, then checks them live until everything turns green.

A clean sending API

One authenticated POST with from, to, subject and html — that's it. Sends are rejected unless the from-address matches your verified domain, so nothing can be spoofed from your account.

Test mode built in

Keys come in mf_live_ and mf_test_ flavors. Test sends are recorded and inspectable in the console but never leave the platform — integration-test your email flow without emailing a single human.

Delivery tracking, end to end

Every message carries a status timeline: pending, sent, delivered, bounced or complained — with bounce types and complaint feedback captured automatically. Your dashboard updates in real time.

Inbound email

Point an MX record at MailFlo and receive email on your domain. Messages are parsed, stored, and forwarded to your webhook — replies and support addresses become just another API event.

Teams and roles

Organizations with owner, admin, member and viewer roles. Invite teammates by email, scope everything to your workspace, and manage API keys per project.

Why we're invite-only (for now)

Email is shared infrastructure: one abusive sender can hurt deliverability for every honest one. While we're in early access, we review every application by hand before issuing an invite. It keeps the platform's sender reputation clean — and it means your email lands in inboxes, not spam folders.

This is a temporary limitation. As our abuse-prevention tooling matures, we'll open self-serve signup. Applying today puts you at the front of that line.

Apply for access

Verified senders only

No one sends until their domain is verified, and no key can send as a domain it doesn't own.

Bounces and complaints watched

Delivery, bounce and complaint events are recorded per message and aggregated daily, so problem sending is visible immediately.

Reviewed applications

Every account on the platform was approved by a human. Shared infrastructure stays clean because bad actors never get in.

From zero to sending in minutes

Create a project

One project per sending domain, in the AWS region closest to your users.

Verify your DNS

Copy the generated SPF, DKIM and DMARC records into your DNS. We check them live.

Grab an API key

Start with a test key — sends are recorded but never delivered, so you can build safely.

Go live

Swap in the live key. Watch deliveries, bounces and inbound replies stream in real time.

Ready to take email off your worry list?

Tell us what you're building. If it's a legitimate use case, you'll usually hear back within a few business days.

Request an invite