Environments & Configuration

Keep consumer lanes independent from OpenRTC platform internals

Public applications use a published OpenRTC package and the supported managed platform through an app-specific public API key.

VITE_OPENRTC_API_KEY=pk_test_replace_me

const rtc = OpenRTC({ apiKey: import.meta.env.VITE_OPENRTC_API_KEY });

Your development, staging, and production apps should use separate registered OpenRTC identities. A consumer app lane does not select a private platform lane or SDK source automatically.

Standard application configuration contains no OpenRTC provider project IDs, database URLs, storage buckets, public app tags, or gateway endpoints. Service routing and platform identity derive from the API key.

Test-only endpoint overrides are available from openrtc/testing. They are for OpenRTC's own emulator and internal staging matrices, not normal consumer setup.