About
About Mailtruss.
A transactional email API that shows what happened to every message, built and run by one person in India.
01Why it exists
Why Mailtruss exists
A 200 OK from an email API only tells you the request was accepted.
I built Mailtruss to show what happens next: a recorded trace for every message, and plain-language reasons when something fails, including whether a retry is safe.
I work in DevOps and site reliability, where the first question after an incident is always “what exactly happened, and in what order?” Email deserves the same evidence. It is still the part of a product that people trust least, because so little of it is visible.
Mailtruss is small on purpose. It does fewer things than the large providers and tries to explain each one clearly. If something is missing that you need, tell me.
02How it is run
What you can hold me to.
- One person, answerable
- Email to hello@mailtruss.com reaches me. There is no sales team or support queue between you and the person who builds the product.
- Claims you can check
- Plans and limits come from the product and the pricing page. Where Mailtruss is compared with another service, that service's own published prices are used, with a link and the date they were read. No invented numbers, logos or testimonials.
- Open client libraries
- The libraries for Node.js, Python, Go, PHP, Ruby, Java and .NET, and the MCP server, are MIT licensed. Read them, fork them, take them with you.
- Limits stated plainly
- What Mailtruss can't tell you is written down next to what it can: see security and the delivery errors guides.
At a glance
- Launched
- November 2026
- Based in
- India
- Contact
- hello@mailtruss.com
- Security reports
- security@mailtruss.com
- What changed lately
- The changelog
- Is it up?
- The status page
Try it, then tell me what is missing.
The free plan has 3,000 emails a month. Send a test in test mode first, and read what the trace says.