AI ERP with agents inside the systems you run
AI phone and voice agents for real calls
LLM.coPrivate, self-hosted LLM deployments
Legal AI infrastructure for firms
AI RFP discovery and response drafting
Automatic.coBusiness process automation
CyberAttack.aiThreat detection and defense
Secure AI virtual data roomsneko
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.
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.
Get the neko source
Clone the repository and explore it locally.
git clone https://github.com/m1k1o/neko.gitcd neko# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
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 |
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.
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.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
neko FAQ
Can multiple users control the same browser simultaneously?
Is my browsing private if I run Neko locally?
Can I embed Neko in my own web app?
What hardware do I need to run Neko?
From evaluation to production software
Bringing neko into production usually means new services, new interfaces, and new failure modes. DEV.co is a software development agency that builds all three and stays on for the open-source devops maintenance.
Ready to deploy a collaborative virtual browser?
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.