carbonyl vs neko

Terminal browsing and shared remote desktops compared

carbonyl renders Chromium-based web pages directly in a terminal, including over SSH and without a window server. neko streams a containerized browser or other desktop application over WebRTC for remote, shared use.

carbonylneko
LanguageRustGo
LicenseBSD-3-ClauseApache-2.0
Stars19.5k22.5k
Forks5841.6k
Last analyzedOct 7, 2026Oct 11, 2026

Key differences

  • carbonyl focuses on rendering web pages locally in a terminal; neko streams a live containerized desktop to connected users.
  • carbonyl supports modern web features and media in a console; neko supports shared sessions with multiple participants, audio, and control.
  • carbonyl is written in Rust and licensed under BSD-3-Clause; neko is written in Go and licensed under Apache-2.0.
  • carbonyl can be installed through npm, Docker, or a binary; neko requires deploying a containerized application and configuring network access for WebRTC.
  • carbonyl is aimed at terminal use where a graphical browser is unavailable; neko supports watch parties, collaboration, and remote access to applications beyond browsers.
  • carbonyl's Chromium-based runtime can require a substantial build; neko's setup and deployment details vary by application and image.

Choose carbonyl if you…

  • need Chromium-based pages in a terminal, including over SSH or without a window server.
  • want modern web pages, JavaScript, or media in a console environment.
  • prefer terminal browsing over streaming a shared desktop.
Read the carbonyl analysis →

Choose neko if you…

  • want multiple people to view and control the same browser or desktop session.
  • need WebRTC streaming for watch parties, teaching, support, or collaborative work.
  • want to make a containerized application or desktop environment remotely accessible.
Read the neko analysis →

Compare the numbers side by side, or add more projects

This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.