# CloudAMQP

> cloudamqp.com | Developer services; 2 records: free tier, limits, identity cost and evidence.

HTML https://fshy.ajam.dev/p/cloudamqp/ | JSON https://fshy.ajam.dev/api/v1/entity/cloudamqp.json | how to read a record: https://fshy.ajam.dev/llms-full.txt

## CloudAMQP (Little Lemur)

- `dev-services/cloudamqp-little-lemur` | qualifies-with-caveat | evidence documented | binding request-rate | category message queue broker: a vhost on a shared RabbitMQ broker | tier Little Lemur
- needs card no, phone no, ID no, institution no | verified 2026-11-02T00:38:24.165Z (live) | stale on 2026-12-03
- url https://www.cloudamqp.com/plans.html
- free tier: Little Lemur: 1 M messages a month, 20 connections, max 100 queues and max 10 000 queued messages on a shared RabbitMQ broker, free for as long as the instance is used, no card | unit: requests | metered on: request-count | read on: 2026-10-30 | source: [1] | note: The quota counts messages: a message counts once when it is published and once when it is consumed, so 1 M a month is about 500,000 messages that are both published and consumed. The monthly count resets on the first day of each month, and warning emails go out at 70 and 100 percent. An instance that crosses the queue or queued-message threshold is blocked from publishing and from creating queues. At the connection limit new connections are refused and existing ones stay up. Shared plans allow 200 channels per connection. An account may hold up to 49 free instances (650 once it has a paid instance).
- per-object cap: 128 MiB per message on CloudAMQP | bytes: 134217728 | source: [2]
- retention: A queue not consumed from for 28 days is deleted, temporary queues are deleted after 60 seconds, and a free instance with no message published or consumed during the latest two months is deleted after a warning email | source: [1] | note: Activity-based: an instance and its queues survive as long as messages move. The 28-day idle-queue limit is listed on the plans page for Little Lemur and was introduced on shared plans in 2017.
- egress: Data transfer is included within a fair-use allowance equal to 30% of the team's monthly spend; usage above it may be charged after a 30-day grace period | metered: yes | free allowance: unverified: the allowance is stated as 30% of team spend, and no page states a figure for a team that holds only free instances | source: [1]
- identity: email | detail: The signup page asks for an email address, or a GitHub or Google sign-in; the plans page states no credit card is required for the free shared plans. The vendor's getting-started steps are create an account, choose a plan and create the instance, and name no phone step; whether the signup flow itself asks for a phone number is unverified: behind a sign-up.
- interface: rest, unknown
- limits:
  - request-rate (binding): 1 M messages per month, counted on publish and on consume, reset on the first day of the month [1]
  - per-object-cap: 128 MiB per message [2]
  - retention-clamped: queues idle for 28 days deleted; temporary queues deleted after 60 seconds; instance deleted after two months with no message [3]
- limits note: 20 concurrent connections, max 100 queues and max 10 000 queued messages per instance, and 200 channels per connection. Crossing the queue or queued-message threshold blocks publishing and queue creation; at the connection limit new connections are refused. The vocabulary has no kind for a concurrency or a backlog cap.
- binding note: 1 M messages a month is about 33,000 a day (1,000,000 / 30), and a message that is published and consumed counts twice, so a steady job queue meets the monthly count before the 20-connection or 10 000-message backlog caps.
- interface detail: Broker protocols AMQP 0.9.1 (ports 5672, and 5671 for AMQPS), AMQP 1.0, MQTT, STOMP, HTTP(S) and WebSockets; the interface vocabulary has no term for AMQP, MQTT, STOMP or WebSocket, so they are listed here. Instances, teams and keys are managed through the CloudAMQP Customer API at https://customer.cloudamqp.com/api, which answers 401 without an API key.
- endpoint: part of interface detail
- tooling: Any AMQP 0.9.1 client library, an MQTT or STOMP client, the CloudAMQP Customer API with an API key as the HTTP basic password, and the cloudamqp Terraform provider.
- composes with: A durable work queue between a scheduler that publishes jobs and free compute workers that consume them, sized for about 33,000 message events a day.
- reliability: A free instance with no message published or consumed for two months is deleted after a warning email; shared vhosts sit on a multi-tenant broker where other users' load can affect performance.
- notes: CloudAMQP's other free shared plan, Loyal Lemming, runs on LavinMQ rather than RabbitMQ and is another tier with its own quotas. Paid shared RabbitMQ (Tough Tiger) is USD 19 a month for 10 M messages and 100 connections.
- evidence note: Every limit is quoted from a first-party page; the management API host was probed and answered 401 without a key. No broker connection was made, because a broker URL exists only inside an account. A probe of an AMQPS connection with an account's URL would move it to measured.
- evidence:
  - [1] 2026-10-30: Little Lemur and Loyal Lemming are free with no time limit and no credit card | quote: Yes. Our free shared plans, Little Lemur (RabbitMQ) and Loyal Lemming (LavinMQ), are free to use for as long as you like — no credit card required to get started.
  - [1] 2026-10-30: Little Lemur gives 1 M messages a month and 20 connections at no cost | quote: Message quota/month 1 M Connection limit 20 Free
  - [1] 2026-10-30: Little Lemur holds at most 10 000 queued messages | quote: Max 10 000 queued messages
  - [1] 2026-10-30: Little Lemur deletes a queue idle for 28 days | quote: Max idle queue time 28 days
  - [1] 2026-10-30: a free instance with no traffic in two months is deleted after a warning email | quote: Free instances that have not published or consumed a single message during the latest two months are deleted, after a warning email.
  - [1] 2026-10-30: data transfer is a fair-use allowance of 30% of team spend | quote: Each plan includes free data transfer equal to 30% of your team's spend each month.
  - [1] 2026-10-30: shared RabbitMQ supports AMQP 0.9.1, HTTP(S), MQTT and WebSockets | quote: All clusters support AMQP 0.9.1, HTTP(S), MQTT, and WebSockets.
  - [1] 2026-10-30: shared RabbitMQ also supports AMQP 1.0 and STOMP | quote: RabbitMQ also supports AMQP 1.0 and STOMP on shared and dedicated plans; LavinMQ supports neither.
  - [3] 2026-10-30: the monthly quota counts a message on publish and again on consume | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: One message is counted as consumed when a message is published from your service to the broker (RabbitMQ or LavinMQ) or when one message is consumed from the broker.
  - [3] 2026-10-30: the message quota of shared instances resets on the first day of the month | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: The reset is performed the first day every month.
  - [3] 2026-10-30: warning emails at 70 and 100 percent of the quota | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: You will get warnings via email when you have used 70 and 100 percent of your allowed usage.
  - [3] 2026-10-30: an account may hold up to 49 free instances, 650 once it has a paid instance | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: You are allowed a maximum of 49 free instances. If you need more instances, please upgrade to one of our paid plans. Customers with at least one paid instance are allowed a maximum of 650 free instances.
  - [3] 2026-10-30: shared plans allow 200 channels per connection | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: We limit all shared plans to 200 channels per connection.
  - [3] 2026-10-30: an abandoned Little Lemur instance is deleted after two months without traffic | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: Little Lemur (RabbitMQ) and Loyal Lemming (LavinMQ) instances that are abandoned/not used during the latest two months will be deleted.
  - [4] 2026-10-30: on shared plans idle queues are deleted after 28 days and temporary queues after 60 seconds | capture: sha256:301fd6993db9703f6f23f3fb1c16b0c6c80064f6faad0d9fd9e0a2900f99b4b1 | quote: A queue that has been idling (a queue that haven't been consumed from) for 28 days will be deleted, and temporary queues will be deleted after 60 seconds.
  - [5] 2026-10-30: crossing the queue or queued-message threshold blocks publishing and queue creation | capture: sha256:c16af864443c11ec2f3b4023853bced6d9d80f569f09e2ca7d1ae19a1966212a | quote: The instance will be blocked from publishing of messages/creation of new queues, when the number of messages or the number of queues crosses the limit thresholds.
  - [2] 2026-10-30: CloudAMQP caps a RabbitMQ message at 128 MiB | capture: sha256:39a9f98d47522283888e44f6dbec7c742e6ad7f578669fe58afbd373bebf82f0 | quote: On CloudAMQP we limit message size at 128MiB.
  - [6] 2026-10-30: AMQP listens on 5672 and AMQPS on 5671 | capture: sha256:6cfdc546a73b899d67fe4ad6e619cb1577d4a70b0ecc1c230e6ef7666a720ede | quote: AMQP assigned port number is 5672 or 5671 for AMQPS (TLS/SSL encrypted AMQP).
  - [7] 2026-10-30: a REST API manages instances and the team | capture: sha256:4d571dc466cfc084e62bac455d70af07db1786a34a29192fc55a2245ff8e658b | quote: This API allows you to create and edit your instances, manage your team, invoices etc.
  - [7] 2026-10-30: the Customer API is served at customer.cloudamqp.com/api | capture: sha256:4d571dc466cfc084e62bac455d70af07db1786a34a29192fc55a2245ff8e658b | quote: Server:https://customer.cloudamqp.com/api
  - [8] 2026-10-30: the signup asks for an email, or a GitHub or Google sign-in | capture: sha256:6d68582d3dc925366a1acc5163a1f54c6f1fbd8a8e8bc6688d653a4c94a104f8 | quote: or use a third-party service
  - [1] 2026-10-30: Little Lemur holds at most 100 queues | quote: Max 100 queues
  - [1] 2026-10-30: traffic above the fair-use allowance may be charged after 30 days | quote: Teams that use more may be subject to additional charges: after an overage you have 30 days to resolve it before traffic charges are added to later invoices.
  - [1] 2026-10-30: the paid shared RabbitMQ plan Tough Tiger is USD 19 a month for 10 M messages and 100 connections | quote: Message quota/month 10 M Connection limit 100 $19/mo
  - [3] 2026-10-30: at the connection limit new connections are refused and existing ones are kept | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: With max connections you will be unable to establish new connections, existing connections are not affected.
  - [4] 2026-10-30: shared instances are vhosts on a multi-tenant server where other tenants affect performance | capture: sha256:301fd6993db9703f6f23f3fb1c16b0c6c80064f6faad0d9fd9e0a2900f99b4b1 | quote: Little Lemur and Tough Tiger instances are virtual hosts (vhosts) located on a shared server, where other users' actions might affect the performance of the whole server.
  - probe:https://customer.cloudamqp.com/api/instances 2026-10-31: the Customer API host answers and refuses a request with no API key | capture: sha256:03cdb4c7e88434aa39c648b20252b65c437c458aa7133071a0b6866ba5b7789b | quote: "status": 401
  - [1] 2026-10-31: Loyal Lemming is CloudAMQP's other free shared plan and runs on LavinMQ, while Little Lemur runs on RabbitMQ | quote: Yes. Our free shared plans, Little Lemur (RabbitMQ) and Loyal Lemming (LavinMQ), are free to use for as long as you like — no credit card required to get started.
  - [1] 2026-10-31: Little Lemur still gives 1 M messages a month and 20 connections at no cost | quote: Message quota/month 1 M Connection limit 20 Free
  - [9] 2026-11-01: the getting-started steps are create an account, choose a broker and plan, and create the instance, with no phone step | capture: sha256:0874289502eca4199cf80841bd886e17c0a0fcdc42a968d2f7a927bf3e6b62b6 | quote: 1. Create a CloudAMQP account. 2. Choose your broker and plan. 3. Create the instance.
  - [9] 2026-11-01: the free plan needs no billing information | capture: sha256:0874289502eca4199cf80841bd886e17c0a0fcdc42a968d2f7a927bf3e6b62b6 | quote: Free plan: No billing information required.
  - [9] 2026-11-01: shared plans allow 200 channels per connection and 200 consumers per channel | capture: sha256:0874289502eca4199cf80841bd886e17c0a0fcdc42a968d2f7a927bf3e6b62b6 | quote: All shared plans have a channel limit of 200 and a maximum of 200 consumers per channel.
  - [3] 2026-11-01: every RabbitMQ plan, shared ones included, supports AMQP 0-9-1, AMQP 1.0, AMQPS, HTTPS, STOMP, MQTT and WebSockets | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: All our RabbitMQ plans, shared and dedicated, have protocol support for AMQP 0-9-1, AMQP 1.0, AMQPS, HTTPS, STOMP, MQTT, and WebSockets.
  - [10] 2026-11-01: RabbitMQ MQTT is available on all plans at port 1883, and 8883 with TLS | capture: sha256:6676f24cc440145cf526cbedfff4226212adb332c997388ce9537d80dd7cb537 | quote: The MQTT plugin is available on all plans. ... The port used for MQTT is 1883 (8883 for TLS wrapped MQTT).
  - [11] 2026-11-01: STOMP runs on shared RabbitMQ plans at port 61613, and 61614 with TLS | capture: sha256:eafd5cfbb30e9bee6d17ff65752c10eb54a2d521be467b2e77d1f69f67ffd54f | quote: all CloudAMQP have the Stomp plugin running on port 61613 (TLS: 61614). ... On CloudAMQP, STOMP is available on shared and dedicated RabbitMQ plans.
  - [12] 2026-11-01: AMQP over WebSockets is available on all CloudAMQP plans and is served over wss at the path /ws/amqp | capture: sha256:8b0c1ba24aa9f78274f852cac4c6b5acde021c0dacc29bca30670ae7904eb320 | quote: This feature is available on all CloudAMQP plans ... You must use the Secure WebSockets protocol(wss) and connect to the endpoint at “/ws/amqp”
  - [3] 2026-11-01: the FAQ states the data transfer allowance as 30% of team spend and gives no figure for a team with no spend | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: Each plan includes a certain amount of free data transfer which can be calculated as 30% of the team spend each month. Teams that use more than these limits may be subject to additional charges.
  - probe:https://customer.cloudamqp.com/api/instances 2026-11-01: the Customer API host answers and refuses a request with no API key | capture: sha256:864fad1020fd6c767b2c687a39d233555dc5e4b3c252de81acf84afed2638c98 | quote: "status": 401
  - [1] 2026-11-01: the plans page lists Little Lemur with 1 M messages a month, 20 connections, 100 queues, 10 000 queued messages and a 28-day idle queue limit at no cost, unchanged | quote: For Development - Shared RabbitMQ broker - Max 100 queues - Max 10 000 queued messages - Max idle queue time 28 days Message quota/month 1 M Connection limit 20 Free
- sources:
  - [1] https://www.cloudamqp.com/plans.html
  - [2] https://www.cloudamqp.com/blog/what-is-the-message-size-limit-in-rabbitmq/
  - [3] https://www.cloudamqp.com/docs/faq/
  - [4] https://www.cloudamqp.com/blog/new-limit-for-shared-plans.html
  - [5] https://www.cloudamqp.com/blog/added-limits-for-shared-plans.html
  - [6] https://www.cloudamqp.com/docs/amqp/
  - [7] https://docs.cloudamqp.com/
  - [8] https://customer.cloudamqp.com/signup
  - [9] https://www.cloudamqp.com/docs/
  - [10] https://www.cloudamqp.com/docs/mqtt/
  - [11] https://www.cloudamqp.com/docs/stomp/
  - [12] https://www.cloudamqp.com/docs/amqp-over-websockets/

## CloudAMQP (Loyal Lemming)

- `dev-services/cloudamqp-loyal-lemming` | qualifies-with-caveat | evidence documented | binding request-rate | category message queue broker: a vhost on a shared LavinMQ broker | tier Loyal Lemming
- needs card no, phone no, ID no, institution no | verified 2026-11-02T00:38:24.167Z (live) | stale on 2026-12-03
- url https://www.cloudamqp.com/plans.html
- free tier: Loyal Lemming: 2 M messages a month, 40 connections, max 200 queues and max 20 000 queued messages on a shared LavinMQ broker, free for as long as the instance is used, no card | unit: requests | metered on: request-count | read on: 2026-10-31 | source: [1] | note: The quota counts messages: a message counts once when it is published and once when it is consumed, so 2 M a month is about 1,000,000 messages that are both published and consumed. The monthly count of shared instances resets on the first day of each month, and warning emails go out at 70 and 100 percent. At the connection limit new connections are refused and existing ones stay up. Shared plans allow 200 channels per connection. An account may hold up to 49 free instances (650 once it has a paid instance), Little Lemur and Loyal Lemming together.
- per-object cap: 128 MB per message on LavinMQ (written 128mb), configurable | source: [2] | note: The page writes 128mb without saying whether it means MB or MiB, so no byte count is recorded.
- retention: A free instance with no message published or consumed during the latest two months is deleted after a warning email; the plans page lists no idle-queue limit for Loyal Lemming | source: [1] | note: Activity-based: an instance survives as long as messages move, and the warning email offers to wake the instance up. The plans page listed Max idle queue time 28 days under Loyal Lemming in the archived copies of 2023-12-18 and 2025-08-03; the archived copy of 2025-11-18 and the current page list it under Little Lemur and Tough Tiger and not under Loyal Lemming. The 28-day idle-queue and 60-second temporary-queue rules were scheduled for 2017-03-02 in a post that names Little Lemur and Tough Tiger. Whether either rule applies on shared LavinMQ now is unverified: behind a sign-up.
- egress: Data transfer is included within a fair-use allowance equal to 30% of the team's monthly spend; usage above it may be charged after a 30-day grace period | metered: yes | free allowance: unverified: the allowance is stated as 30% of team spend, and no page states a figure for a team that holds only free instances | source: [1]
- identity: email | detail: The signup page asks for an email address, or a GitHub or Google sign-in, and an email signup is confirmed by a link sent to the inbox; the plans page states no credit card is required for the free shared plans. The vendor's steps for a LavinMQ instance are create the account, verify the email address and create the instance, and name no phone step; whether the signup flow itself asks for a phone number is unverified: behind a sign-up.
- interface: rest, unknown
- limits:
  - request-rate (binding): 2 M messages per month, counted on publish and on consume, reset on the first day of the month [1]
  - per-object-cap: 128 MB per message (written 128mb), configurable [2]
  - retention-clamped: instance deleted after two months with no message published or consumed [3]
- limits note: 40 concurrent connections, max 200 queues and max 20 000 queued messages per instance, and 200 channels per connection. At the connection limit new connections are refused. The vocabulary has no kind for a concurrency or a backlog cap.
- binding note: 2 M messages a month is about 66,667 a day (2,000,000 / 30), and a message that is published and consumed counts twice, so a steady job queue meets the monthly count before the 40-connection or 20 000-message backlog caps.
- interface detail: Broker protocols AMQP 0.9.1, MQTT, HTTP and WebSockets; LavinMQ supports neither AMQP 1.0 nor STOMP. A hosted LavinMQ instance has its own hostname, and its management interface is at https://{hostname}.lmq.cloudamqp.com. The interface vocabulary has no term for AMQP, MQTT or WebSocket, so they are listed here. The shared plans include streams, webhooks (push-queues) and the built-in delayed message exchange of LavinMQ. Instances, teams and keys are managed through the CloudAMQP Customer API at https://customer.cloudamqp.com/api.
- endpoint: part of interface detail
- tooling: Any AMQP 0-9-1 client library, many RabbitMQ-compatible ones included, an MQTT client, the CloudAMQP Customer API with an API key as the HTTP basic password and an empty username, and the cloudamqp Terraform provider, which names the plan lemming.
- composes with: A durable work queue between a scheduler that publishes jobs and free compute workers that consume them, sized for about 66,667 message events a day; the larger of the two free CloudAMQP shared plans.
- reliability: A free instance with no message published or consumed for two months is deleted after a warning email; a Lemming instance is a vhost on a multi-tenant LavinMQ broker that shares hardware with other instances, and the vendor lists the shared plans as not recommended for production because of variable performance.
- notes: The other free CloudAMQP shared plan, Little Lemur on RabbitMQ, has half the quota and is a separate record. Paid shared LavinMQ (Elegant Ermine) is USD 19 a month for 20 M messages, 200 connections, max 2000 queues and max 200 000 queued messages. A shared LavinMQ instance can move to a single-node dedicated LavinMQ plan from the console, and it gets a new hostname.
- evidence note: Every limit is quoted from a first-party page; the management API host was probed and answered 401 without a key. No broker connection was made, because a broker URL exists only inside an account. A probe of an AMQPS connection with an account's URL would move it to measured.
- evidence:
  - [1] 2026-10-31: Little Lemur and Loyal Lemming are free with no time limit and no credit card | quote: Yes. Our free shared plans, Little Lemur (RabbitMQ) and Loyal Lemming (LavinMQ), are free to use for as long as you like — no credit card required to get started.
  - [1] 2026-10-31: Loyal Lemming is a vhost on a shared LavinMQ broker | quote: A vhost on a shared LavinMQ broker. For development, prototypes and small hobby projects.
  - [1] 2026-10-31: Loyal Lemming gives 2 M messages a month and 40 connections at no cost | quote: Message quota/month 2 M Connection limit 40 Free
  - [1] 2026-10-31: Loyal Lemming holds at most 200 queues | quote: Max 200 queues
  - [1] 2026-10-31: Loyal Lemming holds at most 20 000 queued messages | quote: Max 20 000 queued messages
  - [1] 2026-10-31: a free instance with no traffic in two months is deleted after a warning email | quote: Free instances that have not published or consumed a single message during the latest two months are deleted, after a warning email.
  - [1] 2026-10-31: the idle-queue limit of 28 days is listed for the shared RabbitMQ plans | quote: Max idle queue time 28 days
  - [1] 2026-10-31: data transfer is a fair-use allowance of 30% of team spend | quote: Each plan includes free data transfer equal to 30% of your team's spend each month.
  - [1] 2026-10-31: traffic above the fair-use allowance may be charged after 30 days | quote: Teams that use more may be subject to additional charges: after an overage you have 30 days to resolve it before traffic charges are added to later invoices.
  - [1] 2026-10-31: LavinMQ supports neither AMQP 1.0 nor STOMP | quote: RabbitMQ also supports AMQP 1.0 and STOMP on shared and dedicated plans; LavinMQ supports neither.
  - [1] 2026-10-31: the shared plans include streams | quote: | Streams | Included | Included | Included |
  - [1] 2026-10-31: the shared plans include webhooks (push-queues) | quote: | Webhooks (Push-Queues) | Included | Included | Included |
  - [1] 2026-10-31: the shared LavinMQ plans include the built-in delayed message exchange | quote: | Delayed Message Exchange (built-in) | Included (LavinMQ) | Included | – |
  - [1] 2026-10-31: the paid shared LavinMQ plan Elegant Ermine is USD 19 a month for 20 M messages and 200 connections | quote: Message quota/month 20 M Connection limit 200 $19/mo
  - [1] 2026-10-31: Elegant Ermine holds at most 2000 queues | quote: Max 2000 queues
  - [1] 2026-10-31: Elegant Ermine holds at most 200 000 queued messages | quote: Max 200 000 queued messages
  - [4] 2026-10-31: shared LavinMQ supports AMQP 0-9-1, HTTP, MQTT and WebSockets | capture: sha256:1379f348f0338c4eddcf5127ea71d7f60fe2f933338a5e22ab71d22638c08d83 | quote: LavinMQ supports AMQP 0-9-1, HTTP, MQTT, and WebSockets on both shared and dedicated CloudAMQP plans.
  - [4] 2026-10-31: RabbitMQ-compatible AMQP 0-9-1 client libraries work with LavinMQ | capture: sha256:1379f348f0338c4eddcf5127ea71d7f60fe2f933338a5e22ab71d22638c08d83 | quote: Yes. LavinMQ implements AMQP 0-9-1, allowing applications to use many existing RabbitMQ-compatible client libraries.
  - [3] 2026-10-31: the monthly quota counts a message on publish and again on consume | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: One message is counted as consumed when a message is published from your service to the broker (RabbitMQ or LavinMQ) or when one message is consumed from the broker.
  - [3] 2026-10-31: the message quota of shared instances resets on the first day of the month | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: The reset is performed the first day every month.
  - [3] 2026-10-31: warning emails at 70 and 100 percent of the quota | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: You will get warnings via email when you have used 70 and 100 percent of your allowed usage.
  - [3] 2026-10-31: at the connection limit new connections are refused and existing ones are kept | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: With max connections you will be unable to establish new connections, existing connections are not affected.
  - [3] 2026-10-31: an account may hold up to 49 free instances, 650 once it has a paid instance | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: You are allowed a maximum of 49 free instances. If you need more instances, please upgrade to one of our paid plans. Customers with at least one paid instance are allowed a maximum of 650 free instances.
  - [3] 2026-10-31: shared plans allow 200 channels per connection | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: We limit all shared plans to 200 channels per connection.
  - [3] 2026-10-31: an abandoned Loyal Lemming instance is deleted after two months without traffic | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: Little Lemur (RabbitMQ) and Loyal Lemming (LavinMQ) instances that are abandoned/not used during the latest two months will be deleted.
  - [3] 2026-10-31: the deletion warning email offers to wake the instance up | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: You will receive a warning email before the instance is deleted, from where you have the option to wake up the instance.
  - [3] 2026-10-31: a shared LavinMQ plan can be moved to a single-node dedicated plan from the console | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: You can migrate directly from a shared plan to a single-node dedicated plan via the CloudAMQP console
  - [3] 2026-10-31: the migrated instance gets a new hostname | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: Your cluster will receive a new hostname after the migration.
  - [2] 2026-10-31: LavinMQ caps a message at 128mb, configurable | capture: sha256:39a9f98d47522283888e44f6dbec7c742e6ad7f578669fe58afbd373bebf82f0 | quote: For LavinMQ max message size is 128mb. Max message is configurable.
  - [5] 2026-10-31: the shared plans are not recommended for production because of variable performance | capture: sha256:febacc6f4850a0ef61a3df69122b50aa810c0ce0621a092cc0e2929a62fcb99b | quote: For development or small hobby projects. Not recommended for production due to variable performance.
  - [5] 2026-10-31: an email signup is confirmed by a link sent to the inbox | capture: sha256:febacc6f4850a0ef61a3df69122b50aa810c0ce0621a092cc0e2929a62fcb99b | quote: In case you signed up with email address you need to verify your account by clicking the link sent to your inbox.
  - [6] 2026-10-31: the Lemming plan shares underlying hardware with other instances | capture: sha256:8173de0da1cb561acfdb08886feb1337d9189cd06b673cbd3c1f4c7a5d9d01e0 | quote: `Lemming`and `Ermine` are shared instances and share underlying hardware with other instances.
  - [6] 2026-10-31: the Terraform provider names the Loyal Lemming plan lemming, type shared | capture: sha256:8173de0da1cb561acfdb08886feb1337d9189cd06b673cbd3c1f4c7a5d9d01e0 | quote: | Loyal Lemming | lemming | shared |
  - [7] 2026-10-31: a REST API manages instances and the team | capture: sha256:4d571dc466cfc084e62bac455d70af07db1786a34a29192fc55a2245ff8e658b | quote: This API allows you to create and edit your instances, manage your team, invoices etc.
  - [7] 2026-10-31: the Customer API is served at customer.cloudamqp.com/api | capture: sha256:4d571dc466cfc084e62bac455d70af07db1786a34a29192fc55a2245ff8e658b | quote: Server:https://customer.cloudamqp.com/api
  - [7] 2026-10-31: the API key is sent as the HTTP basic password with an empty username | capture: sha256:4d571dc466cfc084e62bac455d70af07db1786a34a29192fc55a2245ff8e658b | quote: Enter your Instance API key as password. Leave username empty.
  - [8] 2026-10-31: the signup asks for an email, or a GitHub or Google sign-in | capture: sha256:215ce2133dd625a7a2cc93e95309a3ee54e7a53a65b6e788bbc1d188d6531061 | quote: or use a third-party service
  - probe:https://customer.cloudamqp.com/api/instances 2026-10-31: the Customer API host answers and refuses a request with no API key | capture: sha256:03cdb4c7e88434aa39c648b20252b65c437c458aa7133071a0b6866ba5b7789b | quote: "status": 401
  - [9] 2026-11-01: the 28-day idle-queue and 60-second temporary-queue rules were announced for shared plans in a post that names Little Lemur and Tough Tiger | capture: sha256:301fd6993db9703f6f23f3fb1c16b0c6c80064f6faad0d9fd9e0a2900f99b4b1 | quote: A queue that has been idling (a queue that haven't been consumed from) for 28 days will be deleted, and temporary queues will be deleted after 60 seconds. ... Little Lemur and Tough Tiger instances are virtual hosts (vhosts) located on a shared server
  - [5] 2026-11-01: the steps to a LavinMQ instance are create the account, verify the email address and create the instance, with no phone step | capture: sha256:febacc6f4850a0ef61a3df69122b50aa810c0ce0621a092cc0e2929a62fcb99b | quote: Step 1: Create CloudAMQP account Sign Up Step 2: Verify your email address In case you signed up with email address you need to verify your account by clicking the link sent to your inbox. Step 3: Create LavinMQ instance
  - [10] 2026-11-01: a LavinMQ instance hosted by CloudAMQP has its management interface at https://{hostname}.lmq.cloudamqp.com | capture: sha256:492aeddbebf257ffa36fb7f74ad1126494bbfd3d1462d661ff2cd6ff45d05ab5 | quote: The LavinMQ Management Interface can be accessed using a Web browser at `http://localhost:15672` if running it locally, or `https://{hostname}.lmq.cloudamqp.com` if hosted by CloudAMQP.
  - [11] 2026-11-01: the plans page copy archived on 2023-12-18 lists Max idle queue time 28 days under Loyal Lemming | capture: sha256:009fdd882e4f0d64636d96e7febd719ab762f068047311aab3a937a17eb81e17 | quote: Loyal Lemming - Max 200 queues - Max 20 000 queued messages - Max idle queue time 28 days
  - [12] 2026-11-01: the plans page copy archived on 2025-08-03 lists Max idle queue time 28 days under Loyal Lemming | capture: sha256:ea0eef337f10ae56b9ab69766346cd01e0666440f930d6251cd968804334d4c7 | quote: Loyal Lemming - Max 200 queues - Max 20 000 queued messages - Max idle queue time 28 days
  - [13] 2026-11-01: the plans page copy archived on 2025-11-18 lists no idle queue time under Loyal Lemming | capture: sha256:473b9efa1302b775777fef9dcf380e6236a3ccaabba03dc44a95e43deb5d253e | quote: Loyal Lemming - Max 200 queues - Max 20 000 queued messages - Shared LavinMQ broker 2 M Message quota/month 40 Connection limit FREE
  - [13] 2026-11-01: the plans page copy archived on 2025-11-18 lists Max idle queue time 28 days under Tough Tiger | capture: sha256:473b9efa1302b775777fef9dcf380e6236a3ccaabba03dc44a95e43deb5d253e | quote: Tough Tiger - For Hobby Apps - Max 1000 queues - Max 100 000 queued messages - Max idle queue time 28 days - Shared RabbitMQ broker
  - [13] 2026-11-01: the plans page copy archived on 2025-11-18 lists Max idle queue time 28 days under Little Lemur | capture: sha256:473b9efa1302b775777fef9dcf380e6236a3ccaabba03dc44a95e43deb5d253e | quote: Little Lemur - For Development - Max 100 queues - Max 10 000 queued messages - Max idle queue time 28 days - Shared RabbitMQ broker
  - [1] 2026-11-01: the plans page lists Max idle queue time 28 days under Tough Tiger | quote: For Hobby Apps - Shared RabbitMQ broker - Max 1000 queues - Max 100 000 queued messages - Max idle queue time 28 days
  - [14] 2026-11-01:  | capture: sha256:95379152c28c22ccf789ca23696254cf3b9c9ab6a41a76054487a468d1de7a73 | quote: Connection URL, server name, user/vhost, and password are available on the instance details page in the CloudAMQP console.
  - [3] 2026-11-01: the FAQ states the data transfer allowance as 30% of team spend and gives no figure for a team with no spend | capture: sha256:b5ee62c7f162f75d94135f7376c2df66f7fcad74838801bd2eea2b8209aa9c8d | quote: Each plan includes a certain amount of free data transfer which can be calculated as 30% of the team spend each month. Teams that use more than these limits may be subject to additional charges.
  - [15] 2026-11-01: shared plans allow 200 channels per connection and 200 consumers per channel | capture: sha256:0874289502eca4199cf80841bd886e17c0a0fcdc42a968d2f7a927bf3e6b62b6 | quote: All shared plans have a channel limit of 200 and a maximum of 200 consumers per channel.
  - [15] 2026-11-01: the free plan needs no billing information | capture: sha256:0874289502eca4199cf80841bd886e17c0a0fcdc42a968d2f7a927bf3e6b62b6 | quote: Free plan: No billing information required.
  - [16] 2026-11-01: LavinMQ serves MQTT with no plugin on port 1883, with QoS 0 and 1 | capture: sha256:6676f24cc440145cf526cbedfff4226212adb332c997388ce9537d80dd7cb537 | quote: MQTT version 3.1 is supported in LavinMQ with no plugin needed. QOS levels 0 and 1 are available. Port 1883 is used for MQTT.
  - probe:https://customer.cloudamqp.com/api/instances 2026-11-01: the Customer API host answers and refuses a request with no API key | capture: sha256:864fad1020fd6c767b2c687a39d233555dc5e4b3c252de81acf84afed2638c98 | quote: "status": 401
  - [1] 2026-11-01: the plans page lists Loyal Lemming with 2 M messages a month, 40 connections, 200 queues and 20 000 queued messages at no cost, and lists no idle queue time for it | quote: Loyal Lemming - Shared LavinMQ broker - Max 200 queues - Max 20 000 queued messages Message quota/month 2 M Connection limit 40 Free
- sources:
  - [1] https://www.cloudamqp.com/plans.html
  - [2] https://www.cloudamqp.com/blog/what-is-the-message-size-limit-in-rabbitmq/
  - [3] https://www.cloudamqp.com/docs/faq/
  - [4] https://www.cloudamqp.com/docs/faq-lavinmq.html
  - [5] https://lavinmq.com/cloudamqp
  - [6] https://registry.terraform.io/providers/cloudamqp/cloudamqp/latest/docs/guides/info_plan
  - [7] https://docs.cloudamqp.com/
  - [8] https://customer.cloudamqp.com/signup
  - [9] https://www.cloudamqp.com/blog/new-limit-for-shared-plans.html
  - [10] https://lavinmq.com/documentation/management-interface-overview
  - [11] https://web.archive.org/web/20231218070709/https://www.cloudamqp.com/plans.html
  - [12] https://web.archive.org/web/20250803095701/https://www.cloudamqp.com/plans.html
  - [13] https://web.archive.org/web/20251118233813/https://www.cloudamqp.com/plans.html
  - [14] https://www.cloudamqp.com/docs/lavinmq-server.html
  - [15] https://www.cloudamqp.com/docs/
  - [16] https://www.cloudamqp.com/docs/mqtt/