mailcontact is now available. We are building a contact inbox for every project: a place to receive website form submissions, collect incoming email on Pro, and get notified in the tools you already check. If you are launching a portfolio, a small SaaS or a side project, the goal is simple: make it easy for people to reach you without building and maintaining a contact backend yourself.
Public signup is open. Create a free account, verify your email and connect your first project. Here is what mailcontact offers and how the plans differ.
A contact form backend for the website you already have
Each project gets a form endpoint: a URL that receives your contact form's submissions and stores them in an inbox. Keep your own HTML, labels and styling. Your form sends the visitor's email address and message to mailcontact; you do not need to set up an email-sending service or host a server just to collect enquiries.
The endpoint accepts ordinary form data and JSON, so the same setup works with a static website or a JavaScript frontend. There are guides for Astro, Next.js, GitHub Pages and other stacks. Moving your website to another host does not require changing where your messages go.
The current endpoint returns JSON. For an inline confirmation on your own page, submit with fetch and check the response before telling the visitor their message was received. Our complete contact form example includes success and error states, and the endpoint reference lists supported fields.
A project email address alongside the form on Pro
Some visitors prefer a contact form; others want to write from their email app. Pro gives each project a receiving address such as yourproject@mailcontact.cc. Messages sent there arrive in the same project inbox as form submissions, with the source identified.
Choose an available address for your project without configuring your own domain's DNS. This gives a portfolio, product or early beta a public contact address while keeping your personal address off the page. These are receiving addresses on mailcontact.cc; custom receiving domains are not available at this stage. The project email guide explains how they work.
Notifications where you already work
An inbox holds the message; a notification tells you to look at it. mailcontact supports email destinations on every plan, with Discord, Slack and webhooks on Pro and Plus. Email notifications go to your verified account address. Channels are configured per project, so a portfolio enquiry and a product support message can reach different destinations.
You can test a notification destination and see its delivery status. Temporary delivery errors are retried, and a failed notification does not remove the original message from the inbox. Start with the notification setup guide or the walkthrough for Slack contact form alerts.
Free, Pro and Plus: what each plan includes
Free is for a single project that needs a working contact form. Pro includes 10 projects and Plus includes 50, with receiving email addresses, replies and larger message allowances.
| Feature | Free | Pro | Plus |
|---|---|---|---|
| Projects | 1 | 10 | 50 |
| Forms per project | 1 | 1 | 1 |
| Monthly allowance | 50 form submissions | 1,000 messages received and replies combined | 10,000 messages received and replies combined |
| Receiving email address | No | One per project | One per project |
| Discord notifications | Included | Included | Included |
| Email notifications | To your verified account email | To your verified account email | To your verified account email |
| Price | Free | €9/month or €90/year | €29/month or €290/year |
The monthly allowance is shared across the account and renews on your activation date, including with yearly billing. Free uses your account activation date. Once it is used, new messages are refused; existing messages remain available. Deleting a message does not restore the allowance. Plus includes 50 projects and 10,000 shared messages for €29/month; the pricing page is the reference for the current offers and message packs.
Spam controls without adding a puzzle to your form
The endpoint validates incoming fields, limits request sizes and applies rate limits. The hosted script injects the required company_website check; direct integrations must include it themselves. A missing check blocks sending and a filled check is silently discarded. Content checks and campaign detection can trigger automatic verification or hold messages in Spam for review without alerts or quota usage. These controls reduce unwanted traffic, but they are not a guarantee that every spam message will be caught. Our guide to contact form spam protection covers the setup and its limits.
Connect your first project
- Create a free account and verify your email address.
- Choose the first project you want to connect: a portfolio, product website or side project.
- Prepare your form using the contact form generator or a framework guide.
- Pick a notification destination so incoming messages reach the place you check.
Replace the example endpoint with the one from your project, send a test submission, and confirm it appears in both your inbox and your chosen notification channel. That is the contact setup mailcontact is built to simplify.