Open-Source DevOps · m1k1o

neko

Neko is a self-hosted virtual browser and desktop environment that streams via WebRTC, allowing multiple users to simultaneously view and control a containerized Linux environment from a web browser. Deployed in Docker, it enables use cases from collaborative watch parties and presentations to persistent personal workspaces and automated browser tasks.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/m1k1o/neko

21.4k

GitHub stars

1.5k

Forks

Primary language

Apache-2.0

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	m1k1o/neko
Owner	m1k1o
Primary language	Go
License	Apache-2.0 — OSI-approved
Stars	21.4k
Forks	1.5k
Open issues	180
Latest release	v3.1.0 (2026-04-02)
Last updated	2026-06-14
Source	https://github.com/m1k1o/neko

What neko is

Built in Go with a Vue.js frontend, Neko captures X server display frames and streams video/audio via WebRTC to multiple clients. It supports real-time multi-user input synchronization, RTMP broadcasting, and arbitrary Linux applications (not limited to browsers), with state isolation via containerization and optional VPN/Tor integration.

Quickstart

Get the neko source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/m1k1o/neko.git2cd neko3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Multi-user collaborative browsing & watch parties

Host synchronized browser sessions where multiple participants can view, control, and chat in real-time. Ideal for watch parties, interactive presentations, and code debugging sessions without requiring external services.

Persistent, privacy-isolated personal workspace

Deploy a persistent browser with retained cookies and state accessible from any device, while keeping sensitive data server-side. Useful for sensitive tasks, Tor browsing, or throwaway sessions where no client-side footprint is desired.

Embedded virtual browser for web applications

Embed a controlled Linux desktop/browser environment within your own web app via iframe or API, enabling third-party site access, video streaming synchronization, and interactive automation without client software installation.

Implementation considerations

Multi-user synchronization requires careful input queueing and conflict resolution; test with expected concurrent user counts to validate responsiveness.
Docker container resource allocation (CPU, memory, GPU passthrough) directly impacts video quality, latency, and user experience; size containers conservatively and monitor in production.
WebRTC requires accessible STUN/TURN servers for NAT traversal; self-host TURN servers for privacy or rely on public ones (test connectivity in your network environment).
Session state and credentials are server-side only; ensure backend securely manages session tokens, room access control, and user isolation.
Audio sync between video and user actions requires careful buffering; test with multiple participants over varied network conditions (low bandwidth, high jitter).

When to avoid it — and what to weigh

Strict sub-100ms latency requirements — WebRTC introduces inherent network latency. While generally smooth, this is not suitable for real-time gaming, live trading, or ultra-responsive professional CAD work.
GPU-intensive workloads — Neko is designed for CPU-based X server rendering. Running GPU-heavy applications (3D graphics, ML training) inside the container will be inefficient and may not be supported.
Regulated environments requiring hardware isolation — If compliance mandates genuine hardware separation (HIPAA, PCI-DSS), container-based isolation may not meet requirements. Verify with your security/compliance team.
Single-user, low-complexity remote desktop replacement — For simple remote desktop needs, lighter alternatives (VNC, RDP) with less overhead may be more practical. Neko's multi-user synchronization and WebRTC add complexity if not needed.

License & commercial use

Licensed under Apache License 2.0 (Apache-2.0), a permissive OSI-approved license.

Apache-2.0 permits commercial use, modification, and redistribution with minimal restrictions (retain license and copyright notice, provide change documentation). However, no warranties are provided; review liability implications before deploying to production systems with SLA requirements. Consider consulting legal counsel for embedded or high-availability use cases.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Adequate
License clarity	Clear
Deployment complexity	Moderate
DEV.co fit	Good
Assessment confidence	High

Security considerations

Neko runs a full Linux desktop in a container; security depends on container isolation strength, host kernel, and application choices (e.g., Tor Browser vs. standard Firefox). No formal security audit data provided. Input validation and authentication mechanisms are not detailed in provided data—review source code and GitHub security advisories. Multi-user environments require robust session isolation and RBAC. Network exposure is via WebRTC; TURN server and signaling server must be trusted or self-hosted.

Alternatives to consider

Apache Guacamole

Mature clientless remote desktop gateway supporting RDP, VNC, SSH. Lighter weight, but lacks native multi-user collaborative control and audio support.

noVNC + linuxserver/firefox

Open-source VNC client over WebSockets. Simpler deployment for single-user remote access, but no built-in multi-user sync or audio.

Hyperbeam (commercial API)

Closed-source SaaS for embedded virtual browser. Fully managed and battle-tested, but requires vendor lock-in and recurring costs.

Software development agency

Build on neko with DEV.co software developers

Neko offers a powerful, open-source alternative to commercial virtual browser platforms. Start with Docker, configure your WebRTC networking, and enable real-time multi-user collaboration. Our DevOps and application development teams can guide architecture, containerization, and production deployment.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

filebrowser memories yokai

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source DevOps Web Application Development Cloud Deployment & DevOps Custom Application Development Talk to DEV.co

neko FAQ

Can multiple users control the same browser simultaneously?

Yes. Neko is designed for multi-user collaborative control; input from all participants is synchronized in real-time to a single X server desktop. Conflicts are queued.

Is my browsing private if I run Neko locally?

Cookies, history, and credentials are stored server-side in the container, not on your client. However, the Neko server and network operator can observe traffic. For privacy, use Tor Browser image + VPN add-on.

Can I embed Neko in my own web app?

Yes. The neko-rooms project and REST API allow programmatic room provisioning. You can iframe the Neko client or build a custom UI consuming the WebRTC stream.

What hardware do I need to run Neko?

Minimum: 2-4 CPU cores, 2-4 GB RAM per container. Scales with user count and application complexity. GPU acceleration is not natively supported; X11 rendering is CPU-based.

Custom software development services

From first prototype to production, DEV.co delivers software development services around tools like neko. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across open-source devops and beyond.

Ready to deploy a collaborative virtual browser?

Talk to DEV.co Schedule a Consultation