Plans and limits

Every account is on a plan. Plans decide how many machines and projects you may keep, how many Exeora Cloud instances you may run, and how long the audit log remains visible. There is no self-serve billing yet: the free plan is the default for everyone.

Free#

The free machine and project 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.

Activity uses a rolling 24-hour window, enforced by the server. Physical cleanup is asynchronous: archive maintenance, recovery records and snapshot expiration have separate lifetimes, so the visibility window is not a promise that every stored copy disappears at exactly 24 hours.

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.

Cloud instances have a cap of their own. It counts every instance Exeora runs for the account, in whatever state it is in: one per workspace on Exeora Cloud, and one for the project root of a project that was created there or has Cloud as its default location. They do not count as live machines, so an instance never takes a slot from a laptop. Removing a workspace frees its slot once the instance is gone. An instance that is asleep runs nothing and still takes one slot. Destroying it frees that slot, and a project root in state no instance takes none until the next call to it makes the instance. Cloud itself is enabled per account by an administrator while there is no billing.

Projects count once, however many locations they live in. A project is a repository, so a second machine that joins it, or Exeora Cloud added as a location, consumes no new slot. Neither does registering again a project that machine already holds. A project that lives nowhere is still a project and still counts, until it is removed.

When a limit is hit#

Registering one machine or project too many, or asking for one instance too many, returns a clear error from the CLI and a 403 with error: "plan_limit" from the API, which names the limit that was reached. 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.