/01
A short path from setup to send
One clean API, sensible defaults, and documentation designed to get builders to a first send quickly.
Private beta waitlist
Transactional email,
minus the guesswork.
One API, searchable delivery logs, and 4,500 emails free each month. Pay only for what you send after that.
Built forPassword resetsReceiptsOnboardingNotifications
send-welcome.ts
import { Mailer } from "@mailerapi/node";
const mailer = new Mailer(process.env.MAILERAPI_KEY);
await mailer.send({
from: "hello@yourapp.com",
to: "dev@example.com",
subject: "Welcome aboard!",
html: "<h1>You're in.</h1>",
});
✓202 Acceptedmessage queued
1 callto queue a message
$0monthly minimum
Day 1logs and webhooks
Why mailerapi
The email layer we wanted to use ourselves.
Reliable delivery without enterprise complexity. mailerapi gives small teams the essentials — and gets out of the way.
/02
Pay for emails, not a plan
No monthly minimums or confusing tiers. Start free, then pay only for the messages you actually send.
/03
Built to debug, not guess
Useful errors, searchable logs, and webhook events that make delivery problems easy to understand.
A tiny API
One request. That's the whole point.
Send with our SDKs or plain HTTP. The response is predictable, the docs are concise, and every message is traceable.
- ✓Node.js, Python, Go, and REST at launch
- ✓Idempotency and retry handling included
- ✓Local test mode that never sends
POST /v1/email
import { Mailer } from "@mailerapi/node";
const mailer = new Mailer(process.env.MAILERAPI_KEY);
const result = await mailer.send({
from: "hello@yourapp.com",
to: "ada@lovelace.dev",
subject: "Your receipt",
html: "<p>Thanks, Ada.</p>",
});
// { id: "msg_9Kx2...", status: "queued" }
The difference
Clear tradeoffs instead of another feature wall.
mailerapi is being designed for teams that want a small surface area, transparent usage, and enough delivery context to solve problems without a support ticket.
Decisionmailerapi approachWhy it matters
SetupOne send API + focused SDKsLess surface area before the first message.
Pricing4,500 free, then usage-basedNo monthly minimum or capacity tier.
DebuggingSearchable logs + webhook historyTrace what happened without guessing.
TestingLocal mode that does not sendExercise email flows without reaching inboxes.
Beta readiness
Deliverability basics are launch gates, not add-ons.
We publish the recipient-protection rules we follow and require. Read our email practices and acceptable-use policy.
- SPF and DKIM domain authentication
- Hard-bounce and complaint suppression
- Permission-based sending only
- No bought, rented, or scraped lists
- Clear unsubscribe in non-transactional mail
- Abuse review, throttling, and suspension
Pricing preview
Free to validate. Usage-based when you grow.
No contracts, no credit card to start, and no paid sending until the final per-email rate is published.
Pricing commitment
Get pricing updates Monthly allowance
4,500emails free
After the free allowance, pay only for messages sent. The exact rate will be published before paid access begins.
/00
Free to start
4,500 emails included every month. No credit card required.
/01
Volume that scales
Automatic discounts as your monthly sending grows.
/02
Every feature included
Logs, webhooks, templates, and team access from day one.
/03
No capacity plan
No monthly minimum or commitment. Usage starts only after the free allowance.
The free allowance is the current launch plan; the paid per-email rate is still being finalized.
FAQ
What we know now — and what is still being decided.
What will mailerapi cost after the free allowance?
The first 4,500 emails each month are planned to be free. The exact pay-as-you-go rate is not final yet; we will publish it before asking anyone to enable paid sending.
Is a credit card required to join or start?
No. Joining the waitlist and the planned free allowance do not require a credit card.
How will deliverability be handled?
Production sending is gated on authenticated domains, SES bounce and complaint events, automatic suppression, searchable message logs, and delivery webhooks. These controls must be verified before public sending is enabled.
Which SDKs are planned?
Node.js, Python, Go, and a plain REST API are planned for launch. The examples on this page are a preview and may change before the public API is finalized.
Can I migrate from another email provider?
That is a core use case. We plan to provide focused migration examples once the API is stable enough for beta use.
Where will data be processed?
Regional hosting and subprocessors are not final. We will publish those details before beta customers process production email data; the current waitlist practices are covered by the Privacy Policy.
Get in early
Help shape the email API you'll actually enjoy using.
Join the private beta list. We'll invite groups based on use case and sending needs, then use their feedback to decide what ships next.
Reserve your spot
Email is the only required field.