Development
RabbitMQ on a VPS: the AMQP message broker behind your job queues, with its web management console served over HTTPS.
In validation
RabbitMQ is a free, open-source message broker (MPL-2.0 licence) and the most widely deployed AMQP server. Your applications drop messages into it — an invoice to generate, an email to send, an image to resize — and workers consume them at their own pace: a traffic spike no longer takes the site down, and a failed job is retried instead of lost. Laravel, Django with Celery, Spring, Node.js, .NET or Go connect to it with their usual libraries.
A single container is enough, with the web management console to watch queues, rates and consumers. The ServOrbit installation creates the admin account with a generated password, publishes the console over HTTPS and keeps the AMQP port on the VPS loopback, out of reach from the Internet.
What gets installed
A Laravel or Django shop sends invoice generation, emails and exports to a queue: the page answers at once, and workers handle the rest in the background.
A confirmed order publishes a single event; stock, billing and notifications each receive it in their own queue, without the services knowing each other.
During a campaign or a sale, messages pile up in the queue instead of overloading the database: workers catch up as soon as the spike is over.
Guide
Order an Ubuntu 24.04 VPS: 2 GB of RAM suits most projects. RabbitMQ is installed with a domain, so that its management console is served over HTTPS: a subdomain of one of your domains, or the VPS's free subdomain (rabbitmq.{dns_slug}.servorbit-dns.com), HTTPS included. There is no need to buy a domain name.
In your client area, select RabbitMQ, choose the address and click Install. The script deploys the official image with the management console, creates the admin account with a generated password and configures the nginx reverse proxy over HTTPS. RabbitMQ starts in about fifteen seconds.
Open https://your-domain and sign in with the admin user and the password shown in your client area. The factory guest account does not exist. The password is only set on first start: if you change it in the console, your new password is kept across restarts.
In the Admin tab, create a virtual host per application (for example shop) and a user with permissions on that vhost only. Never give the admin account to an application: if it leaks, only its vhost is exposed.
The AMQP port 5672 stays on the VPS loopback. An application installed directly on the VPS connects to amqp://127.0.0.1:5672; a containerised application joins the RabbitMQ Docker network:
`bash
docker network connect rabbitmq <application-container>`
Address to use: amqp://<user>:<password>@rabbitmq:5672/<vhost>.
Proof
The memory required and the VPS that covers it, on every card.
Check it: the “Recommended VPS” line of each card
You administer the system over SSH; your data stays on your VPS.
Check it: the “What is installed” section of each page
The applications are open source: your only cost is the VPS that runs them.
Check it: in the cart, no line for the application
In-memory store for caching, sessions, queues and real-time data structures.
DevelopmentOpen-source real-time messaging server: WebSocket connections and a publish API for your applications, on your VPS.
DevelopmentPHP-FPM, Nginx, PostgreSQL, Redis and Supervisor preconfigured. Deploy Laravel to production with no initial configuration.

Dedicated Cloud VPS — IPv4 included, server in Europe, support included. Your data never leaves your server.
RabbitMQ also runs on a dedicated server, when models or data outgrow a VPS. See dedicated servers