KRNL Browser

KRNL is a terminal-based web browser, and it's paired with BrowserBox, a self-hosted remote browser engine that powers it. Together they let you browse the web from your command line on infrastructure you control, rather than through a graphical browser on your desktop or a cloud service someone else runs. Both come from DosayGo, with BrowserBox as the underlying engine and KRNL as the terminal client that connects to it.

The idea is straightforward once you see the split. BrowserBox is the part that actually renders and runs the web, and you host it yourself, on your own hardware. KRNL is the lightweight front end you drive from a terminal, connecting to that BrowserBox instance over SSH or a login link. So the heavy browsing work happens on a machine you own, and you interact with it through a text interface rather than a full graphical window. That separation is what makes it a remote browser, the session lives on the host you set up, and the terminal is your window into it.

That architecture is the whole point. Because you host BrowserBox yourself, there's no cloud dependency in the middle, and the browsing session lives on infrastructure you picked rather than a third party's servers. For anyone who wants web access from a server, a remote box, or a terminal-only environment, KRNL gives them a browser that fits that world instead of forcing a desktop app into it. It also means the browsing runs on hardware you control end to end, which is a different posture from handing the session to a hosted service.

Setup is developer-shaped and kept short. You install BrowserBox with a curl script, set a LICENSE_KEY environment variable, run the setup and start commands, and then connect to it with the KRNL client. The whole flow is a handful of shell commands, so it slots into the way technical users already provision machines. License keys are delivered instantly, within about a minute of purchase, so there's no waiting between paying and getting a working setup.

The client side runs where you work. KRNL ships builds for the three major desktops, with binaries for macOS on Apple Silicon, Linux on x64, and Windows on x64, so you can connect from whichever machine you sit at. Because the client is just the terminal front end, it stays light while the BrowserBox host does the actual browsing, which keeps the local footprint small regardless of which platform you launch it from.

It's clearly built for a technical audience. Self-hosting an engine, managing an SSH connection, and driving a browser from the terminal all assume comfort at the command line, and the people who'll get the most out of it are those who already want browsing to happen on hardware they control. It's a narrower tool than a mainstream browser by design, trading the familiar graphical experience for self-hosted control and a terminal-first workflow. That's a deliberate tradeoff rather than a shortcoming to work around.

Before committing, you can try it live. There's a free demo you reach by running an SSH command against the maker's host, which lets you feel out the terminal browsing experience without installing anything or paying first. That's a sensible way to check whether a text-driven, self-hosted browser actually suits how you work before buying a license, since the workflow is different enough from a normal browser that trying it beats reading about it.

It helps to picture where a browser like this earns its place. Plenty of machines never get a graphical desktop, a headless server, a cloud instance, a box you only ever reach over SSH, and on those a normal browser simply isn't an option. KRNL is built for exactly that situation, giving you a way to load and read the web from the same terminal you already use to run the machine. Pair that with BrowserBox running on hardware you own, and the whole browsing session stays on infrastructure you administer rather than a rented cloud tab, which is the ownership posture the product is selling. For teams that care about keeping that control in-house, the per-seat license simply mirrors how many people each need their own activated setup.

On pricing, KRNL and BrowserBox come together under one license. It's $179 for a one-year, per-seat license that activates both the BrowserBox engine and the KRNL terminal browser on hardware you control. There's no free tier beyond the live demo, and the license is annual and per seat, so the cost scales with how many people each need their own activation. For an individual or a small team that specifically wants self-hosted, terminal-driven web access, that's the shape of the deal.