Plans and limits

Your account's plan limits how many vaults you own. Each vault's tier limits how many people it holds and how much it stores. Nothing is billed yet.

Plans and tiers

	Free (everyone)	Alpha tester (by invitation)
Vaults you own	5	25
People per vault	10	25
Storage per vault	100 MB	1 GB

A vault's tier is Standard unless it has been upgraded. A Standard vault takes its people and storage limits from the plan of the account that created it, whoever else becomes an owner later. A vault can be upgraded on its own: the Pro tier holds 50 people and 5 GB, whatever its account's plan. Upgrades are given by hand during the beta; ask the operator.

Sizes are decimal: 1 MB is 1,000,000 bytes, 1 GB is 1,000 MB.

Where you see them

Account, Plan and usage (/account): your plan, how many vaults you own of how many, and each of your vaults' people and storage. Home shows the plan and the count under Your vaults.
A vault's Settings, Plan and usage: its tier, people and storage, for every member. Owners also see the invites waiting.
Agents: list_vaults notes a vault that is near or over a limit.

What counts

Vaults you own: the vaults you created. Being a member, even an owner, of someone else's vault doesn't count.
People: a vault's members, of every role. When an owner invites someone, invites still waiting count too, so a vault never hands out more links than it has places for.
Storage: the text of every version of every file (history takes space too), every variable's encrypted value, and the encrypted values of imports waiting to be applied. A proposal counts once it is applied. Comments, review notes and the activity log don't count.

At a limit

A request that would pass a limit is refused, and nothing is changed. The message names the vault, the limit, the plan or tier and the usage, for example "Club is at its 10-person limit on the Free plan (8 members and 2 invites waiting): revoke an invite or remove someone first".

Limit	Refused	Make room by
Vaults you own	New vault, and `create_vault` over MCP	deleting a vault you no longer need
People	Invite someone; opening an invite link when the vault is already full	revoking invites, removing members, or members leaving
Storage	saving a file, proposing, approving a proposal, setting a larger variable value, importing a `.env`	erasing files (deleting a file keeps its history, and its size), deleting variables, rejecting imports

A proposal whose text wouldn't fit is refused when it is made, so an agent learns at once. Applying an import adds nothing: its values were counted when it was made.

Removing things always works at a limit: deleting and erasing files, deleting variables, removing members, leaving, rejecting imports and deleting the vault.

Over MCP a refusal reads Limit reached: and the message. The env API answers a push that doesn't fit with status 507 and {"error": "storage_limit"}.

When a plan gets smaller

Nothing is deleted. A vault over a limit becomes read-mostly: everyone keeps reading, deleting and erasing, and nothing that adds storage or people is taken until it is back under. An account with more vaults than its plan allows keeps them all and can't create another until it is under.

See Limits for every other limit.