We built it for ourselves first.
Martin Business Consultants needed email infrastructure it could actually audit — for medical communications, for nonprofit programmes, for logistics notifications where a silent failure moves physical goods to the wrong place. Nothing on the market let us answer “what happened to this message?” without taking someone's word for it.
Dogfood before doctrine.
OutSend started as internal infrastructure, not a product idea. We were operating email for clients whose mail genuinely matters — appointment reminders, programme notifications, shipment updates — and the tooling available gave us aggregate dashboards when what we needed was the provider's actual response to a specific message.
So we built the thing that kept the evidence. It now runs millions of emails a day across medical, nonprofit, logistics, and storage workloads. We productised it because the gap we hit is not a niche one, and because we would rather other people be able to audit our infrastructure than trust our description of it.
We name the companies who are happy to be named, and we say nothing at all about the regulated workloads. Trust-sensitive mail does not become case-study material here.
Never venture-backed.
OutSend is owned and operated by Martin Business Consultants and funded entirely by customers paying for cloud hosting and support. There are no investors, no board seats to satisfy, and no acquisition clock running in the background.
This is not a criticism of venture capital, which is a reasonable instrument for companies that need to buy a market quickly. It is a statement about what our incentives reward: we make money when you keep sending successfully, which means reliability is the business rather than a cost centre inside it.
The practical consequence is that the open core will still be there in five years. Our revenue does not depend on closing it, so there is no future quarter in which closing it becomes attractive.
Sending in production for
and more
Four rules we actually apply.
If it cannot be inspected, it does not ship
Every claim on this site should map to something a stranger can go and check — a stored event, a DNS record, a line of code, a published method.
Correct beats clever
We would rather publish a boring accurate number with its limits attached than a sharp one that needs a footnote we did not write.
Isolation over efficiency
Pooled sending is cheaper to run. We do not do it, because the saving comes out of your reputation rather than our margin.
The exit stays open
Open core, exportable data, documented self-hosting. A vendor relationship you can leave is a different relationship from one you cannot.
Judge us on the evidence.
Read the code, run a trace, or ask us something awkward. All three are faster than reading more of this page.
Open core · never venture-backed · operated by Martin Business Consultants