Neko

A self-hosted virtual browser, honestly reviewed. No marketing fluff — just what you actually get when you run it.

TL;DR

• What it is: Self-hosted virtual browser running in a Docker container, streamed to multiple users simultaneously via WebRTC [1][2].
• Who it’s for: Privacy-conscious users, NAS owners, teams that need a shared browser session, and anyone who wants a persistent or throwaway browser they fully control [5][3].
• Cost: $0 for the software (Apache-2.0 license). You need a VPS or home server to run it — plan for $10–20/mo depending on hardware requirements [2].
• Key strength: The concept actually works: multiple people can share a single browser session with real-time control handoff, under 300ms latency, with chat and reactions — all in a browser tab with no plugin required [4][1].
• Key weakness: It is not a media server. It’s a remote desktop streamed over WebRTC, which means hardware requirements are heavier than they look, and NAT/TURN configuration will stop non-technical users cold [2].

---

What Is Neko

Neko is a self-hosted virtual desktop that runs inside a Docker container and streams its output to connected clients via WebRTC. The simplest description: you docker run a Firefox or Chromium image, open localhost:8080 in your browser, and you have a live, controllable browser session that anyone you invite can join and take turns controlling.

The origin story is straightforward and frequently cited in every review: the creator built it because rabb.it shut down and he wanted to watch anime with his friends. Discord kept crashing, his internet couldn’t handle streaming, so he forked an earlier project called Turtus and built the thing himself [1]. The result now has 20,098 GitHub stars and an Apache-2.0 license — one of the cleanest open-source licenses available, meaning you can self-host, fork, and embed without restrictions [merged profile].

It is worth being precise about what Neko actually is, because the marketing framing (“virtual browser”) undersells and misdescribes it in equal measure. It is more accurate to call it a shared remote desktop streamed via WebRTC. The “browser” part is just the most common thing people run inside it. You can run VLC, XFCE, KDE Plasma, Remmina, or any Linux application [4]. Browser happens to be the killer use case, but the underlying mechanism is a containerized X11 display being encoded and streamed to multiple WebRTC peers simultaneously.

---

Why People Choose It

Every third-party article approaches Neko from a different angle, and together they paint an accurate picture of who actually uses it.

The watch party crowd arrives first. The project’s own origin story is about watching anime with friends, and this is still the most emotionally resonant use case. Unlike browser extensions like Teleparty that only work on specific platforms, Neko works on literally any website — if you can open it in Firefox, you can watch it together in Neko. No DRM stripping, no platform limitations: you’re just streaming a browser screen [1][5]. The NasDaddy review describes it as “a bond between me, my friends, and my family” [5], which is either touching or excessive depending on your tolerance for NAS-owner enthusiasm.

The privacy/throwaway browser crowd finds it useful for a specific set of scenarios: opening suspicious links without touching your local machine, accessing websites without leaving your home IP fingerprint, running sessions that are destroyed afterward with no cookies or cache [website]. The deployn.de guide explicitly calls this out as a valid NAS use case — run Neko on your home server, do your sketchy research or one-off logins, and know that nothing hit your daily browser [2].

The internal jump host crowd is the most technically sophisticated segment. Neko gives you a browser running inside your network, accessible from outside it, without exposing any services directly. You browse to an internal dashboard through Neko instead of punching a hole in your firewall or managing a VPN for every team member [3][website]. The website notes that session activity can be recorded for auditing — a detail that matters for compliance-conscious IT setups.

The NAS hobbyist crowd uses it because, as the NasDaddy author puts it, “many people choose to buy a NAS because of its built-in browser — Synology still doesn’t have one” [5]. Neko fills that gap and runs comfortably on a Synology or QNAP with Container Manager or Portainer.

What ties all these groups together is the same thing: they want control over a browser session, either for privacy, collaboration, or access, and they don’t want a third-party company routing their traffic through a cloud service to provide it.

---

Features

Core streaming:

• WebRTC streaming with under 300ms latency — the GIGAZINE hands-on test confirms YouTube playback was “clear” with no noticeable lag [4]
• Multi-participant control: one admin, multiple members who can request and receive cursor/keyboard control [3][4]
• Admin can restrict control entirely, locking the session to view-only [4]
• Chat sidebar for participants, separate from the shared screen [4]
• Emoji reactions overlaid on the shared screen in real-time [4]

Browser and application support:

• Firefox (default Docker image)
• Chromium, Google Chrome, ungoogled-chromium
• Microsoft Edge, Brave, Vivaldi, Opera [4]
• VLC media player
• Remmina remote client
• Full desktop environments: XFCE, KDE Plasma [4]

Session management:

• Live broadcasting via RTMP to Twitch, YouTube, or any RTMP endpoint — streams continue even with zero participants [website]
• Session recording for auditing
• Persistent browser: session state survives container restarts, accessible from any device [website]
• Throwaway mode: session destroyed on exit, no local data retained [website]
• File upload/download between local machine and virtual browser [3][5]
• Clipboard synchronization [3]

Security/access:

• Role-based access: admin and member roles [3]
• Admin can lock the room to new participants [4]
• All traffic is encrypted via WebRTC — from the ISP’s perspective, it looks like a video call [website]
• Intellectual property protection: only video/audio transmitted, source code never reaches clients [website]

Infrastructure:

• GPU acceleration support for improved performance [docs]
• API for programmatic room creation (mentioned in README) [merged profile]
• Docker images via GitHub Container Registry (ghcr.io/m1k1o/neko/) [2]

---

Pricing: What You Actually Pay

There is no SaaS version of Neko. The software is free (Apache-2.0), and you run it on your own infrastructure. The relevant cost question is: what does the infrastructure cost?

Self-hosted:

• Software: $0
• VPS to run it: $10–20/mo
• Hardware minimum: 2–4 CPU cores, 3–4 GB RAM for a smooth 720p session [2]
• Storage: minimal (the container itself, not large)
• Optional: TURN server for NAT traversal (Coturn self-hosted is free; commercial TURN services like Twilio or Metered charge per GB of relayed traffic)

What you’d otherwise pay for similar functionality:

• TeamViewer: $24.90–$42.90/mo for remote access (single user)
• Kast (watch parties): free tier with limits, paid plans for private rooms
• Amazon Prime Video Watch Party: free but locked to Prime content
• Parsec (remote desktop streaming): free for personal, $8–19/mo for teams

The honest comparison is not a single product. Neko competes differently for each use case: against TeamViewer for the jump host use case, against Kast/Teleparty for watch parties, against commercial VDI solutions for persistent browser access. In every comparison, the self-hosted math wins decisively on cost — but only if you’re comfortable with Docker and can handle the NAT configuration.

---

Deployment Reality Check

The one-line Docker run command that appears in every blog post is real and works [1]:

docker run -d -p 8080:8080 m1k1o/neko:firefox

Open localhost:8080, you have a working Neko instance. For local network use, this is the complete story.

For internet-accessible deployment, it gets significantly more involved, and this is where non-technical users will struggle.

What you need:

• A Linux VPS with 2–4 CPU cores and 3–4 GB RAM minimum [2]
• Docker and Docker Compose
• UDP port range open in firewall (52000–52100 typical) — this is required for WebRTC; TCP-only setups will not stream [2]
• A domain and reverse proxy (Caddy/nginx) for HTTPS
• STUN/TURN server configuration for NAT traversal [2]

The deployn.de guide flags STUN/TURN as the most critical and most frequently missed step: “For a reliable connection over the internet (especially behind NAT), configuring STUN/TURN servers is crucial” [2]. This is what separates “works on my LAN” from “works for friends connecting from across the internet.” Google’s public STUN server handles many cases, but if clients are behind symmetric NAT (common in corporate networks and some ISPs), you need a TURN relay server.

What can go sideways:

• WebRTC connectivity failures are the most common support question. The UDP port range must be open and correctly mapped, and the NEKO_WEBRTC_NAT1TO1 variable must be set to your public IP or domain [1][4].
• shm_size: 2gb is required in the compose file. Chromium-based browsers will crash without sufficient shared memory [2].
• The v3 configuration variables (used in current images) are different from the v2 variables. Guides written before mid-2024 may use outdated env var names like NEKO_PASSWORD instead of NEKO_MEMBER_MULTIUSER_USER_PASSWORD [2][4] — check the documentation version you’re following.

Realistic time estimates:

• Technical user on a fresh VPS, local-only use: 15–30 minutes
• Technical user with internet access and HTTPS: 1–2 hours
• Non-technical founder following a guide: half a day, including the frustrating NAT debugging session

---

Pros and Cons

Pros

• Apache-2.0 license. Genuinely free, commercially usable, no Fair-code restrictions, no “contact us for enterprise” walls [merged profile].
• Not platform-locked. Works on any website in any browser — no Teleparty-style “only Netflix/YouTube” limitations for watch parties [1][5].
• One Docker image covers multiple use cases. Same installation serves watch parties, throwaway browsing, jump host, and persistent workspace [5][website].
• Multi-browser images available. Firefox, Chromium, Chrome, Edge, Brave, Vivaldi, Opera — all maintained as separate container images [4].
• Live RTMP broadcasting included. Stream your session to Twitch or YouTube directly from the container, 24/7 even without participants — a surprisingly capable feature for the price [website].
• Clipboard and file transfer included. The practical paper cuts of shared browser sessions are handled [3].
• GPU acceleration supported for setups where video encoding performance matters [docs].
• 20,000+ GitHub stars signals an active, maintained project with a real community around it [merged profile].

Cons

• NAT/TURN configuration is genuinely hard. The difference between “works on LAN” and “works over the internet” is a STUN/TURN setup that will stop non-technical users cold [2]. This is not a one-line fix.
• Hardware requirements are real. 2–4 cores and 3–4 GB RAM for a single 720p session means a $6 VPS will not cut it. Budget $15–20/mo for something that doesn’t lag [2].
• No built-in authentication system beyond shared passwords. Admin password and user password, set via environment variables [1][2]. There is no user management, no invite system, no OAuth — you share credentials manually.
• Not a media server. It streams a browser screen via WebRTC. Video quality and latency depends on the server’s uplink and the WebRTC connection quality, not CDN delivery. For pure video streaming at scale, purpose-built solutions win [merged profile].
• UDP firewall rules required. Many shared hosting environments block UDP port ranges. If your provider or home router doesn’t allow opening UDP 52000–52100, you cannot run Neko for external access [2].
• v2 to v3 config variable breaking changes. Existing guides that use v2 env vars will fail silently with v3 images. The documentation is versioned but not all community guides have caught up [2][4].

---

Who Should Use This / Who Shouldn’t

Use Neko if:

• You want to host watch parties with friends on any streaming site, not just the ones Teleparty supports.
• You have a NAS or home server and want a persistent, private browser you can access from any device.
• You’re an IT admin who wants to give team members access to internal web tools without a full VPN setup.
• You need a throwaway browser for one-off sessions that leave no trace on your local machine.
• You’re comfortable with Docker and can handle firewall/NAT configuration, or are willing to learn.

Skip it if:

• You’re a non-technical user and don’t have someone to handle the initial setup and NAT configuration. The one-line Docker command is real, but getting it to work for remote friends is not.
• Your VPS is a $4–6/mo entry-tier instance. Neko needs actual CPU cores for video encoding — shared-core budget instances will deliver stuttery streams.
• You want a proper media server for family video streaming. Use Plex, Jellyfin, or Emby instead — those are built for delivery, not virtual desktop streaming.
• You need SSO, audit logs, or user management. Neko has admin/member passwords and nothing else.

---

Alternatives Worth Considering

• Jellyfin — if watch parties with your own media library is the main use case, Jellyfin’s SyncPlay feature does this natively without the WebRTC overhead.
• Guacamole — Apache Guacamole is a more mature remote desktop gateway if the jump host / internal resource access use case is primary. More complex to set up but more polished for multi-user enterprise use.
• Kasm Workspaces — the commercial/enterprise cousin of the “browser in a container” concept. More polished, user management included, but the free tier is limited and the paid version costs real money.
• RustDesk — self-hosted remote desktop with proper authentication, user management, and cross-platform clients. Better for individual remote access, not collaborative shared sessions.
• Teleparty — browser extension for synchronized streaming on Netflix, YouTube, Disney+, etc. Zero infrastructure required. The right choice if you only watch on those platforms and don’t need anything else.

---

Bottom Line

Neko is a genuinely useful tool that does exactly what it says: it runs a browser (or any Linux app) in a container and streams it to multiple users simultaneously via WebRTC. The watch party origin story is still the most compelling use case, but the jump host, throwaway browser, and persistent browser use cases are equally valid and not well-served by other self-hosted tools. At 20,000 GitHub stars and an Apache-2.0 license, it’s a mature project with a real community and no commercial traps.

The honest caveat is hardware and networking. If you assume the Docker one-liner is the full story, you will be frustrated within five minutes when remote friends can’t connect. STUN/TURN configuration and proper UDP firewall rules are prerequisites, not optional extras. Factor in a VPS with real CPU cores — budget $15–20/mo, not $6. For a technically capable user who can handle these requirements, Neko is an excellent tool. For someone who needs it working for non-technical family members with no IT help, it is a weekend project with a real risk of never quite working right.

---

Sources

1. Code Pulse / Coding Nexus (Medium) — “n.eko: A Full Virtual Computer That Runs in Your Browser. One Docker Command.” (Mar 9, 2026). https://medium.com/coding-nexus/n-eko-a-full-virtual-computer-that-runs-in-your-browser-one-docker-command-66e8d655e186
2. deployn.de — “Neko: Your Virtual Team Browser – Installation with Docker”. https://deployn.de/en/blog/neko-install/
3. Hostinger — “Neko VPS Docker Hosting | Virtual Browser Self-Hosted”. https://www.hostinger.com/id/vps/docker/neko
4. GIGAZINE — “‘n.eko’ allows multiple people to log in at the same time for video viewing parties and interactive presentations” (Jan 17, 2026). https://gigazine.net/gsc_news/en/20260117-neko/
5. NasDaddy — “Living in the Nas Browser: How to Create a Secure and Happy Tech Life with Neko” (Dec 27, 2023). https://nasdaddy.com/en/how-to-install-neko-on-your-nas/

Primary sources:

• GitHub repository: https://github.com/m1k1o/neko (20,098 stars, Apache-2.0 license)
• Official website and documentation: https://neko.m1k1o.net
• Documentation (v3): https://neko.m1k1o.net/docs/v3/introduction