Live and Test environments: differences, creating and switching
Each project has a Live environment for your public service and a Test environment for development and testing.
Live vs. Test
| Live | Test | |
|---|---|---|
| Use | Your public service | Development and testing (localhost, etc.) |
| RP ID example | login.example.com | localhost |
| API keys | Start with sk_live_ | Start with sk_test_ |
| Billing (MAU) | Billed | Not billed |
RP ID, origins, API keys, users and the audit log are separate for each environment. An API key does not work in another environment.
Switch environments
- Click the switcher at the top left.
- Under "Environment", click Live or Test.
The same kind of screen (for example, Users) stays open after you switch.
Create the Live environment
- Open the project and choose Live in the switcher.
- In "RP ID", enter the domain of your login page or its parent domain (for example,
login.example.com). - In "Origins", enter the origins that accept passkey registration and login. If left empty,
https://{RP ID}is used. - Click "Create Live environment".
- Admins and Owners can create environments. Other roles see a message asking them to contact an Owner or Admin.
- For a project without a Test environment, choose Test and follow the same steps.
- For how to choose the RP ID and origins, see Environment settings.
Environment overview
"Overview" in the menu shows the following for the environment:
- Users, users with a passkey, MAU this month and the login success rate (30 days)
- MAU and passkey registrations (6 months)
- Types of active passkeys (built-in, phone, USB key and so on) and login successes and failures (30 days)
Until the integration is done, "Integration steps" (create an API key → register a passkey → log in with a passkey) appear. Finished steps are marked "Done", and the card disappears when all steps are done.
Related pages
API reference
For the API, browser SDK and MCP, see the API reference. If you have questions, please contact us.