Introduction
Choose backend API integration or hosted OAuth and OpenID Connect for your application.
Virtneu Auth provides two integration paths for the same App user directory. Your backend can use the /v1 API and @virtneu/auth SDK to build registration, login, and session flows with your own UI. It authenticates with a scoped service credential that stays on the backend.
For hosted sign-in through the system browser, Web and native applications can use OAuth and OpenID Connect with Authorization Code and PKCE. Native applications use a public client without a client secret. Your application owns its business permissions in either integration.
Start here
| I want to… | Go to |
|---|---|
| Make my first authenticated request | Quickstart |
| Implement registration, login, and logout | Authentication and sessions |
| Use hosted sign-in for Web, macOS, or Windows | OAuth and OpenID Connect |
| Keep a passkey ceremony inside my page or native app (SDK 0.7.0) | Embedded passkeys |
| Manage passkeys and factors from my application's settings | Account security integration |
| Understand login prompts, the RP domain, or cross-device QR | Hosted prompts and device picker |
| Keep a backend-managed browser session across visits | Browser session renewal |
| Install the TypeScript SDK | TypeScript SDK |
| Call the API directly | HTTP API reference |
| Query users and validate business credential access | Users and business credentials |
| Store app settings and user attributes | Metadata |
| Connect an AI coding tool to Studio | Management MCP |
| Diagnose errors and retry safely | Troubleshooting |
Apps and environments
Create an app in Studio. Each app has isolated test and production environments with their own users, sessions, databases, and API keys. Start in test, then issue a separate production key when your integration is ready. The service currently runs in the Global region.