Usage and Limits
Three things are metered, and all three are counted against the organization that owns the resource — never against the person who happened to click.
| Meter | What it counts | When it resets |
|---|---|---|
| Storage | Data held by this organization's tables | Never — it is a running total |
| Egress | Data leaving Mycorr | Every billing month |
| MCP tool calls | Tool calls an AI assistant made against this organization's data | Every billing month |
All three are on the Usage section of Plan & usage, each with a bar, a percentage and the ceiling it is measured against. The section header carries the reset date for the two monthly allowances, and a Refresh button — nothing on this page polls, so a number you are watching climb needs a nudge.
Storage
Everything your organization's tables hold. It goes up when data is added and down when it is deleted.
A table imported from another organization counts against its owner, not you. Importing is a view onto someone else's table; the bytes stay theirs. The same is true in reverse — publishing a table to the public catalog leaves the bytes billed to you.
Attachments count too. A file uploaded onto a row is stored against the organization that owns the table it landed on.
When storage is full, uploads and edits are refused until space is freed. Waiting does not help: this is the one meter that never resets. To free space, delete data, or buy more — on Pro, each seat carries 20 GB.
Enforcement always asks the organization that owns the resource, never the person writing. So an editor whose own personal organization is full can still write into a company organization that has room.
Egress
Data leaving Mycorr: exports, downloads, the API, and what AI tool calls return.
Reading inside the app is free. Scrolling a table, filtering it, opening a model — none of that is egress. What counts is data crossing out of Mycorr, to you or to something you have pointed at it.
Which organization pays is the organization you are acting in when you pull the data. If you export a table from inside a company organization, that organization pays. If someone outside it exports a table you shared with them, their organization pays, not yours — so sharing a table never puts your allowance at the mercy of the people you shared it with.
Enforcement is strict in two ways, and both exist so you never get a file you cannot trust:
- A download whose size is known in advance is refused whole if it would not fit. You do not get a partial file.
- A stream is cut the moment it crosses the ceiling, and the result is an error rather than a short file — so a truncated export can never be mistaken for a complete one.
When the allowance is spent, exports and API reads are refused until the reset date shown on the row.
MCP tool calls
Every tool call an AI assistant makes against this organization's data, through the MCP server.
The count is a rate governor rather than the cost — what those calls return is already charged as egress. It exists to stop a runaway agent loop eating your allowance.
A failed tool call still consumes a call but is charged no egress. The error is our answer, not your data. That is deliberate: refunding failed calls would make a malformed retry loop free.
When the billing month starts
Egress and tool calls reset on your organization's billing anniversary, not on the first of the calendar month. An organization whose cycle starts on the 14th resets on the 14th.
Short months are handled by clamping rather than drifting: an anchor on the 31st runs 31 Jan → 28 Feb → 31 Mar → 30 Apr, and returns to the 31st rather than ratcheting down for good.
The reset date does not move when you add seats, and it does not move when the plan changes.
On the panel, Since and Resets are two different clocks and will not always agree. Since is when the current plan period opened; Resets is the next billing anniversary. They coincide for a new organization and part company the first time a plan changes. That is the intended reading: the plan changed, the billing cycle did not.
Hitting a limit
A spent allowance stops the whole organization doing the thing, and every member is told — not just the owners. A banner appears across the top of the app naming which limit was reached, when it comes back, and who can act on it:
Limits reached: Egress. Egress resets on 14 October. An owner can move to a larger plan.
Owners see "See Plan & usage in organization settings" instead, because they can do something about it. Admins see the meters on Plan & usage too, but buying a plan is an owner's.
Below 100%, personal organizations show a small meter at the foot of the sidebar once you pass 80%. Company organizations do not — their usage lives on the Plan & usage page, where the people who can act on it are.
What a spent allowance does not stop
Storage and egress limits bound what an organization can take on and pull out. They never lock you out of what you already have:
- Reading inside the app keeps working on every meter.
- A full storage meter refuses new data, not access to old data.
The one thing that can make an organization read-only is an unpaid card, not a spent meter — and even then, reading and exporting keep working. See when a payment fails.