We were tired of gluing messaging tools together.
So we built the platform we wanted: one API for every channel, with the inbox, campaigns and automation that usually live in separate products, all in a single codebase you can actually own.
Most teams start with one transactional email provider. Then they add an SMS vendor for OTPs, a separate tool for campaigns, a help desk for replies, and a chat widget for the website. Each one arrives with another dashboard, another contacts list, and its own idea of what a “message” is. Nobody designs a stack like that. It accretes.
Messy collapses that sprawl. Just like the smartphone folded the camera, the map and the phone into a single device, Messy folds the whole messaging stack into a single platform. A message is a message, whatever shape it takes: an email or an SMS, a one-off receipt or a campaign to thousands, something you send out or something a customer sends back. Everything shares the same contact database and the same delivery rules, and you watch it all happen in one place.
We open-sourced it because messaging is too important to rent from a black box. Run it yourself for free, or let us host it. The platform is the same either way.
The principles behind the product
One place, not ten
Sending, conversations, campaigns and analytics belong together. Stitching five SaaS tools into a messaging stack is the problem, not the product.
Your data, your servers
The full platform is open source. Run it on your own infrastructure and nothing leaves your network unless you decide it should.
Provider-agnostic
We don't lock you to one delivery vendor. Bring SES today, swap to SMTP or Twilio tomorrow, and your code and templates don't change.
Built in the open
Every line is on GitHub under the Elastic License 2.0. Read it, fork it, send a pull request, or deploy it yourself. No black boxes.
The company behind Messy
Messy is a product of The Empire Holding B.V., a software company based in Rotterdam, the Netherlands. We build and maintain the platform, and run the cloud editions for teams who’d rather not host it themselves.