Website blockers versus a browser built kosher: bolted on, or built in

There is a genre of software as old as the consumer internet: the blocker. It arrived as NetNanny-style desktop programs, matured into DNS services and VPN-based protection layers, spawned browser extensions and router-level settings, and in this community it became a serious, subscription-funded industry — Netspark scanning in real time for $15 a month, Gentech running proxy modes at TAG-installed setups, Techloq covering Windows offices from £7.99 a month. Three decades of iteration, real engineering, real benefit in real homes. And across all thirty years and every form factor, the genre has never escaped one sentence: the blocker is not the thing it blocks. Everything that has ever gone wrong with the model lives in that gap.

The three permanent problems of bolted-on blocking

The toggle problem. A blocker is software with an off state — an extension listed in a settings page, an app with an uninstall, a profile a password protects until the password leaks. The industry's countermeasure is meta-locks (passwords on the settings that guard the settings), which works exactly as well as the most careless moment of the most trusted adult in the house. Enforcement that can be switched off is, over a long enough family life, sometimes off.

The second-door problem. Blockers guard doors, and general-market devices are all doors. Chrome supervised? Firefox sideloads. The DNS locked? The neighbor's WiFi isn't. The browser wrapped? The app's built-in webview isn't. The parent guides of 2026 are full of "alternate browser bypass" tutorials because children found the pattern before the vendors named it — and the community's own comparison site concedes that newer operating systems "created significant loopholes" and that not all devices can be filtered.

The treadmill problem. The quietest one, and for households the most expensive: a bolt-on blocker guards a product that updates on its maker's schedule, for its maker's reasons. Every Chrome release can move furniture the blocker depended on; every OS version is a re-verification project. The blocking industry is structurally a chasing industry — its subscriptions fund the chase — and the chased party owes it nothing. Even at communal scale the model holds: Israel's NetFree solves the treadmill by pulling the whole internet through human-reviewed community servers — magnificent, and an admission that at the device, on someone else's software, the seam cannot be closed.

“Thirty years of blockers, one constant: the protection and the protected are different pieces. Every bypass ever written walks through the gap between them.”

kolbo.life

What closing the seam actually means

Now define the alternative precisely, because it is not "a better blocker." The seam closes only when the enforcement and the browser are the same compiled artifact — when there is no "it" to toggle off of, no second door because the device layer holds the line, and no treadmill because the builder of the protection and the builder of the browser are the same party shipping on the same schedule.

That is the design the kolbo.life homepage describes for KolBo Browser, clause by clause: "the full Chromium engine, re-engineered in-house with protection fused into the build itself. Nothing to disable, nothing to bypass" — sitting under a suite-wide layer of "security nobody can peel off," which is "tamper-resistant by architecture... enforced at the device-policy level," where "remove the management layer and the safeguard stays locked," on "one update pipeline, one security layer" so the whole suite "updates together" and stays "current, compliant, and protected for their entire life." Each phrase retires one of the three problems: fused-into-the-build retires the toggle; the device layer retires the second door; one builder on one pipeline retires the treadmill. And the layer sees content, not just addresses: "AI sight protection — state-of-the-art models screen images, video, and text in real time... not just which sites load," which is the difference between blocking a list of doors and guarding what the eyes actually meet.

The full anatomy — the market's delete/wrap/supervise history and the complete bypass record — is the KolBo Browser pillar. And the fairness footnote belongs in print: the blocker industry was never foolish. It built the best possible guards for buildings it didn't own. The critique here is of the situation, and the news is that the situation finally changed — someone built the building.

The practical decision, household by household

• A child's device — the blocker question shouldn't arise: browser-free certified devices are the community's sound default, and the staged first-phone path keeps it that way.
• A general-market phone that must stay (work, reality) — a bolt-on layer is today's tool; choose the serious community services and respect their limits. Better: enforcement below the app layer — KolBo Secure puts device-policy-level, tamper-resistant protection on any iPhone or Android, from $14.99/month, which is the closest a general-market device gets to a closed seam (how to think about "making your phone kosher" is here).
• The next kosher device — the built answer: a browser whose safety is a compile-time property, arriving as part of the suite on devices from manufacturers who license the layer.

Frequently asked questions