Your account and plan.

The plans

Team is the entry plan. Every plan starts with the same short application: see getting access. Enterprise is described in more detail on the trust page, because its whole point is where the data lives.

Seats

A seat is a person, never an agent: the crew does not consume seats. Your admin hands out seats from the Users area, and each seat carries a role that decides what its holder may do. When somebody leaves, revoking them frees the seat immediately for someone else, and everything they approved stays in the record under their name. Trying to add a person beyond your plan's seats is refused with a clear message before anything changes; the ways out are removing a seat you no longer need, or moving up a plan.

Agents at once

Your plan sets how many agents can be working at the same time. It is the only number that changes how the cockpit feels hour to hour, so it is worth understanding properly.

It does not limit how many missions you run, how many agents your crew has, or how much work you get through in a day. When every lane is busy, the next task waits in the queue and starts the moment one frees up. Nothing fails and nothing is lost; the mission simply takes longer.

The limit is there because an agent at work is a real process on a real machine, checking out your repositories and running your tests. Each lane is roughly half a CPU core and a gigabyte of memory, which is why raising it means buying the hardware to run it.

Changing it

Any admin can change the number in Settings, then Orchestration, at any time, up to your plan's ceiling. The change takes effect on the next task to start; work already running is never interrupted. To go above the ceiling you have three routes:

• Add lanes to your current plan, at $45 per lane per month, each bringing the half core and gigabyte it needs.
• Move up a plan, which is usually the better value once you want more than two extra lanes.
• Take a dedicated server, where you set the number yourself and the only ceiling is the size of the machine.

Add ons appear on your next monthly invoice and can be removed at the end of any month. See the add ons table for every option and its price.

Where your cockpit runs

Every customer runs in their own container, with its own memory, workspace and keys. Nothing of yours shares a process with anything of anyone else's, which is the reason the isolation is worth the hardware it costs.

You choose a region at onboarding, from EU West in Paris, EU Central in Frankfurt, the UK in London, or North America in Virginia. Your container and its backups stay in that region. Moving an existing cockpit to another region is a scheduled migration, quoted per case, and we tell you before any data moves.

On a dedicated server the whole machine is reserved for you in the region you name, and you may run as many projects on it as fit. On Enterprise, Carth is installed inside your own infrastructure against your own model provider, so we hold nothing: your code and your files stay on your machines, and the only thing that leaves is what a mission sends to the model provider you chose, on your own contract with them. The trust page goes through that in detail.

Renewal, and what suspension looks like

Your account is always in one of three states, and each is deliberately undramatic:

1. Active. The normal state. The cockpit says nothing about the licence at all, because silence is the correct interface for a healthy account.
2. Renewal due. When the term has ended, a short grace window opens, five days unless agreed otherwise. Everyone keeps working exactly as before; the only change is a dismissible banner counting the days left, with one renewal link.
3. Suspended. When the grace window closes without a renewal, the cockpit locks. People who are not admins see the sign-in screen in its suspended form, with no way in. The admin can still sign in and gets one full-screen notice with the plan, the seat usage and the expiry date, so the one person who can fix it is the one who is told. Nothing is deleted: your data, your missions and your history are all still there, and renewing brings everything back as it was.

Storage limits, in plain words

Your workspace stores your connected repositories, the crew's mission records and evidence, and your knowledge base. Each plan carries three allowances: the whole workspace, each single repository, and the knowledge base.

When something would not fit, connecting a repository, uploading knowledge, the action is refused up front with the actual numbers: what you are using, what the plan allows. Nothing is half done, and nothing you already have is touched. The two real ways out are freeing space or moving up a plan, and the message says so. A storage meter in Settings, under Local services, shows one bar per allowance so you are never surprised.