I built CloudPostOffice because setting up MQTT brokers for simple messaging was overkill. Create postboxes, send messages between them — works with Python, Node.js, and Go.
Still early, I would love feedback from anyone building agents or realtime apps.
This is a clean problem to solve because a lot of agent/app messaging does not need the full weight of MQTT or custom broker setup. “Create postboxes, send messages between them” is simple enough that builders can understand the value immediately.
The part I’d lean into is not just simple messaging. It is lightweight agent communication infrastructure. If agents, apps, and workflows need to pass state, triggers, or small messages between each other, the value is in making that boring and reliable.
CloudPostOffice explains the metaphor well, but it may also make the product feel more playful than the infrastructure layer it could become. For agent infrastructure, a name like Exirra.com would give it a stronger systems feel while still leaving room beyond “postboxes” if this grows into routing, queues, webhooks, auth, logs, or multi-agent coordination.
The product idea is good because it removes setup friction. The brand should probably make builders feel they are plugging into a serious communication layer, not just trying a cute messaging utility.
Thank you.