Skip to content
Hydra

Model accounts

Hydra brings no model access of its own. Every chat, terminal and API call runs on model accounts that your company connects: Claude accounts, and ChatGPT accounts through Codex. This page explains how to connect them, how Hydra spreads the work across them, and when to move to API keys.

Everyone brings their own account

The recommended setup is one account per person. Each person who uses Hydra connects their own Claude or ChatGPT plan, and approves the sign-in on their own phone or laptop.

Hydra then shares the work fairly across every connected account:

  • One busy team does not stall another. When marketing has a heavy afternoon of pictures and designs, operations still gets answers, because each person active right now gets a fair slice of what every account has left.
  • No plan sits idle. A new chat goes to the account with the most room left at that moment, so a plan whose owner is in meetings all day still does useful work.
  • The more people connect, the more room everyone has. Each new account adds to what everyone can use, and nobody has to guess who needs the biggest plan.

Connect an account

Accounts are managed by the owner and admins in System → Provider accounts.

  1. Choose Connect Claude account or Connect Codex account, and give it a name (for example, the person's name).
  2. Hydra shows an address. The person whose plan it is opens it on their own device and approves the sign-in there.
  3. For Claude, paste the code the page shows back into Hydra. For Codex, type the code Hydra shows into the page.
  4. Hydra continues by itself and shows Connected.

The sign-in ends by itself after 10 minutes. If it does not finish, nothing is saved. Hydra keeps a long-lived token for the account in a file only the Hydra service can read, and never shows it again, in any page, log or API.

The account list

Column What it shows
Type A subscription sign-in, or an API key.
Status Connected, needs login, or expired.
Valid until When the stored sign-in ends.
Headroom How much of the account's current usage window is left.
Last used When a chat last ran on it.

When an account's sign-in is refused, or is close to its end date, Hydra marks it needs login, stops sending work to it once it no longer works, and sends the owner and admins an Inbox note. Reconnect runs the same sign-in again.

How the sharing works

System → Accounts shows each account's 5-hour and weekly windows. A conversation stays on the account it started on. Max at once caps how many answers run on one account together; when every account is full, a new turn waits briefly instead of failing.

System → Limits sets each role's share weight, and you can override it for a person. Within each account's window, the people active in it share what is left in proportion to their weight. A person past their share is not refused: they see "You have used your share for now; back at" a time, and continue then. The owner is never held back. Limits can also cap messages or cost per day, by role or by person.

When to move to API keys

Subscription plans are the right way to start: each person's plan, used for their own work. As Hydra grows into a team tool, move the bulk of the work to API keys (an Anthropic key for Claude, an OpenAI key for Codex), which are made for company use and billed by what you use.

Hydra tells you when. Until at least one API-key account exists, the owner and admins see a banner at the top of the app as soon as any one of these is true:

  • more than 9 people are active;
  • Hydra has had other users for more than 3 months;
  • a subscription account is under 10 % of its current window, or someone was held back by their share in the last 7 days.

The banner names which signal fired. To add a key, choose Add API key and paste it once; after that, only its last four characters are shown. Subscription accounts can stay connected beside it.