Devices
Connect the currently online devices owned by one authenticated principal
Device meshes are for products such as Plutonium where one signed-in user owns several installations.
const devices = await rtc.devices.start({
auth,
autoConnect: 'online',
});
const stop = devices.watch((event) => render(event));
const snapshot = await devices.listWithStatus();
OpenRTC preserves the durable device roster, but only live gateway presence makes an installation online. The SDK does not dial persisted offline devices merely because they remain known.
Each install owns an Ed25519 key. Browser keys are non-extractable WebCrypto keys when supported; native keys are held by the host secure-storage integration. Enrollment binds that key to the app-scoped principal and returns a renewable device certificate.
Identity or grant refresh for the same scope occurs in place. Presence is event-driven by socket connect, meaningful state changes, disconnect, or server expiry—there is no application heartbeat loop.
stop();
await devices.close();
Your product owns its device-count policy. Under unified terms, offline inventory rows are not concurrent hosted clients or a separately billed device allowance. One active SDK root counts once across its user, room, space and ticket avenues; separate roots still count separately. Direct peer payloads do not consume hosted message units.
The owned-device roster is bounded at 500 distinct devices per app-scoped principal. This is an inventory and protocol safety bound, not a promise of 500 simultaneous physical connections. Signed grants and connection policy may impose lower bounds. Known devices remain listable as presence becomes idle or offline until explicit removal or the applicable offline-retention horizon. Closing a live handle does not revoke the enrollment. Inventory queries, enrollment and revocation remain authenticated, bounded control operations.