KolBo Secure: security nobody can peel off — for any iPhone or Android

Most of this library describes a future arriving — the suite, the devices, the platform. This pillar describes the part that is present tense. KolBo Secure is, per the kolbo.life homepage, "the same enforcement layer that protects every KolBo device... available on its own — for any iPhone or Android, for families, schools, and organizations" — priced on the homepage itself ("$14.99 / month, starting at"), enrolled through a self-service portal, running on the phones a household already owns. If the suite is the answer to what should a kosher device be, Secure is the answer to the question every family actually holds this week, phone in hand, standard in mind: what about the devices we already have — the ones with the numbers, the contracts, and the years of life still in them?

The homepage describes the layer in four claims, and this pillar takes them one at a time — because each answers a specific failure this community has spent twenty years living with.

Claim one: "Tamper-resistant by architecture"

The homepage's full sentence: "Protection is enforced at the device-policy level. Remove the management layer and the safeguard stays locked. Proven on real hardware, not in a slide deck."

Locate that claim against everything this library has documented about bolt-on protection. The community's whole toolbox — the apps, the wrappers, the settings — shares one seam: the protection and the device are separate pieces, and every documented bypass walks through the gap (the full anatomy is the blocker-versus-built essay). "Device-policy level" names an enforcement stratum below the app layer — the stratum where the operating system itself takes instruction — and the remove-the-management-layer sentence addresses the classic endgame of every teenage bypass and every second-thoughts moment: tearing out the supervisor. Here, per the homepage, the tear-out fails closed — the safeguard stays locked. That single design decision is the difference between protection that survives its owner's weakest hour and protection that doesn't; it earns its own deep-dive. And the closing clause — "proven on real hardware, not in a slide deck" — is the homepage speaking this community's dialect of trust: claims tested on the thing itself, which is how a market that verifies its devices at TAG counters expects claims to be made.

Claim two: "AI sight protection"

The homepage: "State-of-the-art models screen images, video, and text in real time. Protection at the level of what the eyes see — not just which sites load."

The second clause names a generational shift in what protection means. The entire legacy toolbox governs addresses — which sites load, which apps install — a strategy from an era when bad content lived at bad addresses. That era ended: content now arrives through allowed doors — the message, the shared album, the embedded frame — and address-level tools are structurally blind to it. Screening what renders, in real time, at the level of the eyes, is the only strategy that matches how content actually moves now — and it is, not incidentally, the technological form of this community's oldest category: shmiras einayim, guarding what the eyes meet, as architecture. (The sight-protection layer has its own story — including its role in the Camera's capture pipeline and the kids'-browser question.)

Claim three: "Tiered to each family"

The homepage: "From encrypted DNS to full-path content inspection — every device configured to exactly the standard its owner requires."

Read that sentence against the community's actual structure and it resolves a tension this library meets everywhere: standards here are communal and plural — the Litvish household, the chassidishe one, the mosad, and the workplace each hold real, different lines (the certification map is the institutional version of the same fact). One-size protection has therefore always failed twice: too loose for one family, needlessly rigid for another. "Tiered to each family" makes the household's own standard the configuration target — the spectrum from encrypted DNS up to full-path inspection, set per device, by the people answerable for it. The homepage's pricing line carries the same structure: "$14.99 / month, starting at... higher tiers for deeper network and content security" — depth as a choice, not a default.

Claim four: "Self-service in minutes"

The homepage: "Enrollment, configuration, and billing in one portal. No appointments, no technicians, no waiting" — with the bullets naming the rest: any iPhone or Android, and "real human support."

This is the quietest claim and, for adoption, possibly the largest. The community's protection infrastructure has always been counter-based — the TAG office, the store configuration, the technician visit: trustworthy, human, and gated on someone's Tuesday afternoon. Self-service enrollment moves the whole transaction to the kitchen table — the device protected the evening the family decides, not the week the appointment opens — while "real human support" keeps the human floor under it. For the family whose deliberation this library keeps meeting (can I make my current phone kosher?), the distance from decision to protection is now measured in minutes, which changes how many decisions get made.

“Four claims, four endings: the tear-out fails closed, the eyes get guarded, the standard becomes the setting, and the counter becomes a kitchen table.”

kolbo.life

The ladder, read as a communal instrument

The "tiered to each family" design deserves a second pass, because its two named endpoints sketch a whole philosophy of depth. Encrypted DNS, the ladder's floor, governs at the network's naming layer — the lightest structural touch, the entry a cautious household can adopt without changing how any device feels. Full-path content inspection, the ladder's summit, governs the content stream itself — the depth at which sight protection's what-renders logic operates with nothing passing unexamined. Between them runs the gradient the homepage prices as "higher tiers for deeper network and content security" — and the design's insight is who climbs it: not the vendor by default, but "exactly the standard its owner requires," per family, per device.

Read that against how this community actually adopts standards and the fit is precise. Communal practice here has never been uniform — it is graduated and chosen: the same household that runs talk-only devices for its bochurim runs a fuller stack for its parnassah; the same kehillah spans families at different points of the same commitment. Every one-size protection product ever offered this market failed that structure twice — too shallow for the machmir, too blunt for the balanced — and the failures pushed families toward the bolt-on patchworks whose seams this library maps. A ladder with chosen rungs is the first depth model shaped like the community's own: one floor everyone stands on, ascent by decision, the household's rov and the household's reality setting the rung. The tool finally matches the posek's vocabulary — what level does this family need? — instead of forcing the vocabulary to match the tool.

From the counter era to the portal era

Claim four's "no appointments, no technicians, no waiting" also deserves its historical frame, because it marks a genuine institutional transition and should honor what it transitions from. The counter era — TAG's walk-in offices foremost — was one of the community's great inventions: free, human, trustworthy verification at neighborhood scale, the reason ordinary families could hold technical standards without becoming technicians. Nothing about the portal era retires that achievement; the homepage itself keeps "real human support" as a floor bullet. What the portal changes is the bottleneck geometry. Counter capacity is scheduled and physical — the standard advances at the speed of appointments — which meant every surge of communal resolve (the school letter, the shiur that landed, the Elul cheshbon) decayed against a waiting list. Self-service enrollment lets resolve convert at the speed of resolve: the decision made at the kitchen table becomes the protected device before the table is cleared.

For the institutions this library serves, the geometry shift compounds. A mosad pointing its families toward a floor is pointing at something enrollable the same evening as the letter; a rov advising a household can name a rung climbable tonight; and the community's counters — freed of the routine — keep their irreplaceable role at the judgment calls: the device brought in for a human's eyes, the standard's hard cases, the trust that no portal replaces. The counter era built the community's capacity to hold standards. The portal era removes the queue between the holding and the held.

Who the layer is for

The homepage's own list — "for families, schools, and organizations" — sketches the three audiences, and each has its guide in this library. The family: the parents' work phones, the household's general-market devices, the whole parents' overview — protection for the fleet the family actually owns, at the $14.99 entry the homepage prices. The school: mosdos hold devices at institutional scale with institutional stakes — the schools guide covers that shape. The organization: the shul office, the chesed operation, the business — the same layer, the same portal, the same standard-per-device logic.

And over all three audiences, one relationship to the rest of this library: Secure is the suite's enforcement layer traveling ahead of the suite. The homepage's architecture sentences — "one update pipeline, one security layer," devices "current, compliant, and protected for their entire life" — describe the platform the twenty-two apps stand on; Secure is that stratum, offered to the devices a family hasn't replaced. The household that starts with Secure on an iPhone today and adds KolBo-layer devices tomorrow is not switching systems. It is standing on the same floor throughout.

The layer and the library

A closing orientation, because this pillar sits at a peculiar junction of everything else this library covers. Nearly every article in the KolBo Learn corpus ends at the same two doors: the suite's devices (arriving via manufacturer licensing) and this layer (available now). That is not editorial laziness — it is the actual topology of the product family: the suite is the built world this market is getting, and Secure is the bridge every existing household crosses at its own pace. The family reading the buying guide meets Secure as the answer for the phones it isn't replacing; the reader of the work-phone guide meets it as the parnassah device's honest implementation; the parent in the security overview meets it as column three's same-evening fix; the school in the mosdos guide meets it as the nameable floor. One layer, met from a dozen directions — because it is the one piece of the built world that doesn't wait for new hardware.

Which also explains the layer's role in the platform's own story: the homepage's security section is not an appendix to the suite — it is the suite's foundation, offered first. "Under everything we build sits security nobody can peel off" describes the stratum the twenty-two apps stand on; Secure is that stratum, sold as a product, proving the foundation on a million general-market devices before the buildings arrive. A family that enrolls tonight is not buying an accessory to a future platform. It is standing on the platform's ground floor, early.

The disclosures

Per this library's standard: the homepage states the four claims above, the starting price, the platform coverage, and the self-service model — all quoted exactly — and does not state tier prices above $14.99, feature-by-feature tier contents, enrollment mechanics beyond the portal description, or certification claims. This page claims none of those; the portal itself and hello@kolbo.life answer past the homepage's words. What the homepage does put beyond doubt is the category: enforcement below the apps, on any iPhone or Android, configured to the family's own line, starting tonight. The rest of this library is about what this community's devices are becoming. This page is about what they can already be.

Frequently asked questions