From developer access to product integration
Your backend connects to Cloud with a scoped server key. Your product clients use your backend; the Console has a separate developer identity and API.
Step 1
Sign in with your work email
Enter the one-time code. A new verified email creates a review application automatically; returning developers keep their current account state.
Step 2
Configure your default organization
After approval, BeeOS creates your default organization. Create an App with just a name, then add exact HTTPS origins and redirect URIs in App settings when needed.
Step 3
Create a server key
Give the key a name, then copy it when it appears—the plaintext is never shown again. Store it only in your backend.
Step 4
Connect your product backend
Use the Server API or SDK from your backend. Keep product users, permissions and subscription entitlements in your own application. The server key never enters browser or mobile code.
Your backend
Keeps long-lived credentials private
- Stores the scoped server key
- Owns product user identity, permissions and entitlements
- Calls the Server API and receives lifecycle webhooks
Your app
Connects through your product backend
- Uses your product API and user channels
- Receives purpose-bound connections for supported live sessions
- Keeps viewing and control permissions separate