Table of Contents [expand]
Last updated April 29, 2026
CloudAMQP is an add-on managing the largest fleet of LavinMQ and RabbitMQ clusters worldwide. LavinMQ is a high-performance message queue & streaming broker implementing the AMQP and MQTT protocols. RabbitMQ is a messaging and streaming broker, built in Erlang.
CloudAMQP automates the entire setup, operation, and scaling of LavinMQ and RabbitMQ clusters. Let your team focus on what they do best - building your product. Leave server management and monitoring to the experts.
Our control panel offers various tools for monitoring and alarms. Address performance issues promptly and automatically, before they impact your business. CloudAMQP makes it easy to set up custom alarms via email, webhooks, and external services.
CloudAMQP has unmatched operation experience from a wide variety of customers all over the world who count on us for 24/7 support. There’s no scaling or implementation problem we can’t solve.
All AMQP client libraries work with CloudAMQP and there’s AMQP client libraries for almost every platform out there, including Ruby, Node.js, Java, Python, Clojure and Erlang.
In the CloudAMQP documentation you will find lots of good resources to learn more.
Installing the add-on
CloudAMQP can be installed to a Heroku application via the CLI:
A list of all plans available can be found here.
$ heroku addons:create cloudamqp
-----> Adding cloudamqp to sharp-mountain-4005... done, v18 (free)
Example for Power Panda with one node:
$ heroku addons:create cloudamqp:panda-1
Once CloudAMQP has been added a CLOUDAMQP_URL setting will be available in the app configuration and will contain the canonical URL used to access the RabbitMQ cluster. This can be confirmed using the heroku config command.
$ heroku config | grep CLOUDAMQP_URL
CLOUDAMQP_URL => amqp://user:pass@ec2.clustername.cloudamqp.com/vhost
After installing CloudAMQP the application will be configured to fully integrate with the add-on.
Dashboard
The CloudAMQP dashboard allows you to show the current message rate, which queues and exchanges you have, and the bindings between them. You can also create queues and publish/consume messages manually, among other things.
The dashboard can be accessed via the CLI or by visiting the Heroku Dashboard and selecting the application in question. Select CloudAMQP from the Add-ons menu.
$ heroku addons:open cloudamqp
Opening cloudamqp for sharp-mountain-4005…
Separate applications
Virtual Hosts (vhosts) makes it possible to separate applications on one broker. You can isolate users, exchanges, queues etc to one specific vhost. You can separate environments, e.g. production to one vhost and staging to another vhost within the same broker, instead of setting up multiple brokers.
For shared plan, you are limited to a vhost that gets assigned to you. You can add vhosts on all dedicated instance.
Migrating between plans
Migrating between shared plans
Plan migrations are easy and instant when migrating between shared plans. Use the heroku addons:upgrade command to migrate to a new plan.
$ heroku addons:upgrade cloudamqp:rabbit-1
-----> Upgrading cloudamqp:rabbit-1 to sharp-mountain-4005... done, v18 ($600/mo)
Your plan has been updated to: cloudamqp:rabbit-1
Migrating between a shared plan and a dedicated plan
There is no automatic upgrade between a shared plan and a dedicated. Instead we recommend you to create the new plan and point your publishers to the new plan. Let your consumers empty the queues on the old plan and then point them to the new plan and finally delete the old plan.
Migrating between dedicated plans
You can automatically upgrade and downgrade between dedicated plans. It’s also possible to scale out to multi-node cluster or scale in to single-node.
$ heroku addons:upgrade cloudamqp:rabbit-3
-----> Upgrading cloudamqp:rabbit-3 to sharp-mountain-4005... done, v18 ($600/mo)
Your plan has been updated to: cloudamqp:rabbit
Removing the add-on
CloudAMQP can be removed via the CLI.
This will destroy all associated data and cannot be undone!
$ heroku addons:destroy cloudamqp
-----> Removing cloudamqp from sharp-mountain-4005... done, v20 (free)
Error codes
We log errors to your heroku log, below we explain the different codes.
410 - Transfer limit reached
You’ve reached your monthly transfer quota. Upgrade to a larger plan or wait until the next calendar month.
210 - Transfer in compliance
You’ve either upgraded your account (got a higher transfer limit) or it’s a new calendar month and your quota has been reset.
420 - Connection limit reached
You’re using all your connection slots so new connections will be blocked. Either lower your connection count or upgrade to larger plan to accommodate more connections.
220 - Connections in compliance
You can now open more connections again because you’re not using all connection slots.
431 - Max channels per connection
One of your connections was closed because you’d open to many channels on it. This is often due to a bug, so check your code and make sure that you close unused channels.
432 - Max consumers per connection
One of your connections was closed because it had opened more than 12000 consumers. This is often due to a bug, so make sure that you close unused consumers.
GDPR
Information about GDPR.
For all our customers who collect personal data from individuals in the EU, we offer a DPA. Our DPA offers terms that meet GDPR requirements and that reflects our data privacy and security commitments to our customers and their data.
Support
All CloudAMQP support and runtime issues should be logged with Heroku Support at support.heroku.com. Any non-support related issues or product feedback is welcome at support@cloudamqp.com. For dedicated plans, we provide 24/7 critical support, see our SLA.