OSS-first docs
These docs teach the open system first: contracts, generated surfaces, runtimes, governance, and incremental adoption. Studio shows up as the operating layer on top, not as the source of truth.
Domain docs
BillingOS
Plans, subscriptions, invoices, payments, entitlements, and financial evidence across web and mobile.
Source packages
Start with packages/modules/billing-os, then use the spec and runtime packages as compatibility boundaries.
- packages/libs/billing-spec
- packages/libs/billing-runtime
- packages/libs/crypto-payments-spec
Platform stance
Define the domain once. Render web and mobile with platform-native shells after contract, role, tenant, and policy resolution.
Canonical surfaces
- Plan and entitlement contracts
- Checkout and invoice workflows
- Payment-provider bindings
- Mobile-safe billing state views
Implementation notes
- Keep provider redirects and native purchase flows behind explicit integration boundaries.
- Treat mobile as a first-class shell with compact state, resumable payment handoffs, and offline-safe invoice evidence.
BillingOS is web and mobile compatible
Use the same billing contracts for browser checkout, mobile plan management, invoices, entitlements, and payment evidence. Mobile hosts should keep handoffs resumable, avoid hiding payment state behind provider redirects, and expose compact entitlement state for offline-sensitive screens.
Open the mobile guide
AuthOS
Implement identity, roles, permissions, sessions, and tenant-safe access decisions as a reusable domain.
BillingOS mobile implementation
Project BillingOS into mobile apps with compact billing state, resumable payment handoffs, and provider evidence boundaries.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.