Questions, answered plainly.

No. You never run mail servers or build the pipelines that process bounces and complaints. Outstamp runs them for every project.

In test mode, right after you sign up and copy a key. Real mail from your own domain starts once its DKIM records verify, which depends on your DNS provider.

Not yet. The API is plain REST with an OpenAPI schema, so any HTTP client works: curl, fetch, requests.

No. Outstamp is a server-side API. Keep keys on your server: a key in browser code can be copied by anyone.

Nobody can promise the inbox, and we don't. We set up what depends on us: DKIM, SPF, DMARC and MAIL FROM, checked automatically. And the events tell the truth: delivered means the recipient's server accepted the message.

That the recipient's mail server accepted the message. What happens next, inbox or spam folder, is the receiver's decision, and no sender can see it reliably.

A hard bounce or a complaint adds the address to your project's suppression list automatically, so you stop hurting your reputation. You can remove it, with a confirmation.

Three DKIM CNAME records are required. MAIL FROM records (MX and SPF) and a DMARC record are recommended. The dashboard shows each one and checks them for you.

No. Test keys, the simulator and webhooks are free, and you can send real emails to your own verified address. You add a card when you start sending live.

Each recipient. An email to one person counts as one; the same email to three people counts as three. Test sends never count.

Yes. If Outstamp does not work for you in the first 30 days of a paid plan, we refund it.

Yes. Invoices are issued in Portugal with your VAT number. Prices on the site exclude VAT.

From the European Union.

Bodies for 7 days and recipient addresses for 30 days by default. You can shorten both, down to not storing content at all, at no cost.

No. No model training and no advertising. Support access to content is audited, and you can turn it off.

Create a project, verify a sending subdomain, then point your sending code at POST /v1/emails with an Outstamp key. The request is familiar but not a copy of another provider's API, so read the migration guide.

Yes, with POST /v1/suppressions/batch, so addresses that bounced elsewhere stay blocked here.

Not yet. Outstamp is an HTTP API.

You are not locked in. The API is plain REST with no SDK to adopt, and your DNS stays yours. Moving to another provider means changing one HTTP call.