Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
An instant-messaging server written in Go, with web, Android and iOS clients and a gRPC API. It handles one-to-one chats, group topics, channels, file sharing and WebRTC calls, and stores its data in PostgreSQL in this setup (MySQL and MongoDB are also supported). The project describes itself as a replacement for XMPP rather than a Slack clone, and calls the software beta quality.
Runs on a VPS from $6/mo (Kamatera 2GB, 2 GB RAM) · prices checked Nov 2026
Fits home hardware (55 MB measured idle, RAM only): Raspberry Pi 4 (4 GB) (arm64 untested), Raspberry Pi 5 (8 GB) (arm64 untested), Repurposed laptop (8 GB), Intel N100 mini PC (16 GB), AMD Ryzen mini PC (32 GB).
Pick Tinode when you want an instant-messaging backend with ready clients for web, Android and iOS, more like a self-hosted WhatsApp or Telegram than a Slack. The server is Go under GPL-3.0 (the clients are Apache-2.0) and uses PostgreSQL in the image we pin, `tinode/tinode-postgres:0.25.3`, released 2026-07-04. The snippet follows `docker/README.md` and adds a Compose file, a PostgreSQL 17 container and generated `AUTH_TOKEN_KEY` and `UID_ENCRYPTION_KEY` values. Upstream gives no RAM figure, so our 512 MB floor is an estimate for a Go binary plus PostgreSQL. The README states that building "yet another Slack replacement" is an explicit non-goal, and it calls the software beta quality, so there is no Slack-style workspace model. Zulip, Mattermost and Rocket.Chat in this catalog are workspace chat with threads and integrations, and Synapse and Tuwunel are federated Matrix servers. Tinode is a standalone messenger with its own protocol and a gRPC API for bots and custom clients, which suits an app or a community more than a company.
Paid link — we earn a commission if you shop through it.
Run these commands on your server:
# Tinode — instant messaging — adapted from docker/README.md (tinode-postgres image + postgres container on one network), pinned to 0.25.3
mkdir tinode && cd tinode
cat > .env <<EOF
POSTGRES_PASSWORD=$(openssl rand -hex 24)
AUTH_TOKEN_KEY=$(openssl rand -base64 32)
UID_ENCRYPTION_KEY=$(openssl rand -base64 16)
EOF
cat > docker-compose.yml <<'EOF'
services:
postgres:
image: postgres:17.11-alpine
restart: unless-stopped
environment:
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
volumes:
- pgdata:/var/lib/postgresql/data
tinode:
image: tinode/tinode-postgres:0.25.3
restart: unless-stopped
depends_on:
- postgres
ports:
- "6060:6060"
environment:
WAIT_FOR: postgres:5432
POSTGRES_DSN: postgresql://postgres:${POSTGRES_PASSWORD}@postgres:5432/tinode?sslmode=disable&connect_timeout=10
AUTH_TOKEN_KEY: ${AUTH_TOKEN_KEY}
UID_ENCRYPTION_KEY: ${UID_ENCRYPTION_KEY}
SAMPLE_DATA: ''
volumes:
pgdata:
EOF
docker compose up -d
timeout 300 bash -c 'until curl -fsS -o /dev/null http://localhost:6060/; do sleep 3; done'
# → http://SERVER_IP:6060 (register the first account in the web app; SAMPLE_DATA is emptied so the demo users (alice, bob, carol, dave, eve, frank, tino, xena) with known passwords are not created)Tinode's README and Docker guide set expectations worth reading first:
Tinode used 55 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 512 MB.
The Tinode install snippet is marked verified on Ubuntu 26.04 (Nov 2026).