User guide
Usage limits & fair use
Backendup is free to use, and free things still need rules - so the rules are short, published, and every number on this page is read live from the server that enforces it. When a limit changes, this page changes with it.
Signed in? This table answers with your account’s row - the best tree you own. Every tree still enforces its own plan’s row, but the number on this page and the gate that applies it come from the same resolve call, for every plan. Visitors and free accounts read the free row, which is every number this page has ever shown.
What is never limited
Work items and history. No cap on how many stories, tasks or messages an organization holds, and no expiry of old ones. A tracker with an item count stops being a tracker - database rows are cheap, and yours should stay forever. (Some tools cap issues; that is a pricing choice we have chosen not to make.) Discussion history is kept for the life of the account, not 90 days.
The numbers
| What | Limit | Counted per | When it is reached |
|---|---|---|---|
| Attachment storage | 5.0 GB | organization tree (sub-organizations share the root’s budget) | New uploads pause with a clear message. Existing files stay readable and downloadable. |
| One attachment file | 25 MB | any single upload, anywhere | The file is refused; smaller files, text, and downloads are unaffected. |
| Members | 15 | organization tree (a person counts once across all its teams; a pending invitation reserves a seat, so accepting never fails) | Inviting and assigning pause until someone is deactivated anywhere in the tree. Nothing is removed. |
| Live projects | 50 | per organization (completed and archived projects free their slot) | Creation pauses; existing projects keep everything. This is an abuse rail, not a pricing lever. |
| Root organizations | 3 | per account (creation gate only - orgs you already have are untouched) | Creation pauses; deactivating an old root frees a slot. |
| Chat messages & comments | 50 / minute | per person, shared across chat, discussions and forwards | A brief cooldown, then the window resets. Reads, reactions and files-to-download are unaffected - and this flood guard is the same on every plan by design. |
| Notification emails | 200 / day | organization tree (sub-organizations share the root’s budget) | Email pauses until local midnight. The in-app notification center keeps every event - a pause never loses anything. |
| Invitations | 50 / day | organization tree (sub-organizations share the root’s budget) | New invitations pause until local midnight; existing members and pending invitations are untouched. |
| AI assistant messages | 50 / day | per person, counted against the day | New questions pause until local midnight; every conversation and answer already written stays readable, and a refused question is not even saved. |
| Assistant questions (preview) | 50 / day, 1,000 / month | organization tree (sub-organizations share the root’s budget) | New questions pause until the period resumes; threads, answers and citations stay readable, and a refused question is never even saved. |
| API requests | 60 / minute | per integration token | A 429 with a Retry-After header. Comfortably above any honest agent; sized to blunt floods. |
| API requests, all tokens together | off | organization tree (sub-organizations share the root’s budget) | A fleet of tokens shares this aggregate window - the pool buys fleet throughput, never a bigger flood for one caller. |
One thing this table cannot say, because it is deliberately not a limit: confirming or rejecting an AI assistant draft never spends a message slot. A decision contacts no model - the assistant rows above count questions only.
Why a tree, not an organization
Every resource budget - storage, email, invitations and membership seats - belongs to the organization tree: a sub-organization shares its root’s numbers, because a hundred-person company splitting into teams should not multiply what one customer can spend. Seats count people, not roster rows, so one person in the root and in three teams still holds a single seat; each team keeps its own roster and its own members page.
The future, honestly
If Backendup ever sells a bigger plan, it will raise capacity - people, storage, throughput - the numbers that map to real cost. It will never put a price on your own content. The numbers on this page may change; the promise will not: reaching a limit pauses new things, and deleting your data is never one of them.