The $0 isn't a promise — it's clause text. OCSS §12.1 makes the spec royalty-free; §5.4 bars us earning from assessors. We charge only for the router.
No per-seat pricing: agents and the autonomous loop do most of the enforcement, so counting humans is the wrong unit. The free family tier is the floor; developer and enterprise pay for the operation behind it.
Set one rule and have it hold across the surfaces you control. Free, and we intend to keep it that way — a parent should never have to pay to protect their own child.
Drop the hosted conformant router into your stack. Age signal in, signed decision out — metered by the calls and exports your integration actually makes, not by seats.
Everything in Developer, plus the operational commitments a regulated deployment needs: contracted SLOs, named support, the security floor, and adapter work for your surfaces.
Written into OCSS §12.1 + §5.4 — one arrow can take money, the other never can.
Spec, rule registry, and conformance suite are open at openchildsafety.com — Phosra implements OCSS, it doesn't license it.
On the developer and enterprise tiers, the operation is billed by event. Each line below is a thing the router did on your behalf — a decision, an export, a tool call — never a person on your account. Consumption is visible in real time in the dashboard.
Decision receipts are Ed25519-signed and replayable, so an export is evidence a regulator can verify without us shipping a single user's data. Metering the action — not the seat — keeps price aligned with the protection delivered.
Family tier: enforcement runs free, no meters.
An open standard is only worth trusting if the implementer's revenue can't quietly bend it. So we drew the line where it has to be: families pay nothing, the standard and its mark are never for sale, and governance has no paid lane. What's left to charge for is the operation — the hosted router, the API, the SLOs, the adapter work — and we're happy to be measured on how well we run it.
That's the same reason the conformance suite is built to rate a Phosra-only federation RED. A standard captured by its biggest implementer isn't a standard. Pricing is just one more place we make the separation legible — and checkable.
Start a family account at no cost, wire the router into your own app on the usage-based developer tier, or talk to a partner engineer about an enterprise deployment with contracted SLOs. None of it buys a seat at the standard.
The standard we implement — spec, rule registry, conformance suite — lives at openchildsafety.com, not behind this paywall.