AltFreeStack
ESEN
Video Conferencingdocker-ready1-click-deploypermissive-license100% FOSS🟢 Lightweight · ~256MB

Neko: Open Source alternative to Zoom in 2026

Neko creates a shared streaming browser room where several people watch and control the same virtual browser at once, ideal for watch parties or collaborative browsing.

Alternative to Zoom
License Apache-2.022.5k starsWebsite GitHub Repository

Audit Snapshot

View notes →

  • License — Matches GitHub

  • GitHub — Active

  • Latest release — v3.1.6 · 13 days ago

  • Docker Compose — Not verified

  • Production — Not production-tested by AltFreeStack

Neko vs. Zoom

Pros

  • A unique use case Zoom doesn't cover well (a real shared browser)

Things to consider

  • Not a general substitute for work video calls

Quick Docker installation guide

Copy this docker-compose.yml, adjust the example passwords and run docker compose up -d on your server. See the full step-by-step guide →

💡 Official SaaS or self-hosted with AltFreeStack?

  • On the official cloud: a recurring monthly fee and usage limits on Zoom.
  • On your own VPS: 100% free software on your own server, with no artificial row, project or user limits.
docker-compose.yml
version: "3.9"
services:
  neko:
    image: m1k1o/neko:firefox
    restart: unless-stopped
    ports:
      - "8080:8080"
      - "52000-52100:52000-52100/udp"
    environment:
      - NEKO_SCREEN=1920x1080@30
      - NEKO_PASSWORD=change-me
      - NEKO_PASSWORD_ADMIN=change-me-admin
    shm_size: "2gb"

🚀 Deploy in 1 command

Recommended for beginners

Copy this single command and paste it into your freshly created VPS's console (Vultr, DigitalOcean...). It downloads the script, prints it to your screen so you can see exactly what it's about to do (never a blind direct pipe), and only then installs Docker if needed, writes the files with secrets already generated, and starts everything — no nano, no pasting code blocks.

curl -sSL ".../api/deploy?stack=neko" -o deploy.sh && cat deploy.sh && bash deploy.sh
See what this script does →

This docker-compose corresponds to an actively maintained project — last commit 5 days ago.

This docker-compose not working for you? Report it on GitHub →

Technical profile

License
Apache-2.0
Category
Video Conferencing
Replaces
Zoom
Tech stack
GoWebRTCGStreamer

Under the hood

Database

None / File-based

Language

Go

Platforms

Web

Key features

  • Real-time shared browser
  • Built-in voice and text chat
  • Ideal for watch parties or remote tech support

Frequently asked questions

What is Neko (n.eko)?

An open source tool (Apache-2.0) that creates a streamed shared browser room: multiple people watch and control the same virtual browser at once, ideal for watch parties or collaborative browsing.

Is Neko a replacement for Zoom?

No. It covers a unique, specific use case Zoom doesn't solve well — a genuinely shared browser, not just screen sharing — but it isn't a general replacement for work video calls, as we note on its page.

How do you deploy Neko with Docker?

With the `m1k1o/neko` image in whichever browser variant you prefer (e.g. `m1k1o/neko:firefox`) — a single Docker service, no external database.

Preview

Neko interface preview

Public image provided by Neko on its own website.

💾 Backups in 3 steps (Day 2)

As long as the ./data folder (the "volume" mapped into the container) exists on your server, your data survives any restart or container update — that's the only thing you need to back up.

1. Create a compressed backup on the server

tar -czvf backup-$(date +%F).tar.gz ./data

2. Download it to your computer

From your computer's terminal (not your server's):

scp root@YOUR_IP:~/app/backup-*.tar.gz ./

3. Restore in case of emergency

tar -xzvf backup-file.tar.gz
🌐 Connect your domain with free SSL

Step 1 — Set up the DNS

In your domain registrar's dashboard (Cloudflare, Namecheap, GoDaddy...), create a record:

Type
A
Name/Host
@ (root domain) or a subdomain, e.g. app
Content/Value
Your server's public IP

Wait 5 to 15 minutes for the record to propagate across the internet.

Step 2 — Automatic reverse proxy with Caddy

One single file, no Nginx config or manual certificates — Caddy issues and renews Let's Encrypt HTTPS on its own.

Create a file called Caddyfile:

yourdomain.com {
    reverse_proxy localhost:8080
}

Start Caddy with this command (pulls the image and runs it in the background):

docker run -d -p 80:80 -p 443:443 --name caddy --restart always -v $PWD/Caddyfile:/etc/caddy/Caddyfile -v caddy_data:/data caddy