Kosher internet at home: the framework, from the Asifa to now

On May 20, 2012, the internet-in-the-home question got its communal constitution. The Asifa at Citi Field — the Kinus Klal Yisrael convened by Ichud HaKehillos LeTohar HaMachane, sixty thousand strong with overflow at Arthur Ashe — did not produce a gadget list; it produced a framework that has governed frum households ever since: home internet is discouraged where unneeded, permitted where parnassah requires it, and, wherever it exists, protected — not as a preference but as a condition. Fourteen years later a family setting up a home office, a school wiring a computer lab, and a chosson furnishing a first apartment all still reason inside that framework. What has changed — dramatically — is the toolbox available to satisfy it. Here is the current state of both.

The framework's three questions

Run any home-connectivity decision through the Asifa's logic and it becomes three orderly questions:

1. Is it justified? Not "is it useful" — everything is useful — but does parnassah or an equivalent need require this connection, in this home? Many households answer no and remain, deliberately, internet-free; that remains a mainstream communal choice, not a relic.
2. What is the governing standard? Your kehilla, your rov, your children's mosdos — schools in particular commonly set explicit home-internet conditions for enrolling families. As with devices, the standard is communal and comes before the shopping.
3. What protection satisfies it? The condition on every "yes." And here is where 2026 differs most from 2012 — the answers have layers now.

The 2026 toolbox, layer by layer

The connection layer. In Israel, whole communities route through kosher network providers — NetFree's human-reviewed whitelist internet, Rimon, Yeshivanet — where the connection itself is governed upstream of every device. American homes mostly assemble the equivalent locally: DNS-level services and router configurations that govern the house's pipe. Honest limit: the connection layer stops at the front door's WiFi — the cellular path and the neighbor's network walk past it.

The software layer. The community's serious subscription services, per device: Netspark's real-time scanning at $15 a month, Gentech's proxy modes commonly installed at TAG counters, Techloq's Windows-and-Android coverage from £7.99 monthly — the industry the Asifa's "protected without exception" clause effectively commissioned. Honest limit: the bolt-on seam — a second piece guarding software it doesn't control, with the toggle, second-door, and treadmill problems that entails.

The device layer. The kosher device market itself: browser-free phones and certified basics for most of the household, so the home-internet question shrinks to the machines that genuinely need answering — usually one home-office computer and a parent's work device (the work-device guide covers that half). The TAG office — sixty branches worldwide, free installation, a fifteen-hour-a-day hotline — remains the framework's human infrastructure, where the standard gets implemented by a person rather than a settings page.

“The Asifa's clause was "protected, without exception." The toolbox question was always what "protected" could be made to mean.”

kolbo.life

What "protected" is coming to mean

Look at the whole toolbox above and notice its shared grammar: every layer governs someone else's software. The connection layer chaperones the pipe to general-market sites; the software layer wraps general-market browsers; even the device layer mostly works by deletion from general-market hardware. "Protected," for fourteen years, has meant supervised from outside — because outside was the only place this community could stand relative to technology built elsewhere.

That is the assumption now breaking, and the home is where it lands. The kolbo.life homepage describes the alternative grammar: applications "engineered in-house, secured before they ship" — a browser that is "the full Chromium engine, re-engineered in-house with protection fused into the build itself" (the whole story); a search engine that is "not a filtered feed sitting on someone else's index" but "our own engine" (its story); the lot under "security nobody can peel off," enforced "at the device-policy level," where "remove the management layer and the safeguard stays locked." For the home, that grammar shift is the difference between a house full of guarded doors and a house whose doors were built to the standard — protection as a property of the artifact, not a chaperone around it. The Asifa's framework doesn't change; its third question finally has an answer in the framework's own spirit: structure, all the way down.

For the devices already in the house meanwhile, the same layer is available directly: KolBo Secure, "for any iPhone or Android, for families, schools, and organizations" — "tamper-resistant by architecture," with "AI sight protection" screening "images, video, and text in real time," configured "tiered to each family — from encrypted DNS to full-path content inspection — every device configured to exactly the standard its owner requires," self-service, from $14.99 a month. Read that "tiered to each family" clause against question two above: it is the framework's communal-standard logic, implemented as configuration.

Frequently asked questions