
Floors and rooms
Your channels become a building with floors, a corridor and rooms with doors. The elevator takes you up and down and shows where everyone is.
Ruumble turns a voice server into floors and rooms. You see who is around and who is talking, walk into a room with a click and find a board in every room. Low latency, great audio and a server of your own, with the care for detail a team deserves.

Your channels become a building with floors, a corridor and rooms with doors. The elevator takes you up and down and shows where everyone is.

Pin notes, code, images and files where the conversation happens. With reactions, task lists and search.

Add, rename and order rooms, move a board when a room changes and tidy up old posts. Right where you are.

Settings, the audio wizard, your certificate and servers: everything you know from Mumble is one click away, in the same window.

See who is talking, muted or away, and what they are up to. Write to someone privately without leaving your room.

Hand a file to a person or a whole room. It travels straight from you to them and is never kept on the server.
Voice chat is great for teams that work apart: always on, low latency, no meeting links. What it lacks is the office around it. Who is in, who is busy, where can I drop in for a minute?
Ruumble draws that office. Channels become a building with floors, a corridor and rooms with doors. People sit in their rooms, light up while they talk and carry a short status. A click on a room takes you there, and the board in each room keeps what was shown and shared there.
Ruumble started as a plugin for Mumble and grew into a client, a service and soon a voice server of its own. It keeps what makes Mumble good and puts usability first: one window, no setup puzzles, a building you understand at a glance. People with a plain Mumble client can still join the same server.
It is open source under the BSD 3-Clause license and made by a small team that works in it every day.
| Your team | Talks a lot, or wants to, and misses who is around |
|---|---|
| Server | A small Linux server with Docker, run by you |
| Desktop | Ruumble on Linux (AppImage, .deb, .rpm, Arch, Nix), or a Mumble client with the Ruumble plugin on Linux and Windows |
| Languages | English and German, light and dark |
We are rebuilding this. Today Ruumble runs on top of a Mumble server and adds a service next to it. Step by step, Ruumble Foundation, a voice server of our own, takes over from Mumble's core. What you read below is the current state, not the destination.
Today that is a Mumble server, read by the service with the read secret only. It is the part being replaced.
Floors, corridor and rooms come from the channel tree alone. No special names, no keywords: the order is the order of the channels.
Moves, mute and deafen happen in your own client. The plugin only opens an outgoing connection.
The service keeps boards and statuses. Who is talking, private messages and files pass through and are never written down.
Ruumble Foundation: a clustered voice server in Go, running on three nodes, so that a node can fail or be updated without the building going quiet. ruumble-foundation
Two sides: whoever runs the server sets it up once, everyone else installs Ruumble on their desktop. A fresh setup takes about ten minutes.
One window with the building and voice. Linux, x86_64.
| Debian 12 | sudo apt install ./ruumble-client_<version>+debian12_amd64.deb |
| Ubuntu 24.04, Mint 22 | sudo apt install ./ruumble-client_<version>+ubuntu2404_amd64.deb |
| Fedora | sudo dnf install ./ruumble-client-<version>-1.fc<NN>.x86_64.rpm |
| Arch Linux | sudo pacman -U ruumble-client-<version>-1-x86_64.pkg.tar.zst |
| Any other | The AppImage: chmod +x, then start it. It updates itself. |
| NixOS | nix run github:ruumble-project/ruumble-client |
On first start Ruumble offers to take over an installed Mumble with its certificate and servers. Connect to your server, and the building appears.
Mumble 1.4 or newer on Linux (x86_64) or Windows (x64), plus a current Firefox, Chrome or Edge.
…/download) and install it in Mumble under
Configure → Settings → Plugins.Docker with Compose, in an empty folder. This starts the voice server and the Ruumble service together:
curl -fsSLO https://raw.githubusercontent.com/ruumble-project/ruumble-server/main/deploy/compose/mumble-with-ruumble.docker-compose.yml curl -fsSLO https://raw.githubusercontent.com/ruumble-project/ruumble-server/main/deploy/compose/setup.sh sh setup.sh && docker compose up -d
setup.sh creates the two Ice secrets and prints the line for the root channel.
docker cp mumble-server:/data/. <backup>/mkdir -p secrets && chmod 700 secrets openssl rand -hex 24 > secrets/ice_read openssl rand -hex 24 > secrets/ice_write chmod 644 secrets/*and add
MUMBLE_CONFIG_ICE, the two secrets and the network mumble-network to Mumble's Compose file.
Do not publish port 6502.ghcr.io/ruumble-project/ruumble, the read secret and the same network.
services:
ruumble:
image: ghcr.io/ruumble-project/ruumble:<version>
container_name: ruumble
restart: unless-stopped
environment:
ICE_HOST: mumble-server
ICE_SECRET_READ_FILE: /run/secrets/ice_read
ADDRESS_CHECK: enforce
secrets: [ice_read]
volumes: [ruumble-data:/data]
networks: [mumble-network]
ports: ["64080:64080"]
secrets:
ice_read: { file: ../mumble/secrets/ice_read }
volumes:
ruumble-data: { name: ruumble-data }
networks:
mumble-network: { external: true }Add a line of its own to the description of the root channel, and keep the whole description under 128 characters:
ruumble: http://192.168.1.10:64080
Check with curl http://192.168.1.10:64080/healthz and send your team the address.