Plans and limits
What each account plan allows, and what happens when a limit is reached.
Every account is on a plan. Plans decide how many machines and projects you may keep, and how long the audit log is retained. There is no self-serve billing yet: the free plan is the default for everyone.
Free
| Live machines | Projects | Audit retention | |
|---|---|---|---|
free | 10 | 25 | 90 days |
The free caps are deliberately generous: they are there so the enforcement path is real, not to constrain ordinary personal use. They will tighten when billing lands.
Pro - coming soon
A paid plan with higher limits is on the way. Nothing is charged today, and there is no self-serve upgrade yet. When it ships, this page will list what it includes.
What counts
Machines count only while they are live. Revoking a machine from the dashboard frees its slot immediately; the row stays for the audit trail, but it no longer consumes the plan. Deleting a revoked machine is permanent and also frees nothing extra, because the slot was already free.
Projects count every project on the account. Re-registering a project that already exists under the same slug (what exeora connect does on a machine that is already known) does not consume a new slot.
When a limit is hit
Registering one machine or project too many returns a clear error from the CLI and a 403 with error: "plan_limit" from the API. The dashboard Settings page shows the current plan and how much of each cap is in use.
Usage
Tool calls are rolled up once a night into a per-day counter that survives the audit-log prune. Settings shows the total for the current UTC month. The rollup is metering, not a billable meter: nothing is charged against it today.