I got 84codes

Why take on a cloud broker service?

Diana Kupfer

JAXenter chats with the CEO of 84codes about their recent acquisition, CloudMQTT.

Last week, our German colleague Diane Kupfer interviewed Carl Hörberg, CEO of 84codes. This Swedish server hosting company has recently expanded its product portfolio to the MQTT broker service CloudMQTT. Here, Hörberg tells us where his team found their inspiration, and what lies ahead for the company.

JAXenter: How did you become interested in Machine-to-Machine communication?

Hörberg: We’ve been interested in application messaging since we were consultants and wrote big distributed applications. AMQP has been our go to protocol, but then MQTT sailed up and its simplicity and robustness is very appealing. As engineers we’re easily excited about embedded systems and what the Internet of Things makes possible.  

What exactly is CloudMQTT?  

CloudMQTT offers hosted MQTT Servers as a Service. Simply put, we allow developers to start using MQTT without the hassle of setting up, maintaining and scaling servers/brokers.

What would be good use cases?

Any company or developer looking to jumpstart their MQTT development, or a company that wants to free up their time to focus more on their core business.

These companies/developers are maybe creating things like “Fitbit for dogs” or something else that generates a lot of sensor data. Maybe MQTT could underpin the next Snapchat clone, just like it supports Facebook Messenger today.

When, and where, did you first hear about MQTT?

A friend of us sent us the TEDx video where Andy Standford-Clark from IBM shows his automated home and how all sensors and machines are communicating over MQTT.  


What prompted you to use it?

We have previously had great success with CloudAMQP, RabbitMQ as a Service, and figured that we might try the same thing for MQTT,  as it has a slightly different use case and it really seems to take off.

It says on your website that “MQTT is the Machine-to-Machine protocol of the future.” What makes you so confident that it is?  

The MQTT spec is very easy to read and understand, so it is easy for developers to implement in embedded system. Compare to other messaging alternatives, including rolling out your own, this is by far the easiest we’ve seen.  

What’s on the roadmap for CloudMQTT?

We already have the service up for testing. Now we want more users to validate the server scaling algorithm, while we spread the awareness of MQTT.

Diana Kupfer
Working at S&S Media since 2011, Diana Kupfer is an editor at Eclipse Magazine, Java Magazin and

Inline Feedbacks
View all comments