Mail infrastructure · EU-hosted
We wrote the SMTP engine. We sign your DKIM. We publish your MTA-STS policy. And unlike every other mail service, we will show you all of it — because when you own the whole stack, there is nothing to hide behind.
; zone: yourdomain.com
Generated on domain setup
| Host | Type | Value |
|---|---|---|
| @ | MX | 10 mx.pulsar.email. |
| @ | TXT | v=spf1 include:_spf.pulsar.email -all |
| pulsar._domainkey | TXT | v=DKIM1; k=ed25519; p=… |
| _dmarc | TXT | v=DMARC1; p=quarantine; rua=mailto:dmarc@pulsar.email |
| _mta-sts | TXT | v=STSv1; id=… |
| mta-sts | CNAME | mta-sts.pulsar.email. |
Why Pulsar
They resell an MTA they did not write, on infrastructure they do not run, and the only thing they can tell you when delivery breaks is that they have escalated it. That is why every support thread about a bounced message reads the same way.
Pulsar is the other shape. The SMTP engine, the IMAP and JMAP servers, the queue, the DKIM signer, the TLS policy enforcement — we wrote them, we run them, and we will show you the headers. If you know what a DKIM selector is, or you are the sort of person who is about to go and find out, this is built for you.
What we actually run
RFC 5321
Not Postfix with a control panel bolted on. Inbound, submission, the outbound queue, per-destination pooling and throttling — one codebase we wrote, so when a message stalls we can tell you which hop it stalled on and why.
RFC 6376 · 8463
Ed25519 by default, RSA-2048 for receivers that still need it, dual-signed where it helps. Per-domain selectors you can read in the DNS and in every Authentication-Results header we write.
RFC 8461 · 7672
We publish your policy at mta-sts.pulsar.email and enforce other people's on the way out. Mail to a host with a broken TLS policy is deferred, not silently downgraded to cleartext.
RFC 8620 · 8621
The same protocol the app itself speaks. Third-party clients get the identical surface, including push, so nothing about Pulsar is only reachable through Pulsar.
RFC 5228 · 5804
Filters run on the server, so they apply before your phone lights up. Edit them in the app or with any ManageSieve client — the script is a file you own, not rows in our database.
S3 · mbox
Full mbox export on demand, and an S3-compatible blob backend you can point at Backblaze B2, Cloudflare R2, MinIO or AWS. Storage is a backend, not a hostage.
Honest comparison
What each of us ships, including the rows where we lose. Current as of this release; corrections to and we will change the table.
| Feature | Pulsar | Gmail | Fastmail | Proton |
|---|---|---|---|---|
| JMAPRFC 8620 / 8621 | Yes | No | Yes | No |
| IMAP and SMTP on every plan | Yes | Yes | Yes | Partial |
| ManageSieveRFC 5804, server-side filters | Yes | No | Partial | No |
| Runs its own MTANot a reseller | Yes | Yes | Yes | Yes |
| MTA-STS and DANE outbound | Yes | Partial | Partial | Partial |
| Bring-your-own S3 archive | Yes | No | No | No |
| Full mbox export | Yes | Yes | Yes | Yes |
| Native mobile appsStandards clients only, for now | No | Yes | Yes | Yes |
| Years in operation | 2026 | 2004 | 1999 | 2014 |
Free on a Pulsar subdomain, for as long as you want it. Pro is and adds your own domains, S/MIME and OpenPGP, and the deliverability report. No card to start, and the mbox export works on day one — the way out is the first thing we built.