Work / AI infrastructure
MessagePipe
One API that reaches a person on email, SMS, push, WhatsApp or chat — through whichever providers are already in place, with automatic failover between them.
State
In public use
Domain
AI infrastructure
Our role
Built & run
Still ours
On call
The problem
Reaching a person means stitching together a dozen channels, each with its own quirks, limits and failure modes. Most teams end up maintaining plumbing instead of building product — and every new channel is another integration to keep alive.
What we built
A provider-neutral messaging layer: one API that reaches a person on any channel, through whichever providers are already in place, with automatic failover between them. Providers are swappable, and the application above never learns which one carried the message.
The hard part
Not the channels — the single recipient and consent graph underneath them. One identity per person across every channel, carrying their consent state, so that a reply on any channel routes back to the system that asked. We built the routing first and the identity model second, and had to invert that.
Where it runs now
In public use — the one venture in this set with real users today.
What this means for your project
It is the evidence behind messaging system integration, embedded engineering and white-label infrastructure. If you need transactional, multichannel or OTP messaging, this is the system we would bring.
One person, one identity — however the message got there.