What people build with Runearc
Six jobs Runearc does well, each with a walkthrough you can copy. The requests and code on these pages were run against a real Runearc stack before we published them.
Updated
Guides
- An email inbox for your AI agentAn agent that signs up for things needs an address that receives mail, and a way to get the code out of it without polling. Here is the whole flow in three steps.3 min read
- support@ on your own domain, without Google WorkspaceMost small SaaS products need two or three shared addresses, not a seat per person. Here is how to run support@ on your domain, keep the mail you already have, and answer from a shared inbox or Apple Mail.4 min read
- Send email from Supabase, Next.js or NodePassword resets, magic links and receipts need a sender that is authenticated for your domain. Here is the same job four ways: Supabase Auth over SMTP, Nodemailer, plain fetch from Next.js, and the Resend SDK.3 min read
- Catch-all inboxes for end to end testsEmail is the step most end to end suites skip, because it is slow and flaky to check. A catch-all domain makes every test its own address, and a blocking wait removes the polling.3 min read
- Email for indie hackers with many projectsTen side projects should not mean ten email accounts, ten DNS setups and ten bills. Runearc groups everything by project so each product keeps its own domain, inboxes and keys.2 min read
- Give an MCP agent its own email addressMCP lets an agent use email the way it uses any other tool. Add one server to your client and the agent can create an inbox, send, reply and wait for a code.2 min read
Read next
Put Runearc to work
Get inboxes, sending, your own domains and MCP in one workspace. The free plan includes 3 inboxes, 3,000 emails a month and 3 custom domains, with no card.