No Comments

    Leave a Reply

    12 + 14 =

    Our Story

    RoboMQ - Our Story Image
    It was 2012 when our founder and CEO Bramh Gupta was running middleware for telecom companies. He was managing critical business processes necessary for telecommunication business operations. This included cellular device activation and provisioning, where more than twenty-five systems would interact in less than 3 minutes to light up a cellular device on a network and create all the needed artifacts across telecom systems to onboard new customers. This was an operation of a massive scale when you think about the tens of millions of customers for a telecom company.

    With the adoption of Cloud, SaaS applications, and IoT into mainstream technology, it became clear to our founding team that the existing integration platforms, as well as the middleware technologies, would not fit the coming world. No SaaS or cloud application provider would code to or provide interfaces in proprietary APIs of the likes of TIBCO or IBM.

    “What the world really needed was a middleware that had no proprietary APIs or was API less, but could integrate with any of the hundreds of standard device and application protocols, or APIs, with conversion taken care of in the middleware itself.” – Bramh Gupta, CEO

    RoboMQ was born with this idea. Fred Yatzeck, who had been working alongside Bramh in his telecom days, formally joined to create the founding team and start shaping this dream into a reality.

    RoboMQ adopted containerization technologies and microservices early on. We provide a microservices based integration framework, including a visual business process designer for microservices. This passion drove us to run the core platform itself as docker containers.

    Another problem with the existing middleware technologies is the hub and spoke architecture that often fails at the center. RoboMQ solved this problem by creating a federated and distributed messaging fabric or a mesh, “Hybrid Messaging Cloud”, that can run on the cloud, on-premise, or even on IoT gateways and single board computers (SBCs).

    The result is a highly decoupled and distributed integration platform that treats devices, IoT gateways, SaaS applications and enterprise systems all as “first class citizens”. This allows you to build business workflows across clouds and networks to save cost, or create new revenue generation opportunities.

    Intrigued by our company? Contact us at or visit our website at for more information.

    Did you enjoy this article? Subscribe below for RoboMQ updates:

    No Comments

      Leave a Reply

      17 − 11 =

      You Might Also Like

      RoboMQ Launches a Major Upgrade to Connect iPaaS with Michelangelo Release

      RoboMQ Launches a Major Upgrade to Connect iPaaS with Michelangelo Release

      Last week, RoboMQ launched its last release of Connect iPaaS for 2019. This release was named Michelangelo, after the famed renaissance sculptor and painter of the Sistine Chapel in the Vatican. Michelangelo is the third release to go live…

      Why we chose Excel functions for API data transformation on Connect iPaaS?

      Why We Chose Excel Functions For API Data Transformation On Connect iPaaS?

      This week RoboMQ made available their first 2020 release of Connect iPaaS named Raphael, Sprint One.  Named after the famed Italian painter and the architect of the High Renaissance whose work is admired for its clarity of form, ease…

      Workflow Notification and Event Archival


      You have setup an integration workflow. It is working fine for you and is making your work easier. Now due to a change in the data provided by your trigger caused by some changes upstream in the source system, your integration…

      No Comments

      Leave a Reply

      four × 3 =