Getting started with Chrovia
Start with Persona Hub profiles or integrate Chrovia SDK, then find the guides for credentials, automation, licensing, and browser capabilities.
Choose the path that matches what you want to do. Persona Hub is the desktop app for creating and launching browser profiles. Chrovia SDK is for developers integrating the browser runtime into their own applications. You do not need to follow the SDK License and plugin setup steps to use Persona Hub.
Your first Persona Hub profile
- Download and install Persona Hub from the download page, then sign in to the desktop app.
- Create a profile: choose a name and appearance, optionally configure a node, and save the profile. A node is not required; if you configure one, check it before creating the profile.
- Launch the profile browser: open a website and sign in. Launch the same profile again later to continue using its browser data.
Passwords and sign-in verification
These guides describe operations in Persona Hub and its profile browser, not SDK APIs.
- Save or manage website usernames and passwords: Password management
- Scan an authenticator QR code and get rotating verification codes: TOTP
- Register, use, or delete a software passkey for a profile: Passkeys
Automation and AI clients
- Connect browser automation tools to a running Persona Hub profile: Enable CDP
- Let an AI client work with Persona Hub profiles through its local MCP service: Connect MCP
- Integrate automation directly with the SDK instead: SDK automation
Partner rewards
- Earn Persona Hub credit through Bright Data referrals and redeem it for Pro: Partner rewards
Your first SDK instance
- Need a browser and a trial License? Follow Trial License installation.
- Ready to launch an isolated browser instance and call an API from a plugin? Follow the SDK developer quickstart.
- Choosing features for your application? Use the SDK documentation and capability index.
Licenses and online authorization
- Understand what a License grants, where to install it, and how to replace it: License lifecycle
- Understand online leases, renewal, and authorization failures: Leases
- Purchase a commercial License or understand instance limits, hours, and renewals: Commercial License billing
Configuration and built-in plugins
- Prepare browser settings or read and write application preferences: Extended Preferences
- Use a License that requires signed preferences: Signed Extended Preferences
- Package plugins, default files, and release metadata beside the browser: Provision directory
- Install, debug, update, or remove a built-in extension: Built-in plugins
- Find an API and the JavaScript context where it is available: JavaScript API overview
Browser capabilities
A License grants capabilities; configuration and API calls determine how your application uses them. Start with the relevant guide rather than copying every available setting into one instance.
- Adjust browser identity and network settings: Fingerprint override, System proxy override
- Filter requests or change navigation: Declarative Net Request, Network interception, Navigation redirect
- Supply or manage sign-in credentials: Injected credentials, Saved-password store, Software authenticator
- Coordinate startup and browser lifetime: Messaging, Supervisor process, Process management
- Customize browser presentation: Instance appearance, Instance metadata, Native dialogs
- Restrict developer tools or password reveal: Disable DevTools, Password reveal block
- Understand API access outside the default plugin context: Unrestricted API
The capability index lists every entitlement and its configuration or API reference.