Repolode
m1k1o

m1k1o/neko

A self-hosted virtual browser that runs in Docker and streams to multiple users over WebRTC, with shared control.

Open-source alternative to:TelepartyScenerSharedbrowser

Stars
22,551
Forks
1,642
Open issues
147
Last commit
4 days ago

What is it?

Neko runs a full desktop browser inside a Docker container and streams its screen, audio and video to users' web browsers over WebRTC. Several people can connect to the same session at once, and the host can grant control to participants, so the browser works as a shared space rather than a single-user window.

Because the browser lives on the server, the session is isolated from the viewer's machine: cookies and local data stay in the container, and nothing persists on the client after disconnecting. The project supports many browsers such as Firefox, Chromium, Chrome, Brave and Tor Browser, and it can also run other Linux programs or full desktops such as XFCE and KDE. Streaming can be broadcast over RTMP to platforms like Twitch or YouTube.

Neko is aimed at watch parties, collaborative browsing, interactive presentations, remote support and teaching, and embedding a virtual browser into a web application. It is configured mainly through Docker images and has room management handled by a separate project, neko-rooms.

Key features

  • 01Streams the browser to multiple viewers over WebRTC with low latency video and audio.
  • 02Lets multiple participants share a session, with control handed to selected users.
  • 03Runs in Docker and supports browsers including Firefox, Chromium, Chrome, Brave and Tor Browser.
  • 04Can run other Linux desktop apps and environments such as VLC, XFCE and KDE.
  • 05Broadcasts sessions over RTMP and keeps browser state inside the container.

Use cases

  • Hosting a watch party where friends watch videos together in one browser.
  • Running an interactive presentation or collaborative browsing session for a team.
  • Providing a disposable, isolated browser for private or sensitive browsing.
  • Embedding a virtual browser into a web application for remote access.

Quick start

  1. 1

    Read the Getting Started guide on the documentation site

  2. 2

    Choose a Docker image for the browser or app you want, from the installation docs

  3. 3

    Follow the installation docs to run the chosen image with Docker

Things to know

  • Requires Docker and a self-hosted setup.
  • The README gives no inline install command; setup details are on the external documentation site.
  • The streamed desktop runs on Linux.

In collections

Topics

FAQ

What is neko?
A self-hosted virtual browser that runs in Docker and streams to multiple users over WebRTC, with shared control. Neko runs a full desktop browser inside a Docker container and streams its screen, audio and video to users' web browsers over WebRTC. Several people can connect to the same session at once, and the host can grant control to participants, so the browser works as a shared space rather than a single-user window.
Is neko free to use? What license does it have?
neko is open source under the Apache-2.0 license. Check the license terms before using it in commercial products.
Is neko still maintained?
Actively maintained. The last commit to neko was on Oct 20, 2026.
What can I use neko for?
Hosting a watch party where friends watch videos together in one browser. Running an interactive presentation or collaborative browsing session for a team. Providing a disposable, isolated browser for private or sensitive browsing. Embedding a virtual browser into a web application for remote access.
How do I install neko?
Read the Getting Started guide on the documentation site Choose a Docker image for the browser or app you want, from the installation docs Follow the installation docs to run the chosen image with Docker
Where can I get neko?
The source code and installation instructions are on GitHub: https://github.com/m1k1o/neko

Summary generated by AI from the project's README. GitHub stats refresh daily.

Related projects