Posthaste

Contact

Talk to a person who built it.

Sales, support, billing or a security question: it reaches the people who wrote the code. We aim to reply within one working day.

If it is about a specific send, include the message id — it goes straight to the delivery record and usually to the answer.

We use what you send here to reply to you, and nothing else.

About

Why we run our own mail servers.

Every provider shows you a status: sent, delivered, bounced. None of them show you the conversation that produced it, because the conversation happened on infrastructure they rent. You can only hand somebody the receiving server’s own words if you were the one talking to it.

So Posthaste runs its own mail servers on its own IP. We sign your mail with your domain’s key, talk to the recipient’s server ourselves, keep the transcript and hand it to you.

The sending path, bounce handling, signed webhooks, the delivery record and the dashboard are built and in production. The sending IP is still young, so the warmup is deliberately conservative. We would rather say that plainly than imply a maturity we do not have; the security page sets out exactly what is and is not true.

A very small team, building in the open. Md Shaiyad and Hardil Singh, trading as Posthaste; operated from India, hosted in the EU. Ask why something works the way it does, and you will get the actual reason.

What we will not build.

Marketing campaignsA different complaint profile, with shared consequences: one bad list damages placement for every customer on the IP.
Open tracking by defaultA tracking pixel in every message is a decision about your recipients we should not make for you.
Per-seat pricingCharging by how many colleagues can read a log is a tax on doing the job properly.
A cheaper tier that hides the recordsThe delivery record is the product, not an upsell.