Developer Portal
Create apps, configure trust, and manage monthly capacity
The OpenRTC Developer Portal manages application identities, public API keys, capability manifests, provider registration, monthly subscriptions, and capacity usage.
Every application uses OpenRTC. There is no per-app rollout switch and the portal does not create or update OpenRTC 1.x configuration fields.
Live coordination
Open Billing to compare the live plans, purchase an available plan, and manage its additional-spending cap. The live account view also manages app public keys and automation tokens. Start with Live coordination for this API. The app-manifest setup below applies to the separate room/device APIs.
Minimum prototype setup
- Create an application.
- Copy its public API key.
- Enable capability spaces or ephemeral rooms.
- Register the browser origins that may request capabilities.
This path creates no product user account or Firebase Auth principal.
Existing room and device app settings
The following app-manifest and attestation settings apply to the separate room/device APIs. Live coordination uses your app backend to sign scoped connection credentials; see Live coordination.
Production identity
Register the HTTPS issuer, audience, JWKS, and signing algorithms for assertions produced by your identity backend. OpenRTC validates the assertion and preserves a stable app-scoped principal without taking ownership of your login UX or product authorization.
Managed attestation stores public provider identifiers and policy in the app manifest. Secrets and private keys remain server-side references; they are never stored in the developer-app document or shipped to the SDK.
The portal can register Firebase App IDs, Apple team/bundle/environment/build policy, and Play package/signing/version policy together for a cross-platform app. Apple DeviceCheck is shown separately as a reduced-trust fallback and accepts only a Secret Manager resource name containing the Apple team ID, key ID, and ES256 private key. OpenRTC never accepts that private key in a public identifier field.
Attestation can be disabled, optional on supported platforms, or required. Required is intentionally strict: an unsupported desktop cannot enroll. Evidence is requested only for enrollment, key rotation, recovery, or explicit risk escalation—not for every socket or grant refresh.
Capability manifest
The manifest controls:
- enabled avenues: devices, spaces, rooms, and tickets;
- capability and authenticated access modes;
- allowed origins and registered trust providers;
- external Iroh relay fallback, with an app-wide opt-out;
- durable membership, managed attestation, and BLE opt-ins;
- operator-reviewed adaptive-room capabilities, separate from membership allowances;
- technical payload and concurrency safeguards, separate from your purchased capacity allowances.
An advanced feature is available only when enabled in the manifest and requested by runtime code.
Custom capability routing
Use Security → Advanced routing to choose individual access modes and scopes instead of replacing the entire configuration with a starter profile. Changes preserve provider registration, origins, and unrelated capability settings. Durable membership still requires authenticated rooms.
The owner settings callable and PATCH /v2/developer/apps/{appTag} accept the
same partial capabilityRouting object:
{
"capabilityRouting": {
"accessModes": { "capability": true },
"avenues": { "rooms": false, "tickets": true }
}
}
Omitted flags retain their current values. Only the named boolean routing flags
are accepted; other manifest fields use their own settings. Do not combine this
object with starterProfile. Normal owner authentication, app-write scope and
idempotency requirements still apply. A concurrent app update is rejected: reload
and review the latest settings before submitting again.
Billing and additional spending
The live offer includes Hobby ($5/month, noncommercial), Builder ($29), Pro ($79), and Scale ($299). See Pricing for the included connections, coordination message units and tier-specific overage rates.
Billing shows your purchased plan and its accepted terms. Hobby has hard limits. Commercial plans start with overages off and a $0 additional-spending cap. Enable overages and choose one cap for combined connection and coordination-message charges; the subscription and applicable taxes are separate. A lower cap does not remove charges already incurred. If usage cannot be admitted within the allowance and cap, further chargeable activity is denied.
Live apps share one account allowance. Manage your public app signing keys, personal access tokens and spending settings in the live account view. Keep private app keys on your backend. Existing room/device subscriptions remain in the separate capacity view with their accepted terms; selecting a live plan does not automatically migrate them or prorate an in-cycle upgrade.
Relay availability
Managed TURN and MoQ relay services are unavailable in this release. No relay allowances or relay overages are sold. Relay plans will be introduced separately. The Security tab's external Iroh fallback setting does not enable managed TURN or MoQ. Direct peer traffic does not incur separate OpenRTC byte charges.
Existing capacity usage
The usage dashboard reports app capacity rather than event-credit balances. Monthly active users count once per app and billing term. Rooms and spaces use their peak simultaneous existing counts; room and space devices use peak concurrent device counts within each resource. Registered user devices include retained offline devices until removed. Reconnects do not create a new device identity or a separate billable connection event.
Account, app, and per-user event-credit cap controls are not part of customer capacity plans. Use the Billing page's overage preference and spending ceiling.
Quickstarts are generated for an API-key prototype, authenticated devices, a collaborative room, a production backend assertion, and managed mobile attestation.
Offline edge trust is local and does not require a portal capability switch. The portal does not receive device private keys, local discovery advertisements, or direct LAN payload. Online use remains subject to the app's purchased capacity allowances.