How security is built into RabbitGUI

Why is security important?

When we built RabbitGUI, a desktop IDE for RabbitMQ, security was part of the design from day one. Because the app connects directly to RabbitMQ instances, it often requires confidential credentials, sometimes the same ones used in production environments. Once connected, it can also read messages that may contain sensitive information. With that in mind, we treated security as a top priority from the very beginning.

Our servers never even see you data, ever

One important principle behind RabbitGUI is that our servers never see your data, RabbitGUI is not a SaaS. The application connects straight to your RabbitMQ instance without anything in between. We don’t process or forward your traffic, and we don’t keep logs of your activity, simply because we never touch it in the first place.

If you’re curious to verify this, you can place a proxy in front of your RabbitMQ instance and configure RabbitGUI to use it. You’ll notice that every connection comes directly from your own machine, not from an external server.

All passwords are stored locally and encrypted

Passwords are handled with the same level of care. They are stored only on your machine and are never sent to us. On disk, they are encrypted and can only be decrypted by RabbitGUI itself. This means that if you change machines, the saved passwords will not follow you, and you’ll need to keep them safe in a password manager or another secure place.

You can work offline

Finally, RabbitGUI is designed to work offline. You can keep working even on a plane or in areas where internet access is unreliable. The only time the app needs to connect online is to activate your license the first time you use it, and then once every month. Between those checks, you can stay fully offline for up to a month without any interruption.