I rate CloudAMQP a 9 on a scale from 1 to 10. I give it a 9 and not a higher score because it has many strengths and in my opinion no weaknesses. I would only give a 10 after the graphical aspects are improved in a minor way, but especially when log-related aspects are made a bit more streamlined, without necessarily having to move to other log visualization and aggregation tools such as Splunk. We use the on-premises solution on a Kubernetes cluster. For the rest of the architecture, we use both on-premises solutions and public clouds. CloudAMQP, specifically LavinMQ, runs on our Kubernetes cluster. The cloud provider I mainly use for these public cloud solutions is Amazon Web Services (AWS). My advice to other people who are considering using CloudAMQP is to first assess why they need it and what volume of messages they have to handle, what the requirements of the application or context are, and then evaluate whether to move forward. I would tell them to definitely go with CloudAMQP.
Freelancer at a tech vendor with 201-500 employees
Real User
Top 10
Oct 26, 2026
On a scale from one to ten, I rate CloudAMQP overall as nine. I give that number, nine, because there is always room for improvement. Regarding the AI features of CloudAMQP, I think the governance and security are adapting to the demands of the market, and while they have some things to improve, it is good. Regarding the accuracy and reliability of the results for the AI features of CloudAMQP, I think they are good, though there is room for improvement. CloudAMQP is generally deployed in private clouds in my organization. I use Google, Azure, and Amazon as my cloud providers. This setup uses Google Cloud. My advice for other people considering using CloudAMQP is that it is the best messaging tool there can be.
Tech Lead & Senior Software Engineer at a computer software company with 201-500 employees
Real User
Top 5
Oct 26, 2026
I rate CloudAMQP as eight based on the points that need improvement. I chose this score because of the points I brought up that still need improvement on the plans side, and also due to the lock-in that ends up being generated, which is a consequence of an enhancement, but you need to consider that as relevant and think very carefully if you're really going to adopt this solution. I stayed more on the development and operation side, monitoring queues and capacity increase needs. We use CloudAMQP in the same region we use on AWS as our public cloud. We also use it on-premises, using the LavinMQ container, which is part of and offered by the same company. CloudAMQP is a good starting point as a solution based on the AMQP protocol, as long as you don't have a need for high availability or very high capacity to start using a messaging service.
QA Automation Engineer at American Bureau of Shipment
Real User
Top 5
Oct 26, 2026
I would rate CloudAMQP a nine on a scale of one to ten. I definitely advise using CloudAMQP, and I think running good performance testing is necessary to fine-tune the connectors through AMQP for your business side and the programs that are running to send and receive messages.
Software Developer at a computer software company with 1,001-5,000 employees
Real User
Top 10
Oct 23, 2026
On a scale of 1 to 10, I rate CloudAMQP a 9, as it takes away almost all the operational pain of running RabbitMQ in production with minor room for improvements on pricing tiers. I chose a 9 out of 10 because it's rock-solid in production and removes all the operational headache of managing RabbitMQ clusters myself, with the reliability and the monitoring tools standing out most to me, giving me peace of mind during traffic peaks. I mainly treat CloudAMQP as the message backbone for my event pipelines and AI workflows, rather than an AI platform itself, and in terms of governance and security, it's very reliable, with features like VPC peering, TLS encryption, strict IP whitelisting, and role-based access control ensuring that the payload data feeding my models and services remains secure and compliant. Since CloudAMQP is a message broker and not a generative model, it doesn't produce AI outputs; however, for reliability in my AI pipeline, it's 100% accurate, with message delivery exact and acknowledgements preventing data loss, ensuring my models always receive the right payloads in order without corruption. CloudAMQP is deployed in my organization on the public cloud, specifically Azure, as a fully managed SaaS solution with private VPC peering in my existing infrastructure. I use Azure and AWS as my cloud providers. My advice for others looking into using CloudAMQP is to go for it if you want peace of mind, as running self-hosted RabbitMQ at 2:00 a.m. is no fun; CloudAMQP handles the boring infrastructure, allowing developers to focus on building software.
My advice for others looking into using CloudAMQP is that if you are choosing any message broker, you can go directly to CloudAMQP. However, before making a choice, at least check their plans according to your use case and do not blindly choose any plan. I would rate this product ten out of ten.
If you are considering CloudAMQP, my advice is to start with a small plan and learn RabbitMQ fundamentals such as queues, exchange, and routing keys early. CloudAMQP is excellent for microservices, background jobs, and event-driven systems because it reduces infrastructure and maintenance efforts significantly. Make good use of its monitoring and alerting features from the beginning and design your queues carefully for better scalability and performance. I would rate this product a ten out of ten.
CloudAMQP offers a managed RabbitMQ service in the cloud, providing reliable message queuing for apps of any scale. It supports seamless integration with existing infrastructure, enabling efficient data handling and communication channels.
Designed for scalability and ease of use, CloudAMQP ensures high availability and robust performance in distributed systems. Its managed RabbitMQ service allows businesses to focus on application development without managing servers. Comprehensive...
I rate CloudAMQP a 9 on a scale from 1 to 10. I give it a 9 and not a higher score because it has many strengths and in my opinion no weaknesses. I would only give a 10 after the graphical aspects are improved in a minor way, but especially when log-related aspects are made a bit more streamlined, without necessarily having to move to other log visualization and aggregation tools such as Splunk. We use the on-premises solution on a Kubernetes cluster. For the rest of the architecture, we use both on-premises solutions and public clouds. CloudAMQP, specifically LavinMQ, runs on our Kubernetes cluster. The cloud provider I mainly use for these public cloud solutions is Amazon Web Services (AWS). My advice to other people who are considering using CloudAMQP is to first assess why they need it and what volume of messages they have to handle, what the requirements of the application or context are, and then evaluate whether to move forward. I would tell them to definitely go with CloudAMQP.
On a scale from one to ten, I rate CloudAMQP overall as nine. I give that number, nine, because there is always room for improvement. Regarding the AI features of CloudAMQP, I think the governance and security are adapting to the demands of the market, and while they have some things to improve, it is good. Regarding the accuracy and reliability of the results for the AI features of CloudAMQP, I think they are good, though there is room for improvement. CloudAMQP is generally deployed in private clouds in my organization. I use Google, Azure, and Amazon as my cloud providers. This setup uses Google Cloud. My advice for other people considering using CloudAMQP is that it is the best messaging tool there can be.
I rate CloudAMQP as eight based on the points that need improvement. I chose this score because of the points I brought up that still need improvement on the plans side, and also due to the lock-in that ends up being generated, which is a consequence of an enhancement, but you need to consider that as relevant and think very carefully if you're really going to adopt this solution. I stayed more on the development and operation side, monitoring queues and capacity increase needs. We use CloudAMQP in the same region we use on AWS as our public cloud. We also use it on-premises, using the LavinMQ container, which is part of and offered by the same company. CloudAMQP is a good starting point as a solution based on the AMQP protocol, as long as you don't have a need for high availability or very high capacity to start using a messaging service.
I would rate CloudAMQP a nine on a scale of one to ten. I definitely advise using CloudAMQP, and I think running good performance testing is necessary to fine-tune the connectors through AMQP for your business side and the programs that are running to send and receive messages.
On a scale of 1 to 10, I rate CloudAMQP a 9, as it takes away almost all the operational pain of running RabbitMQ in production with minor room for improvements on pricing tiers. I chose a 9 out of 10 because it's rock-solid in production and removes all the operational headache of managing RabbitMQ clusters myself, with the reliability and the monitoring tools standing out most to me, giving me peace of mind during traffic peaks. I mainly treat CloudAMQP as the message backbone for my event pipelines and AI workflows, rather than an AI platform itself, and in terms of governance and security, it's very reliable, with features like VPC peering, TLS encryption, strict IP whitelisting, and role-based access control ensuring that the payload data feeding my models and services remains secure and compliant. Since CloudAMQP is a message broker and not a generative model, it doesn't produce AI outputs; however, for reliability in my AI pipeline, it's 100% accurate, with message delivery exact and acknowledgements preventing data loss, ensuring my models always receive the right payloads in order without corruption. CloudAMQP is deployed in my organization on the public cloud, specifically Azure, as a fully managed SaaS solution with private VPC peering in my existing infrastructure. I use Azure and AWS as my cloud providers. My advice for others looking into using CloudAMQP is to go for it if you want peace of mind, as running self-hosted RabbitMQ at 2:00 a.m. is no fun; CloudAMQP handles the boring infrastructure, allowing developers to focus on building software.
My advice for others looking into using CloudAMQP is that if you are choosing any message broker, you can go directly to CloudAMQP. However, before making a choice, at least check their plans according to your use case and do not blindly choose any plan. I would rate this product ten out of ten.
If you are considering CloudAMQP, my advice is to start with a small plan and learn RabbitMQ fundamentals such as queues, exchange, and routing keys early. CloudAMQP is excellent for microservices, background jobs, and event-driven systems because it reduces infrastructure and maintenance efforts significantly. Make good use of its monitoring and alerting features from the beginning and design your queues carefully for better scalability and performance. I would rate this product a ten out of ten.
CloudAMQP is a good tool, and if you are able to accommodate the costing, it is useful. I would rate this product an eight out of ten.