NyameBox: A Qt-Based Proxy Client That Pushes sing-box Further
NyameBox, The Original NekoBox Rebranded, the cross-platform Qt proxy utility, empowered by sing-box and thrift
At a glance
- What is it?
- NyameBox, a rebranded fork of NekoBox for PC, is a cross-platform Qt proxy utility built on sing-box and thrift. It adds protocols and subscription formats that upstream sing-box does not support, but its scope and maintenance demands require careful checking before adoption.
- Who is it for?
- NyameBox is for users who need a desktop GUI for sing-box with extra protocols like mieru, juicity, and snell, and who want full JSON subscription support with route and DNS preservation. It is not for those who require macOS or iOS support, since the project explicitly excludes them.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 10 days ago.
- What is it written in?
- Mainly C++, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 14, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What NyameBox Actually Solves
NyameBox is a desktop proxy client for users who want a graphical interface over sing-box. The README describes it as a 'Qt based Desktop cross-platform GUI proxy utility, empowered by Sing-box.' It targets Windows 11/10 (arm64, x86_64, x86) and Linux. The main problem it solves is that sing-box itself is a command-line tool. NyameBox wraps it in a Qt GUI, adds subscription management, and supports TUN mode for system-wide proxying. It also extends the protocol list beyond upstream sing-box. The README lists protocols like mieru, juicity, trusttunnel, vless encryption, xhttp transport, kcp transport, amnezia, and snell as additions not in upstream sing-box. So this is not just a frontend. It is a fork that changes the underlying core.
How It Works: sing-box Core with Thrift and a Custom Fork
The architecture is a Qt client talking to a sing-box core, but the core is a fork. The README credits a separate repository, qr243vbi/sing-box, for the added protocols. The client uses thrift for RPC between the GUI and the core. The README mentions 'empowered by sing-box and thrift.' The core runs in command-line mode, which is now exposed: 'nekobox_core sing-box --help' gives additional information. This means the core executable can be used directly, not just through the GUI. The client also handles subscription formats. For full JSON subscriptions, it imports the entire sing-box configuration, strips inbounds, and adds local application inbounds at runtime. It preserves routing and DNS rules, including fakeip server conversion for newer sing-box versions. This is a deep integration, not a simple link parser. The TUN mode uses the core's TUN capabilities, and profile-specific direct rules are preserved.
Getting It Running: Installation Paths and Package Managers
NyameBox can be installed through several package managers, which is a strength. The README lists WinGet, Chocolatey, Scoop, OBS, COPR, openSUSE, FreeBSD, ArchlinuxCN, Ubuntu PPA, and AUR. For Scoop, the command is 'scoop bucket add extras' then 'scoop install extras/nekobox'. For openSUSE, 'sudo zypper install -y nekobox'. For FreeBSD, 'sudo pkg install -y nekobox'. For ArchlinuxCN, you add the repo to /etc/pacman.conf, install archlinuxcn-keyring, then 'sudo pacman -S nekobox'. For Ubuntu PPA, 'sudo add-apt-repository ppa:miamosagernaki/nekobox' followed by 'sudo apt update' and 'sudo apt-get install -y nekobox'. Portable ZIPs, Windows installers, and AppImages are available from GitHub Releases. The breadth of packaging is notable for a project of this type. It lowers the barrier for users on different distributions.
Subscription Formats: Full JSON Support Is the Differentiator
The README emphasizes subscription formats. It supports share links, JSON array of outbounds, v2rayN link format, and 'limited support for Shadowsocks and Clash formats.' The key feature is full JSON subscriptions for sing-box and v2rayN-style configurations. Imported JSON profiles keep their original routing and DNS rules. They work with URL testing and auto testing, and can be used with TUN mode. This is more than parsing. The client strips inbounds from the imported config and adds local inbounds at runtime. It also handles DNS migration for newer sing-box versions, including fakeip server conversion. Happ subscription links are supported, including encrypted 'happ://' links. You can add subscription groups from browser deeplinks using 'nekobox://' and 'v2raytun://' URLs. For users who manage complex configs, this preservation of routing and DNS is a practical advantage. Many clients flatten configs or ignore route rules. NyameBox tries to keep them intact.
Protocol Coverage: More Than Upstream sing-box
The protocol list is long. It includes SOCKS, HTTP(S), Shadowsocks, Trojan, VMess, VLESS, Hysteria 1 and 2, TUIC, AnyTLS, ShadowTLS, Mieru, Juicity, TrustTunnel, Naive, Wireguard, AmneziaWG, Tailscale, SSH, Tor, Snell, Custom Outbound, Custom Config, Extra Core, and Chaining outbounds. The README specifically notes that mieru, juicity, trusttunnel, vless encryption, xhttp transport, kcp transport, amnezia, and snell are not supported by upstream sing-box. This is a concrete extension. However, it means the core is a fork, and that fork must be maintained. The README points to a separate repository for the core. If that fork lags behind upstream sing-box, users may miss bug fixes or new features. The protocol additions are a double-edged sword. They attract users who need those protocols, but they also create a maintenance burden.
Limitations and Wrong Use Cases
The README's TODO list reveals clear limitations. It lists 'Support for all platforms that supported by sing-box and Qt (except macos & ios)'. So macOS and iOS are explicitly excluded. If you need those platforms, this is the wrong tool. The TODO also includes 'Command line tools', 'OpenRC/runit/systemd integration of nekobox_core', 'Terminal UI', 'Remote control', and 'Replace static UI with declarative UI for editing proxies'. These are unfinished features. The absence of a terminal UI and remote control means the client is GUI-only for management. The lack of init system integration means nekobox_core may not run as a service easily. Also, the README says 'Find the best database storage in the world' as a TODO, which is vague and suggests the current storage may be temporary. The project is under active development, but the TODO list is long. Users who need stable, long-term support may find the unfinished items concerning.
Alternatives and Approach Differences
The obvious alternative is the original NekoBox, from which this project is rebranded. The README credits MatsuriDayo/nekoray as a source. The difference is that NyameBox is a fork with a different maintainer and a custom sing-box core. Another alternative is using sing-box directly with its command-line interface. That gives you the upstream core without the extra protocols. If you need the extra protocols, NyameBox is the only option listed. But if you need stability and upstream compatibility, using sing-box directly or another client like Qv2ray (which is also credited) may be better. Qv2ray is a Qt-based client but does not use sing-box by default. The approach differs: NyameBox is tightly coupled to a sing-box fork, while Qv2ray supports multiple cores. The choice depends on whether you need the added protocols and are willing to accept the fork's maintenance risks.
Maintenance and Licensing Considerations
The project is licensed under GPL-3.0. This has implications for redistribution and modification. If you embed or modify the code, your changes must be open-sourced under the same license. The README credits many upstream projects, including sing-box (GPL-3.0 as well) and Qt (LGPL/commercial). The recent release history shows activity: 5.11.28.3 on 2026-08-26, 5.11.28.2 on 2026-07-30, and 5.11.28.1 on 2026-07-25. That suggests a regular release cadence. However, the project is a rebrand, and the original NekoBox may have a larger user base. The maintenance cost for a user is moderate: you need to track releases and the sing-box fork. The README provides a changelog channel on Matrix and Telegram, which helps. The packaging is extensive, but each package manager may lag behind the latest release. You should check the version available in your package manager against the latest release. The GPL-3.0 license means you can modify the code, but if you distribute your version, you must provide source. This is not a permissive license like MIT.
Editorial conclusion
NyameBox is for users who need a desktop GUI for sing-box with extra protocols like mieru, juicity, and snell, and who want full JSON subscription support with route and DNS preservation. It is not for those who require macOS or iOS support, since the project explicitly excludes them. Before adopting, verify the status of the sing-box fork, the stability of the extra protocol implementations, and the maintenance cadence of this rebranded project. The recent release 5.11.28.3 shows active development, but the TODO list includes unfinished items like remote control and declarative UI, so expect change. If you rely on upstream sing-box features, confirm they are not broken by the fork's additions.
Community notes