What is Neko used for?

Neko is a self-hosted virtual browser that runs inside Docker and streams to multiple users over WebRTC, for private browsing, shared sessions and testing. It is a good fit for shared browsing sessions for a team, privacy-focused disposable browsing and testing web apps in a clean environment.

Yes. Neko is open source under the Apache-2.0 licence. Its source code is on GitHub at m1k1o/neko and is written mainly in Go.

Yes. Neko is open source, so the software itself is free to use.

Can I self-host Neko?

Yes. Neko can be self-hosted on your own server or infrastructure; there is no official hosted version.

What are some alternatives to Neko?

Similar open-source tools in the Productivity category include BentoPDF, OmniTools and Homebox. SaaS products in the same category include canihavesex.today, 1% Better and AirSpell.

Is Neko actively maintained?

Yes. The most recent commit to Neko was on 30 September 2026, and the latest release is v3.1.6, published on 30 September 2026. The project has 22k stars on GitHub.

Neko: open-source productivity

About Neko

Neko, written n.eko, is a self-hosted virtual browser that runs in a Docker container and delivers its screen to users through WebRTC. It lets you run a fully functional browser, and other applications, in an isolated environment, then access it securely from anywhere, which supports privacy-minded browsing and a clean separation from your own machine.

A key capability is that several people can connect to the same virtual browser at once. That makes it suitable for teams that need to share a browser, for individuals using multiple devices on one session, and for developers testing web applications. The topics mention remote control, remote desktop and media streaming, and the server is written in Go with a Vue front end.

Neko is Apache-2.0 licensed and documented at neko.m1k1o.net. Because it is container-based, you deploy it on your own server with Docker, so no hosted service is involved. It appeals to homelab users, privacy enthusiasts and groups who want shared, disposable browsing sessions.

Key features

Browser running inside Docker
WebRTC streaming of the session
Multiple users on one session
Isolated and private browsing environment
Remote control and remote desktop use
Go server with Vue interface

Good fit for

→Shared browsing sessions for a team
→Privacy-focused disposable browsing
→Testing web apps in a clean environment

Built with: Go; Docker; Vue
Tags: virtual-browser; webrtc; docker; self-hosted; remote-desktop; privacy; golang; browser

Neko: questions and answers

What is Neko used for?: Neko is a self-hosted virtual browser that runs inside Docker and streams to multiple users over WebRTC, for private browsing, shared sessions and testing. It is a good fit for shared browsing sessions for a team, privacy-focused disposable browsing and testing web apps in a clean environment.
Is Neko open source?: Yes. Neko is open source under the Apache-2.0 licence. Its source code is on GitHub at m1k1o/neko and is written mainly in Go.
Is Neko free?: Yes. Neko is open source, so the software itself is free to use.
Can I self-host Neko?: Yes. Neko can be self-hosted on your own server or infrastructure; there is no official hosted version.
What are some alternatives to Neko?: Similar open-source tools in the Productivity category include BentoPDF, OmniTools and Homebox. SaaS products in the same category include canihavesex.today, 1% Better and AirSpell.
Is Neko actively maintained?: Yes. The most recent commit to Neko was on 30 September 2026, and the latest release is v3.1.6, published on 30 September 2026. The project has 22k stars on GitHub.