Frequently asked questions

A shared inbox for the email your app sends in development, staging and CI. Point your app's SMTP settings at Mailclutch and every message is captured instead of delivered, so your team can read it, check how it renders, test its deliverability and share it with a client for sign-off.

Yes. Every visitor gets a working SMTP host, port, username and password on the homepage, without an account. Send to it from your app and the message shows up in your browser. That sandbox keeps mail for 24 hours, and you can keep it by signing up within 7 days. Get your credentials.

Each project has its own SMTP credentials. Replace your mail server settings in your app's environment with them — host, port, username, password — and every email your app sends lands in the project instead of reaching a real inbox. Nothing else in your code changes. Quickstart · Framework guides

Anything that can send email over SMTP: Laravel, Symfony, Rails, Django, Node.js, Spring, .NET, WordPress and the rest. There is no SDK to install. Mailclutch listens on the usual ports with and without TLS, and the documentation has a setup guide per framework.

Yes. The REST API can create an inbox per run, wait until a message arrives and return a pass/fail verdict on it — links, codes, unrendered variables, deliverability — in one call, so a test suite can assert on the email it triggered. CI recipes.

No, and that is the point: Mailclutch never delivers to the real recipient. It is a sandbox for development, staging and CI. Keep your transactional provider (SES, Postmark, Resend) for production.

Yes, from the Indie plan: every captured email gets a SpamAssassin score and an SPF, DKIM, DMARC and BIMI check, with what to fix when something fails.

Yes: in the browser, through HTTP webhooks, or in a Slack channel. The inbox itself updates in real time for everyone looking at it.

Yes, up to 25 MB per email. They are listed with the message and can be downloaded from it.

2 on Free, as many as you like on every paid plan. Each project has its own credentials and its own inbox, typically one per application or per client.

Any message that reaches your project, through its SMTP credentials or its forwarding address. Every plan, Free included, captures an unlimited number of them. You are charged for seats, never for volume.

Retention is 7 days on Free, then emails are removed. Indie, Pro, Team and Enterprise keep captured email until you delete it. A throwaway inbox created from the homepage lives 24 hours.

No. Sharing produces a link, for a single email or for a whole project, optionally password-protected. Whoever opens it needs no account and takes no seat. Seats are only for the people working inside your organization.

A seat is a place in your organization, taken by a member or a pending invitation. Pro includes 5 and each extra seat costs €6/month; Team includes 20 and each extra seat costs €5/month. Extra seats are ordered from the billing page and charged pro rata straight away; seats nobody uses can be released, and the next renewal is smaller.A seat is a place in your organization, taken by a member or a pending invitation. Pro includes 5 and each extra seat costs $7/month; Team includes 20 and each extra seat costs $6/month. Extra seats are ordered from the billing page and charged pro rata straight away; seats nobody uses can be released, and the next renewal is smaller.A seat is a place in your organization, taken by a member or a pending invitation. Pro includes 5 and each extra seat costs £5/month; Team includes 20 and each extra seat costs £4/month. Extra seats are ordered from the billing page and charged pro rata straight away; seats nobody uses can be released, and the next renewal is smaller.A seat is a place in your organization, taken by a member or a pending invitation. Pro includes 5 and each extra seat costs CA$10/month; Team includes 20 and each extra seat costs CA$8/month. Extra seats are ordered from the billing page and charged pro rata straight away; seats nobody uses can be released, and the next renewal is smaller.A seat is a place in your organization, taken by a member or a pending invitation. Pro includes 5 and each extra seat costs CHF 6/month; Team includes 20 and each extra seat costs CHF 5/month. Extra seats are ordered from the billing page and charged pro rata straight away; seats nobody uses can be released, and the next renewal is smaller.A seat is a place in your organization, taken by a member or a pending invitation. Pro includes 5 and each extra seat costs A$10/month; Team includes 20 and each extra seat costs A$8/month. Extra seats are ordered from the billing page and charged pro rata straight away; seats nobody uses can be released, and the next renewal is smaller.

Yes, from the Team plan. Share links lose every mention of Mailclutch — the page, the browser tab and the email announcing the share carry your name and logo — and are served from a subdomain of yours, such as sandbox.acme.com, with the HTTPS certificate handled for you. One DNS record to create. How white label works.

Yes: a year costs ten months, so you get 2 months free — about 17% off twelve monthly payments. The Free plan stays free, with no time limit.

No: every price we show excludes tax. Tax is calculated at checkout from your billing address and shown before you pay. A business in the EU outside France with a valid VAT number is invoiced without VAT (reverse charge); a customer outside the EU pays no French VAT. Every payment comes with an invoice showing the tax breakdown, downloadable from your billing settings.

By card, through Stripe; we never see or store your card number. Monthly and yearly plans renew automatically and can be cancelled at any time from the billing settings, in a few clicks: the plan runs to the end of the period already paid, then your organization returns to the Free plan. Seats added during a period are charged pro rata.

Every plan gets an answer from the people who build Mailclutch. Response targets grow with the plan: 2 business days on Indie, 1 business day on Pro, 4 business hours on Team, business hours (Monday to Friday, Paris time). A monthly uptime SLA backed by service credits comes with Pro 99.5%, Team 99.9%, Enterprise 99.95%. Enterprise can negotiate its own terms.

Yes. Open-source projects and non-profit organizations can use a paid plan for free. Write to support@mailclutch.com or through the contact form with a link to the project or proof of non-profit status.

The organization-wide audit log, custom roles and SAML SSO. They are designed and priced but not shipped, and they are listed so you can plan around them. They are not part of what you get today. If one of them gates your decision, write to us and we will give you a date.

In the European Union. The application, database and object storage all run in the Paris region (eu-west-3), and captured email is never transferred outside it. A signed DPA is available.

It is encrypted in transit (TLS for SMTP, the API and the app) and at rest. Each organization only ever sees its own projects, and a share link can be protected by a password and revoked at any time.

Yes. Mailclutch is made and operated in France, staging inboxes often hold real personal data, and the service is built for it: EU hosting, retention you control, and a data processing agreement. Read the DPA · Security

Yes, at any time: a single email, a whole project, your organization or your account. Deleted emails go to the trash first, then are purged for good.