The backend you don't deploy
Your host keeps serving flat files. The POST goes to mailcontact's servers, which validate, store, and notify: the one dynamic piece a static site is missing.
integrations · approach
You can add a working contact form to a static site without writing or hosting any backend. Point a plain HTML form's action at a form endpoint (a URL that accepts the POST for you) and every submission lands in your project's inbox with a notification on Discord, Slack, email, or a webhook. Your site stays a folder of static files.
The usual shortcut, a mailto: link, fails in two ways. It prints your email address into the page's HTML, where spam harvesters scrape it within days. And it only works if the visitor has a desktop mail client configured: on most machines the click opens nothing, or opens an app they've never signed into, and the message is silently lost.
A form endpoint fixes both. Your address never appears in the markup, and submitting is a normal HTTP POST that works in every browser. mailcontact validates the fields, stores the message, and pings the channel you chose, the same flow whether your site is hand-written HTML, a generator's output, or an old page you inherited.
the snippet
Point the form at your project's mailcontact endpoint. Submissions land in your project inbox. No server, no API route, no email service to wire up.
<form action="https://mailcontact.app/api/forms/your-form-id" method="POST">
<label for="name">Name</label>
<input id="name" type="text" name="name" />
<label for="email">Email</label>
<input id="email" type="email" name="email" required />
<label for="message">Message</label>
<textarea id="message" name="message" rows="5" required></textarea>
<button type="submit">Send</button>
</form>how it works
One inbox per project. Name it after your site and you immediately get a form endpoint URL and a project email address. No DNS, no mail server.
Copy the snippet above into any HTML page and replace your-form-id with your endpoint. The field names (name, email, message) are all the endpoint needs.
Add a Discord, Slack, email, or webhook channel. New messages appear in the inbox and ping you the moment they arrive.
why mailcontact
Your host keeps serving flat files. The POST goes to mailcontact's servers, which validate, store, and notify: the one dynamic piece a static site is missing.
No mailto: link, no obfuscated spans, nothing for scrapers to harvest. Visitors see a form; your inbox address stays private.
The snippet is plain HTML. It works in hand-written pages and in any generator's output. No bundler, no framework, no script tag required.
faq
Completely. It's your HTML and CSS. The endpoint only cares about the field names: email and message are required, name and subject are optional. Everything else about the markup is up to you.
A native form post currently shows the endpoint's JSON reply, so the best UX today is a few lines of fetch: POST the same fields from a submit handler and swap in an inline success message. A configurable redirect for native posts is coming with the launch.
Any of them: GitHub Pages, Netlify, Vercel, Cloudflare Pages, an S3 bucket, or nginx serving a folder. The form posts to mailcontact's servers and requests are accepted from any origin, so there's nothing to configure on the host.
The free plan includes one form and one project email address per unified inbox, up to 2 projects, with Discord and email notifications. Submissions are rate-limited to 20 requests per minute per IP (far more than a contact form sees), and higher volume comes with the Pro plan at launch.
related
Forms and a real email address, together, with notifications where you live. Launching soon. Be the first to know.