Ruumble Under construction
A fork of Mumble, built for coolness

Voice chat as an office building

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.

The building
The elevator lists the floors with their head count

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.

The board of a room with an image, a file and code

A board in every room

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

The rooms of a floor in the floor care

Care for the building

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

Ruumble
Ruumble: the floor Development with its rooms, people in Let's talk and the board of the room on the right
And more
Settings, audio and the full menu at the foot of the elevator

All your favourite Mumble features New

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

Clara's status and a private message to her

Who is around, and a quiet word

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

Sending a file to Clara

File exchange

Hand a file to a person or a whole room. It travels straight from you to them and is never kept on the server.

About

The feeling of a shared office, for a team that is spread out

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.

Is Ruumble for you?

Your teamTalks a lot, or wants to, and misses who is around
ServerA small Linux server with Docker, run by you
DesktopRuumble on Linux (AppImage, .deb, .rpm, Arch, Nix), or a Mumble client with the Ruumble plugin on Linux and Windows
LanguagesEnglish and German, light and dark
Features

Everything Ruumble does today

The building

  • Channels become floors, a corridor and rooms
  • Elevator with the head count of every floor
  • Plants, binders and a pin board show what each room holds
  • Building overview with a directory of people, rooms and statuses
  • Room descriptions in Markdown, behind the binders on the wall

Presence

  • Who is talking, muted or deafened, quiet or away
  • A short status text that expires when you want
  • Recording notice and who listens in
  • Avatars, and guests without Ruumble shown as such

Moving and listening

  • One click to walk into a room or over to a person
  • Mute and deafen from anywhere
  • Listen in on another room at your own volume
  • A nudge for someone who has deafened themselves

Talk without talking

  • A quiet word: private messages, never stored on the server
  • Files to a person or a room, passed through, never stored
  • Notices for people who have Ruumble closed

The board

  • Markdown, source code with highlighting, images and files
  • Reactions, shared task lists, posts kept on top
  • Search and filters by kind
  • Export a board as Markdown or ZIP

Care and maintenance

  • Floor care: rooms, their boards and data of deleted rooms
  • Set up rooms and floors with the server's permissions
  • Building maintenance: limits and settings without a restart
  • Key cabinet: see and revoke paired browsers

Privacy and security

  • The service reads the voice server, it cannot change it
  • Who is talking goes only to your own screen and is never stored
  • Browsers are paired once with a link or a 6-digit code
  • Foreign origins are turned away

Ruumble on your desktop

  • One window: the building and all of Mumble's voice features
  • Takes over an installed Mumble with its certificate and servers
  • AppImage, .deb, .rpm, Arch package and Nix flake
  • Tells you when a newer version is out

The full feature list · What's new in each version

Architecture · under reconstruction

How Ruumble works today

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.

Mumble server voice, today BEING REPLACED Ruumble service Docker · web UI · boards pairing · file relay Ruumble desktop app, one window building and voice Browser + plugin in a Mumble client (Linux, Windows) HTTP WebSocket Ice read-only voice, low latency, straight to the voice server

A voice server at the core, for now

Today that is a Mumble server, read by the service with the read secret only. It is the part being replaced.

The building is drawn, not configured

Floors, corridor and rooms come from the channel tree alone. No special names, no keywords: the order is the order of the channels.

Your client does the moving

Moves, mute and deafen happen in your own client. The plugin only opens an outgoing connection.

Little is stored

The service keeps boards and statuses. Who is talking, private messages and files pass through and are never written down.

Setup

Getting Ruumble running

Two sides: whoever runs the server sets it up once, everyone else installs Ruumble on their desktop. A fresh setup takes about ten minutes.

On your desktop: Ruumble

One window with the building and voice. Linux, x86_64.

Debian 12sudo apt install ./ruumble-client_<version>+debian12_amd64.deb
Ubuntu 24.04, Mint 22sudo apt install ./ruumble-client_<version>+ubuntu2404_amd64.deb
Fedorasudo dnf install ./ruumble-client-<version>-1.fc<NN>.x86_64.rpm
Arch Linuxsudo pacman -U ruumble-client-<version>-1-x86_64.pkg.tar.zst
Any otherThe AppImage: chmod +x, then start it. It updates itself.
NixOSnix run github:ruumble-project/ruumble-client

Latest release

Soon: a package repository for apt, so that Ruumble updates with the rest of your system.

On first start Ruumble offers to take over an installed Mumble with its certificate and servers. Connect to your server, and the building appears.

Already on Mumble? The plugin

Mumble 1.4 or newer on Linux (x86_64) or Windows (x64), plus a current Firefox, Chrome or Edge.

  1. Download the plugin from your Ruumble address (…/download) and install it in Mumble under Configure → Settings → Plugins.
  2. Connect to the server: the plugin opens your browser with a pairing link.
  3. From then on, open Ruumble at its address. You can install it as an app.

User guide

On your server: a new setup

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.

On your server: next to an existing Mumble

  1. Back up Mumble's data: docker cp mumble-server:/data/. <backup>/
  2. Enable Ice with a read and a write secret:
    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.
  3. Start Ruumble beside it with the image ghcr.io/ruumble-project/ruumble, the read secret and the same network.
    docker-compose.yml
    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 }

Then: tell the clients where Ruumble is

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.

Plain HTTP belongs in a LAN or VPN. On the internet, put Ruumble behind an HTTPS reverse proxy.

More for operators