Send Email Directly From Your Code.
No server code needed, a single REST API call is enough.
Free · 500 emails a day per app · no card, no plan to cancel
Who it’s for
Static sites
Nothing to host, no database, no form service to log into — the submission arrives as an email.
Small business contact forms
An enquiry form whose submissions need to reach a real person, on whatever inbox that person already reads all day.
Side projects and prototypes
A waitlist, a feedback box, a bug report form. Wire it up in an afternoon and delete it just as easily — no plan to cancel.
Features
What you get
- Any inbox, any provider — Gmail, Zoho, Outlook or your own domain. Mail is sent from our account and replies go to the person who filled the form.
- Fields you define — Declare exactly which fields an app accepts — the default is name, email, phone, message. Anything undeclared is rejected, so a leaked key can't be used to mail arbitrary content.
- 5 mail designs — Pick how submissions look in the inbox and switch any time. Every design is table-based inline HTML with a plain-text alternative, so it survives every mail client.
- No SDK, no lock-in — A single HTTP endpoint that takes JSON or a form post. Works from a static site, a serverless function, a shell script or curl.
- Confirmed destinations only — An address has to confirm by code before anything is delivered to it, so the service can never be pointed at an inbox that never asked for the mail.
- Sensible limits, published — Each app may send 500 emails a day — far more than a contact form needs, and stated up front rather than discovered. Identical submissions within a minute are collapsed, so a double-clicked submit button never doubles an email.
- Every attempt logged — Successes and failures are recorded with the mail server's own response, so a missing email is something you can actually diagnose.
- Nothing delivered is stored — The submission is rendered, emailed and dropped. The log keeps the status, the time and the mail server's reply — never the fields you received. Only a blocked submission records what triggered the block.
Who it’s not for
- Companies sending newsletters, ad campaigns or marketing blasts. Every send goes to the one confirmed destination for that app, never to a list of recipients.
- Anyone who needs a large volume of mail in a day. Each app is capped at 500 emails a day — we will raise it for a form that genuinely needs more, but not to the point of a bulk sender.
- Products sending transactional email to their own users — receipts, password resets, alerts. The sender is always our address, not your domain.
- Cold outreach. A submission has to come from a form somebody actually filled in on your site.
Clients
VM Computers and NetworkingEnquiry form submissions delivered to the owner's inbox.
Sending through Mailer by satz and happy to be listed? Tell usand we’ll add your site.
Ready to wire up your form?
Register an app, copy its key, and post your first submission in a couple of minutes. The API docs carry the full reference, and contact has the answers to the questions people ask first.