Skip to main content
Phosra operates a hosted OCSS census — an OCSS Trust-Framework-conformant relay that routes signed child-safety rules between parental-controls providers and the apps where children consume content. There are two roles. Every integration is one or both. The two SDKs speak the same OCSS Trust Framework protocol under the hood. All cryptographic signing happens in your process — your private key never leaves your machine. The hosted census persists, distributes, and confirms; your SDK verifies.

Before you write any code

Run the CLI to prove the setup end-to-end against the shared sandbox in under two minutes. No account required.
phosra doctor runs five checks and exits 0 on green:
  1. Census reachable (GET /health — mounted at the ROOT, not under /api/v1)
  2. Trust list verified (Ed25519 root signature against the baked-in root key)
  3. Capabilities doc verified (123-rule self-describing document, WARN if absent)
  4. Spec-version negotiation (client ↔ server OCSS version range agreement)
  5. Signed sandbox round-trip (§8.3.2 consent attestation + §8.3.1 rule write, both 201)
The sandbox wired by phosra init is the production sandbox census (phosra-api-sandbox-production.up.railway.app) — the one canonical partner host, with no new backend, no database, no provisioning. (Phosra runs a separate -staging census for its own pre-release testing; it is not a partner surface — see Environments → the two sandbox hosts.)

SDK availability

All five SDKs (@phosra/link, @phosra/gatekeeper, @phosra/cli, @phosra/sdk, and @openchildsafety/ocss) are published on npm. See the status page for full version info.

Pricing — the §12.3 line

The OCSS standard and both SDKs are MIT-licensed. You can run your own census at zero cost. You pay Phosra only when Phosra operates the census for you.
  • SDK operations (signing, verifying, the local isAllowed decision) — free, always
  • Safety-path operations (enforcement profile reads, enforcement confirmations, proposals) — free, never metered
  • Hosted census operations (consent ingest, grant mint, endpoint binding, rule writes, profile distribution) — metered per distinct linked family
The §12.3 line is the pricing boundary: local crypto and enforcement are free; hosted persistence and distribution are paid.
You pay for the connection, never for keeping a kid safe.
For the full billing model, see Billing.

What is live today


Next

CLI quickstart

phosra initphosra doctor → green signed round-trip in under two minutes

Provider quickstart

@phosra/link — connect a family, ingest consent, write rules

Platform quickstart

@phosra/gatekeeper — receive profiles, decide locally, confirm enforcement

Billing model

Per-family FamilyMeter — what is metered, what is always free