Five ways in. One integration behind them.
Pick the door that matches how you reach a kid — a parental-control vendor, a platform, a developer, a school, a regulator, or a parent. Whichever you pick, you wire up the same integrationonce, so a parent's choice and a statute's requirement are honored on every surface. Built on OCSS, the Open Child Safety Specification — the open standard Phosra implements but doesn't own.
California AB 1043 requires operating systems to surface age signals to the apps running on them. The plumbing to consume those signals — and prove you acted on them — has to exist on day one. Phosra is building the conformant router for that signal. Phosra is its reference implementer and one network on it— it doesn't own OCSS. The standard lives at openchildsafety.com.
Each lane is a different way in. The router is the same.
Bespoke per audience — a one-line value prop and its own next action. The two front doors carry their own integration pages today; the lanes behind them are at different stages, and we say which.
Parental-control vendors
You already own the parent relationship. Phosra gives you a conformant way to carry one parental choice across every surface — DNS, MDM, routers, app controls — instead of each platform reinventing age logic. Ingest OS-level age signals, emit signed assertions downstream, and hand a regulator a replayable receipt for every enforcement decision.
Self-serve developers
Drop the router into your stack and get age-appropriate access control that maps to real law. POST /v1/check — age signal in, signed decision out — with tier vocabulary from the 115-category OCSS rule registry. No raw birthdates stored; receipts you can hand a regulator without exporting user data.
Platforms & OS age-signal issuers
You ship the platform — or the operating system that AB 1043 asks to emit the age signal in the first place. Phosra runs the continuous compliance layer above your surface: every mapped statute, every platform capability, the right policy on whichever surface can carry it.
Schools & K‑12
A district has its own authority, parallel to the parental model — and an SSL-inspecting gateway is not an OCSS receiver. We're honest about which institutional duties are specified in the open standard versus shipped today.
Regulators
Every enforcement decision leaves a replayable receipt — verify what was decided, under which rule, without us exporting a single user's data. The point of an open standard is that you don't have to take one vendor's word for it.
Parents
You set the rule once; it should hold everywhere your kid goes — not just inside one app. Phosra is the conformant router that carries your choice across surfaces, instead of asking you to manage a different toggle on every device.
We don't own the standard. That's the point.
Whichever door you pick, you're building on an open standard — so you're never locked to one vendor, and a parent's choice still holds even if Phosra isn't in the loop. Phosra implements OCSS and runs one accredited network on it; it doesn't own it. The canonical spec lives at openchildsafety.com, not here.
The governance details — verifiable succession, a ≥3-router federation, and a conformance suite that rates a Phosra-only world RED — are on the trust page for whoever wants them.
Conform in a few API calls — through whichever door fits.
The two front doors are live today. Start with the parental-control integration if you own the parent relationship, or the developer door if you're wiring age-appropriate access into your own app.