Skip to content
NewA free test that shows whether your emails will reach the inbox.

Inboxes, sending and MCP in one account.

Email API for apps and AI agents.

Send sign-up codes and receipts, receive replies, and give each AI agent its own inbox. One account, your own domain, free to start.

Free plan: 3 inboxes and 3,000 emails a month, custom domains included, no card.

terminal
$ mailbay inbox create support

✓ support@k7m3qz.mailbay.email
ready, receiving mail now

Works with the tools you already use

  • Next.js
  • Supabase Auth
  • Clerk
  • Claude Code
  • Cursor MCP
  • Codex
  • v0
  • Replit
  • n8n
  • Zapier
  • Make
  • Laravel
  • Rails
  • Django
  • FastAPI
  • Resend SDK
  • LangChain
  • Vercel AI SDK

What are you building?

One account sends and receives for your app, on as many addresses as you need. Left: the code you write. Right: what Runearc does.

app/actions/welcome.ts
// .env  RESEND_BASE_URL=https://api.mailbay.dev/v1
//       RESEND_API_KEY=mb_live_...  (a Runearc sending key)
import { Resend } from "resend";

const mailbay = new Resend(process.env.RESEND_API_KEY);

export async function sendWelcome(email: string) {
  const { data, error } = await mailbay.emails.send({
    from: "Acme <hello@acme.com>",
    to: email,
    subject: "Welcome to Acme",
    html: "<p>Thanks for signing up. Your workspace is ready.</p>",
  });
  if (error) throw new Error(error.message);
  return data.id; // "eml_01jc4r..."
}

The code is real and runs against the Runearc API. The right side replays what it returns.

What do you want to do?

Pick the one closest to you. You can do the others later, with the same account.

  • Add email to your app

    Send and receive mail from your code with one API key, on as many addresses as you need. Keep each product or client separate.

    Best for: Developers and SaaS teams

  • Send from your own domain

    Send as you@yourcompany.com. We show you the DNS records to add, and Runearc checks DNS and Amazon SES readiness for you.

    Best for: Real emails to your customers

  • Let an AI agent use email

    Give your agent its own inbox. It can receive verification codes, read mail and reply.

    Best for: AI agents and automations

  • Get an email address to try

    Create an inbox and send yourself a test message. No domain or setup needed.

    Best for: Trying Runearc for the first time

What Runearc does

Everything your product does with email, in one place.

Send
Welcome emails, receipts and password resets, from your own domain.
Receive
Read replies in the dashboard, through the API, or let an AI agent read them.
Agents
Give each AI agent its own inbox. It can sign up, read the code and reply.

One account instead of four tools.

Most products need one tool to send, one to receive, a help desk and a test inbox service. Here is what changes.

All comparisons
The usual stack

Four tools, four bills

  • One tool to send, another to receive
  • A help desk for support@
  • A test inbox service for your automated tests
  • Domains and keys set up again for each one
Runearc

One account, one bill

  • Sending, receiving, a shared support inbox, inboxes for AI agents and test inboxes
  • One set of domains and API keys
  • Free plan: 3 inboxes, 3,000 emails a month, 3 custom domains
  • Received mail never counts toward your sending allowance

Using another tool today? Here is what changes, and where the other one is still better.

  • From Resend

    Keep the Resend SDK and change one base URL. Receiving, a support inbox and agent inboxes come with the same key.

    Where Resend is better: Stored templates, React Email, open and click tracking, broadcasts, official SDKs in many languages, dedicated IPs and more than one sending region.

  • From AgentMail

    Custom domains on the free plan, and sending for your app from the same account as your agents.

    Where AgentMail is better: A larger MCP server with OAuth sign in, Python and Node SDKs, and paid plans you can buy today.

  • From Mailosaur

    A catch-all where every test makes up its own address, and one API call that waits for its email.

    Where Mailosaur is better: SMS testing, email previews, and plugins for many test frameworks.

How do you want to start?

Set it up yourself for free, or email us if you would like help.

On your own

Set it up yourself

Create a free account and get an inbox in a few minutes. The free plan has 3 inboxes, 3,000 emails a month and 3 of your own domains. No card needed.

With help

Talk to a person

Moving from Resend, AgentMail or Mailosaur, or setting up many projects at once? Email us and we will help you plan it.

One place for all your email.

Most products need four email tools: one to send, one to receive, a help desk and a test inbox service. Runearc is all four, in one account.

  • Send

    Sign up emails, magic links and receipts from your own domain. A Resend compatible API, SMTP, batches of up to 100 and scheduled sends, with delivered, bounced and complained events.

  • Receive

    Mail to your addresses is stored, threaded and checked for SPF, DKIM and DMARC. Read it with the API or get a webhook.

  • Support inbox

    support@ on your domain as a shared inbox: assign, snooze and close conversations, and reply in the customer's thread.

  • Agent inboxes

    Give each agent its own address over MCP. wait_for_email blocks until the message arrives and returns its codes and links.

  • Test inboxes

    Any address under your private mailbay.email domain lands in one catch-all, so every test can make up its own address.

  • Guided domain setup

    Add a domain and on Vercel or Cloudflare we write the inbound MX, DKIM, DMARC and Amazon SES return-path records for you. Anywhere else, copy the records and the dashboard checks each one live. Existing MX records are never deleted.

Works with your stack.

Pick the tool you use and copy the setup for it. It works through SMTP settings, the Resend SDK, our API or one command for AI agents.

All integrations

Resend SDK, new base URL. Our /v1/emails endpoint takes the same request, so emails.send works unchanged.

app/api/invite/route.ts
// The Resend SDK, pointed at Runearc. In .env:
//   RESEND_BASE_URL=https://api.mailbay.dev/v1
//   RESEND_API_KEY=mb_live_...
import { Resend } from "resend";

const mailbay = new Resend(process.env.RESEND_API_KEY);

export async function POST(req: Request) {
  const { email } = await req.json();
  const { data, error } = await mailbay.emails.send({
    from: "Acme <team@acme.com>",
    to: email,
    subject: "You're invited to Acme",
    html: "<p>Join your team on Acme.</p>",
  });
  return Response.json(error ?? data, { status: error ? 400 : 200 });
}
Sending with the Resend SDK

Names and logos belong to their owners. They are shown because Runearc works with these tools, not because of a partnership.

Built for people with many projects.

One workspace, with a separate project for each product. Each project has its own domains, inboxes and API keys, so one product never sees another's mail.

  • Your plan's inboxes and emails are pooled across every project
  • Invite teammates and choose who sees which inbox
  • A Playground project with a catch-all for your tests

Example workspace. Paid plans will be one bill for the whole workspace.

See what happened to every email.

For every email you send, Runearc shows whether it was delivered, delayed, bounced or reported as spam. Incoming mail is checked and saved before your app or agent reads it.

Know what happened to every email
Each email you send shows as delivered, delayed, bounced or reported as spam, so you can tell why a password reset never arrived.
Mail we accept is never lost
We only confirm that we received a message after it is safely saved. Mail to an address that does not exist is refused straight away.
One bad address cannot hurt you
If an address bounces or someone reports your email as spam, we stop sending to it for that project.

Deliverability is a shared job. Runearc authenticates your domain, handles bounces and complaints, and pauses harmful traffic. Inbox placement still depends on wanted content, list quality, domain reputation and each mailbox provider's filters.

Start free.

Every workspace gets the whole product: API, SMTP, MCP, the CLI and the dashboard. Nothing is charged before billing launches, and no card is needed.

  • 3 inboxes
  • 3,000 emails a month
  • 3 custom domains

pro

Planned

$9a month

25 inboxes, 50,000 emails a month, 10 domains

scale

Planned

$99a month

250 inboxes, 250,000 emails a month, unlimited domains

Global prices shown in USD. See the full pricing page.

Questions before you switch.

For indie hackers, SaaS teams, people building with AI and anyone testing email.

What is Runearc?
Email for the products you build: send sign up emails and receipts, receive mail at your own domain, answer support@ as a team, give AI agents their own inboxes and test email flows. One API, SMTP, a CLI and an MCP server cover the whole workflow.
How much does it cost?
The free plan includes 3 inboxes, 3,000 emails a month and 3 custom domains, with no card. Paid plans are planned from $9 a month and start when billing launches.
I have several side projects. Do I pay for each one?
No. One workspace holds a project per product, each with its own domains, inboxes and keys. Your plan's limits are pooled across all of them.
Can I use Runearc for Supabase Auth or Clerk emails?
Yes. In Supabase, turn on custom SMTP with host smtp.mailbay.dev, port 465, username mailbay and a Runearc API key as the password. With Clerk, turn off Delivered by Clerk and send each email from its email.created webhook through our API.
I use Resend today. How hard is it to switch?
Set RESEND_BASE_URL to https://api.mailbay.dev/v1 and use a Runearc key. We tested emails.send and emails.get with the Resend Node SDK. Stored templates and React Email rendering are not supported: send HTML you render yourself. Runearc has no open or click tracking and no broadcasts.
My app was built with Lovable, Bolt or v0. Can it send email?
Yes. Paste our prompt into your AI builder. It stores your API key as a server secret and sends with one POST to our emails endpoint from server code, such as an edge function. The key must never reach the browser.
How do AI agents use Runearc?
Through our MCP server at mcp.mailbay.dev/mcp with your API key as a bearer token, one command in Claude Code or one file in Cursor. Agents can create inboxes, send, reply, read threads and call wait_for_email, which returns codes and links.
How do I test sign up and password reset emails?
Every workspace has a catch-all on its private mailbay.email domain. Each test makes up an address, triggers the email and waits for mail to exactly that address with one API call, which returns the message with its codes and links.
Can my team answer support@ together?
Yes. Point support@ on your domain at Runearc and work it as a shared inbox: assign conversations, snooze and close them, and reply in the customer's thread. Replies keep the thread intact in Gmail and Outlook.
Will my emails land in the inbox?
We set up aligned DKIM, SPF and DMARC, handle bounces and complaints, and use Amazon SES for the final outbound hop. That improves the starting point but cannot guarantee Inbox placement: content, list quality, domain reputation and mailbox-provider filters still decide it.
My domain already receives email. Will you break it?
No. We never delete existing MX records. If your domain already receives mail elsewhere, we suggest a subdomain such as mail.acme.com for Runearc instead.
Do you read or track my email?
The public website uses Vercel Web Analytics when hosted on Vercel and self-hosted Umami when configured. The dashboard and API have no visitor analytics. Runearc stores messages so your authorized workspace members, keys and agents can use them; authorized Runearc operators may access them when required for support, security or abuse handling. Outbound messages are processed by Amazon SES for delivery.

Who Runearc is for, and who it is not.

Better to know before you sign up.

A good fit if

  • You send your app's own email: sign-up codes, receipts, resets
  • You want agents or tests to have inboxes they can read
  • You want one account for sending, receiving and a shared inbox

Not the right tool if

  • You send marketing newsletters to large lists. Use a tool built for campaigns.
  • You need a full office suite with docs, drive and meetings. Runearc is email only.
  • You need SMTP-only sending at very high volume with a dedicated IP team. Ask us first.

Ready to send your first email?

Create a free account and you will have an inbox in a few minutes. No card needed.

Prefer the terminal? Copy this command.

$ mailbay inbox create support

Still deciding? Ask your AI.

These open your assistant with a question about Runearc already typed in. Check what it says against our docs.