Get started

Set up your workspace

Create a workspace, choose a connection, and give your users their setup instructions.

Open sov.solibra.ai/app. Anyone can create a workspace with an email and password. Existing admins sign in at the same address. Sovereign opens the right workspace automatically.

Choose what to connect

Open Connect and select:

  • Claude Code Terminal or Claude Code Desktop: use existing Claude logins or a company API account.
  • Codex: connect an OpenAI, OpenRouter, Azure, or Bedrock account that supports OpenAI Responses.
  • OpenRouter, OpenAI, or Anthropic: bring your provider API key and generate application setup instructions.
  • Cloud account: connect Amazon Bedrock, Azure AI Foundry, or Google Vertex AI with the account's region, deployment, or service-account details.

Each path shows the fields and instructions for that connection. You can use the dashboard before connecting a tool, and add more connections later.

Set up your users

For Claude subscription users, copy the workspace's install command. Members run it once on their Mac and keep their normal Claude login. Their verified Claude identity links their requests to your workspace.

For company API accounts, connect the provider once. Choose a supported model, enter a user or application name, and press Create user setup. Share the generated instructions with that user. Repeat for each user so activity stays attributable. Provider keys stay on the server; users receive separate gateway credentials.

Codex setup includes an installer for Terminal and Desktop, plus a manual configuration. Claude Desktop with a company API account uses its supported Third-Party Inference configuration. SDK paths provide runnable Python examples with your workspace's address.

View and manage activity

Open Sessions to see requests, models, routing status, usage, and timing. Workspace lists Claude members and admins. You can add or replace admins without changing member setup, and remove or restore member access.

Workspace data remains separate. Backend routing approvals do not restrict sign-up or dashboard features. When model selection is inactive, the gateway keeps the requested model and records the request.