Gimodi: The Self-Hosted
Discord Alternative You Control

Why Look for a Discord Alternative?

Discord has become the default communication platform for gaming communities, developer groups, open-source projects, and online friend circles. It works well, it is free at the surface level, and almost everyone already has an account. But that convenience comes with real trade-offs.

Discord is a closed, centralized platform. Your server can be deleted with little notice if it violates policies - or even if it is wrongly flagged. Every message, every voice session, every file you share passes through Discord's infrastructure. The company collects detailed telemetry, sells access to data for advertising purposes, and has made clear that the "free" model is subsidized by your community's activity and data.

For communities that handle sensitive conversations, operate in regulated industries, or simply value control over their own infrastructure, the question of a self-hosted alternative is worth taking seriously.

What is Gimodi?

Gimodi is a self-hosted voice and text communication server. You run it on your own hardware - a VPS, a dedicated server, or even a Raspberry Pi - and you connect to it using the Gimodi client. No third party has access to your data, no telemetry leaves your server, and no external company can shut down your community.

The server is distributed as a Docker image, making it straightforward to deploy in minutes. It uses mediasoup as its SFU (Selective Forwarding Unit) for real-time audio and video, the Opus codec for high-quality voice, and OpenPGP for end-to-end encrypted direct messages.

Key Features

Voice, Video, and Screen Sharing

Gimodi delivers crystal-clear voice chat through mediasoup's SFU architecture with the Opus codec. Low latency, minimal bandwidth usage, and clean audio quality are the result. Beyond voice, it supports full webcam sharing in voice channels - with a pop-out video view for multitasking - and screen sharing with system audio, which makes it viable for watch parties, presentations, and collaborative work sessions.

Text Channels with Markdown and File Sharing

Text channels support markdown rendering and file uploads. Message history is persisted in a SQLite database by default, so users can scroll back through previous conversations. If you prefer ephemeral channels where messages are not stored, you can disable persistence with a single environment variable.

End-to-End Encrypted Direct Messages

Private messages between users are encrypted with OpenPGP. This means not even the server operator can read direct messages. True end-to-end encryption is built into the platform, not bolted on as an optional paid feature.

No Account Required

Connecting to a Gimodi server requires nothing more than a nickname. There is no email address, no phone number, and no sign-up form. If you want a persistent identity across sessions, you can generate an OpenPGP key pair and export it - no external account needed.

Privacy First Architecture

Gimodi does not phone home. There is no analytics, no telemetry, and no tracking built into the server. What happens on your server stays on your server.

Role-Based Access Control

Full role-based permission management lets you create custom roles, assign granular permissions per channel, and restrict access exactly as you need. Community moderation is handled entirely on your own infrastructure.

Lightweight Server Footprint

The server runs efficiently even on modest hardware. A single CPU core and 1 GB of RAM is sufficient for a typical community. Voice capacity scales by adding mediasoup worker processes - each worker runs on one CPU core and handles one UDP port for WebRTC traffic.

Gimodi vs Discord: A Practical Comparison

Getting Started: Deploy in Minutes with Docker

Gimodi is distributed as a Docker image. You need a machine with Docker installed and a public IP address (or domain name) so clients can reach it.

Minimum Requirements

• Architecture: x86_64 (amd64) - ARM is not currently supported
• CPU: 1 core (each mediasoup worker uses one core)
• RAM: 1 GB
• Disk: 1 GB base install, grows with message history and file uploads
• Network: Public IP required for WebRTC media

Quick Start with Docker Run

Create a directory for persistent data and start the container. Replace YOUR_PUBLIC_IP with your server's public IP address or domain:

mkdir -p gimodi/data

docker run -d --name gimodi \
  -p 6833:6833/tcp \
  -p 40000-40003:40000-40003/udp \
  -e GIMODI_MEDIA_ANNOUNCED_IP=YOUR_PUBLIC_IP \
  -e GIMODI_MEDIA_WORKERS=1 \
  -v $(pwd)/gimodi/data:/app/data \
  gimodi/gimodi

Port 6833/tcp serves HTTPS and WebSocket connections. Ports 40000-40003/udp carry WebRTC media traffic for voice, video, and screen sharing - one UDP port per mediasoup worker.

Or Use Docker Compose

Create a docker-compose.yml:

services:
  gimodi:
    image: gimodi/gimodi
    restart: unless-stopped
    ports:
      - 6833:6833/tcp
      - 40000-40003:40000-40003/udp
    environment:
      - GIMODI_MEDIA_ANNOUNCED_IP=YOUR_PUBLIC_IP
      - GIMODI_MEDIA_WORKERS=1
    volumes:
      - ./data:/app/data

Then bring it up:

docker compose up -d

Claim Admin Access

On first startup, Gimodi generates a one-time admin token and prints it to the container logs:

docker logs gimodi

Copy the token, connect to your server from the Gimodi client using YOUR_PUBLIC_IP:6833, pick a nickname, then go to the menu and select Redeem Token to gain admin privileges.

SSL Certificates

Gimodi automatically generates a self-signed SSL certificate on first start and the client accepts it without issues. For production use with a proper domain, place your cert.pem and key.pem (e.g. from Let's Encrypt) in the data directory and configure the paths:

-e GIMODI_SSL_CERT_PATH=/app/data/cert.pem \
-e GIMODI_SSL_KEY_PATH=/app/data/key.pem

Configuration Reference

Gimodi is configured via environment variables, which always take highest priority over settings stored in the database via the admin panel. The most important variables:

• GIMODI_NAME - Display name of your server (default: Gimodi Server)
• GIMODI_PORT - TCP port for WebSocket/HTTPS (default: 6833)
• GIMODI_PASSWORD - Server password; leave unset for an open server
• GIMODI_MAX_CLIENTS - Max concurrent connections (default: 100)
• GIMODI_MEDIA_ANNOUNCED_IP - Public IP for WebRTC (required behind NAT)
• GIMODI_MEDIA_WORKERS - mediasoup worker count; 0 = auto-detect CPU cores
• GIMODI_CHAT_PERSIST_MESSAGES - Store chat history in SQLite (default: true)
• GIMODI_FILES_MAX_FILE_SIZE - Max upload size in bytes (default: 10 GB)

Scaling for Larger Communities

Voice traffic is the most resource-intensive workload. Each mediasoup worker runs on a single CPU core and handles WebRTC routing for voice, webcam, and screen sharing. For a small group of friends, one worker on a 1-core VPS is sufficient. For a larger active community, increase GIMODI_MEDIA_WORKERS and open the corresponding UDP ports:

# 4 workers - open ports 40000-40003
-p 40000-40003:40000-40003/udp
-e GIMODI_MEDIA_WORKERS=4

Disk usage depends on whether message persistence is enabled and how actively files are being shared. The GIMODI_FILES_MAX_FILE_SIZE variable lets you cap individual upload sizes to keep storage consumption predictable.

Who is Gimodi For?

Privacy-focused communities that do not want their conversations routed through a US-based commercial platform will find Gimodi a compelling option. End-to-end encrypted DMs and zero telemetry are rare in this space.

Developer and technical teams that already run their own infrastructure will appreciate the straightforward Docker deployment and the lack of any external dependency for core functionality.

Gaming groups and friend circles that want the Discord experience - voice channels, text channels, screen sharing - without the account requirements, data collection, or risk of arbitrary platform bans.

Organizations in regulated industries where data residency matters. When your server runs in your own data center, you know exactly where your communication data sits.

Conclusion

Gimodi does not have every feature Discord has accumulated over a decade of development - there is no mobile app yet, no ARM support, and no massive integrations ecosystem. But what it offers is something Discord fundamentally cannot: genuine ownership of your communication infrastructure.

You run the server. You control the data. You set the rules. Nobody can delete your community from the outside. Direct messages are end-to-end encrypted even from you as the server operator. And the whole thing runs for free on hardware as modest as a Raspberry Pi - or a small VPS costing a few euros a month.

For communities where privacy, control, and data sovereignty matter more than convenience, Gimodi is worth a serious look.