selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

Neko logo

Self-host Neko

v3.2.0

Self-hosted virtual browser with WebRTC streaming

ReleaseOpen SourceApache-2.0
Updated4 weeks ago
LanguageGo
Setup difficultyAdvanced
Stars
22 675
CPU
4 cores
RAM
3gb
Ports
8080 (HTTP/WebSocket server), 52000 (WebRTC UDP ephemeral port range (52000-52100))
Docker
ghcr.io/m1k1o/neko/firefox
Install with Docker Compose
n.eko virtual browser streaming demo showing collaborative browsing session

What is Neko?

n.eko runs a complete Linux desktop inside a Docker container and streams it to multiple users over WebRTC with under 300ms latency and synchronized audio. Multiple participants can share control of the session. It supports many browsers (Firefox, Chrome, Chromium, Brave, Edge, Vivaldi, Opera, Tor Browser, Waterfox), full desktop environments (XFCE, KDE), and apps like VLC and Remmina. Use cases include watch parties, interactive presentations, collaborative debugging, remote teaching, jump host for internal resources, persistent browser sessions, throwaway browsers for privacy, RTMP broadcasting to Twitch/YouTube, and automation with Playwright or Puppeteer. GPU acceleration works with NVIDIA CUDA, Intel VAAPI, and Raspberry Pi V4L2. Authentication options include built-in passwords, OAuth 2.0/OIDC, file-based users, and an object provider. Configuration uses environment variables, YAML/JSON/TOML files, or CLI arguments. Requires Docker and Docker Compose; recommended specs are 4+ CPU cores and 3-4GB RAM for 720p@30fps.

Neko alternatives

All self-hosted alternatives to Giggl.app → All self-hosted alternatives to Hyperbeam → All self-hosted alternatives to hyperbeam API →

Should you self-host Neko?

Neko scores 78/100 on selfhost.directory (how scoring works) and ranks #3 of 22 in Remote Desktop. It has 22 675 GitHub stars, +207 in the last 30 days.

It shipped 4 stable releases in the past year. The latest, v3.2.0, came out on 15 October 2026. New versions land roughly every 2 months.

Setup is advanced: plan for several services and some ongoing maintenance. An official Docker image is available. It is Apache-2.0-licensed and written mostly in Go.

Its closest alternative on selfhost.directory is rustdesk (92/100, 129 283 stars). It scores higher overall, so compare the two before you pick. See Neko vs rustdesk side by side.

Features

  • Additional applications
  • Automated browser (Playwright/Puppeteer)
  • Desktop environments
  • GPU hardware accelerationGPU support may not work as expected; focus is on CPU images.
  • Interactive presentations
  • Jump host for internal resources
  • Multi-participant control
  • Multiple browser choices
  • Multi-user collaborative browsing
  • OAuth 2.0 / OpenID Connect authentication
  • Persistent Browser Sessions
  • RTMP live broadcasting
  • Throwaway browser
  • Watch parties
  • WebRTC ultra-low latency streaming

Neko README

n.eko

Welcome to Neko, a self-hosted virtual browser that runs in Docker and uses WebRTC technology. Neko is a powerful tool that allows you to run a fully-functional browser in a virtual environment, giving you the ability to access the internet securely and privately from anywhere. With Neko, you can browse the web, run applications, and perform other tasks just as you would on a regular browser, all within a secure and isolated environment. Whether you are a developer looking to test web applications, a privacy-conscious user seeking a secure browsing experience, or simply someone who wants to take advantage of the convenience and flexibility of a virtual browser, Neko is the perfect solution.

How to install Neko

Install Neko with Docker Compose

Docker and Docker Compose Plugin installed
Environment variables
NEKO_DESKTOP_SCREEN, NEKO_MEMBER_MULTIUSER_USER_PASSWORD, NEKO_MEMBER_MULTIUSER_ADMIN_PASSWORD, NEKO_WEBRTC_EPR, NEKO_WEBRTC_ICELITE, NEKO_WEBRTC_NAT1TO1

Default compose file runs Firefox image with multi-user auth. Edit environment variables for passwords, screen resolution, WebRTC ports.

How to configure Neko

  • NEKO_WEBRTC_EPRLimits the pool of ephemeral ports that ICE UDP connections can allocate from.
  • NEKO_WEBRTC_NAT1TO1Sets a list of external IP addresses of 1:1 (D)NAT and a candidate type.
  • NEKO_MEMBER_MULTIUSER_USER_PASSWORDnekoPassword for regular users in plain text.
  • NEKO_MEMBER_MULTIUSER_ADMIN_PASSWORDadminPassword for admin users in plain text.
  • NEKO_DESKTOP_SCREEN1280x720@30Default screen size and framerate (e.g., 1280x720@30).

Neko releases & version history

@ Every self-hosted release, weekly

One Monday email with the week's stable releases across the directory.

FAQ

Why am I unable to install extensions in the Neko browser?

The browser uses policies to restrict extension installation. Add extensions to the policy file or disable the policy.

Why does the clipboard button not show up?

When using HTTPS with a compatible Chromium-based browser supporting the Clipboard API, the native clipboard functionality is used instead of the button.

Can I use neko without Docker?

Yes, but not recommended. Neko is based on Debian with Xorg and PulseAudio. You can copy the binary from the Docker image and install GStreamer dependencies on a host with GUI/desktop manager.

How can I embed Neko into a web page without login prompt for viewers?

Use URL with credentials: http://<your-neko-server-ip>:8080/?usr=neko&pwd=neko and ensure iframe has allowfullscreen attribute.

How to enable debug mode?

Set NEKO_DEBUG=1 environment variable or log.level=debug in config. For GStreamer issues, set GST_DEBUG=3. For Pion WebRTC debugging, set PION_LOG_DEBUG=all.

More in Remote Desktop

Rate this project

Click to rate — no account needed.

0 comments

Posting as guest
Loading comments…