Work standards, home standards: why one setting can't fit both

Every household that takes its internet posture seriously eventually meets the same contradiction. The breadwinner needs the web the way a tradesman needs a sharp blade — suppliers, payments, forms, the industry's whole online plumbing. The home needs the web the way a house needs a front door — present, controlled, mostly closed. Families that try to satisfy both with one setting discover the iron law of one-size configurations: sized for the office, the home is open; sized for the home, the office is crippled. The resolution is not a better compromise setting. It is refusing the premise that there should be one setting at all.

Context is a real variable

The insight that unlocks the whole question: who is browsing matters, and so does where and for what. A standards regime mature enough to distinguish the nine-year-old from the mother is mature enough to distinguish the desk from the kitchen:

• The work context runs the guarded-broad posture — the unpredictable legitimate needs of a livelihood, inside category walls and sight protection, as laid out in the home-office setup. Its width is a business requirement, justified per role.
• The home context runs narrower — the household's shared machines on the family posture, the children's access on allow-only, the whole two-architectures logic applied per person. Its narrowness is not distrust of adults; it is the recognition that the kitchen serves everyone, including the seven-year-old doing homework at it.
• The seam between them is where discipline lives: work width never leaks homeward as a convenience ("just use the office login for that"), because every leaked exception becomes the household's new floor.

“A standard that ignores context will be violated by context — daily, reasonably, and then habitually.”

kolbo.life

Who decides the widths

Per-context standards raise a governance question families should answer out loud. The pattern that works: the household's posture is a family decision (often with a rav's guidance on the tiers), while the work context's width is justified by the work itself — this portal because these suppliers, this category because this trade. Work width earned by enumeration stays honest; width granted as a vibe ("I need everything, I'm an adult") drifts. Businesses run the same review on their fleets — the employer-side version, with its oversight tooling, is exactly the "IT login & customization" and "employee oversight" territory the KolBo Browser business platform describes, and the enrollment path for that world is its own product.

Annual review belongs on the calendar for both contexts: the work list sheds dead portals; the home tiers graduate with the children — the same season-change rhythm every standing policy in the household deserves.

One platform, many widths

The historical reason families settled for one bad setting was tooling: consumer products offered one dial per product, so two contexts meant two products, two vendors, and seams everywhere. The platform model dissolves exactly this. A browser whose protection is, in the homepage's words, "fused into the build itself" carries policies rather than a single posture — per-person, per-context, per-device widths as configurations of one secured engine, the position KolBo Browser holds as "the first kosher Chrome." One engine means one set of walls everyone trusts, with widths that fit each door — and no seam between products for a workaround to live in. The same per-role logic extends to the pocket: the work phone's specific tools against the family phone's tier, per the work-phone patterns.

Frequently asked questions