Limits and capacity
Oddlynew has product capacity, throughput guardrails, and surface-specific technical limits. This page owns the public status of product capacity and entitlements. Exact mechanics stay with the product surface they constrain.
What is decided
Documents carry no permissions of their own: who can read them is set per organization. They do count toward capacity: every plan has a document limit, and stored documents are billed by the day. The section on documents below says what counts.
Capacity does not determine who can read an organization. Membership and organization visibility determine the audience.
Exact mechanical constraints belong to the surface that enforces them and to the generated runtime declarations.
File capacity is decided and live: it defaults to 250 MiB for a free organization and 100 GiB for an organization funded by a Pro billing account, with no file-count limit; grants or individual overrides can change the storage ceiling, and the baseline content feature adds no file capacity. The Files guide owns the numbers and mechanics.
Documents: what counts, and when to delete
Every document in an organization counts toward its plan's document limit until it is deleted, archived documents included. Documents in the trash, comment threads and earlier versions do not count. Stored documents are also billed by the day on this same count, at the prices on the pricing page. An organization administrator sees the count and the limit on the billing page or through organizations.getCapacity.
Archiving organizes: it takes a document out of default listings and search and keeps it readable, citable and restorable, but it frees no capacity. Use it for finished work whose history still matters, such as decisions, reviews and completed trackers.
Deleting frees capacity. The document moves to the trash, can be restored for 30 days and is then removed for good, as Archive, restore, delete describes. Delete rather than archive high-volume machine records, such as run logs, sync snapshots or generated reports, whose substance already lives in other documents, once losing them after the trash window is acceptable. When unsure, archive.
Files outlive their documents. A file counts toward the organization's file storage until you delete it, even after every document that used it is archived or deleted: Oddlynew never deletes a file on its own. To remove one, confirm with files.getFileMetadata that no document references it, then call files.deleteFile. A deleted document keeps its files referenced until it leaves the trash, so remove the reference first if you want the file gone sooner, as References anchor the file explains.
Limits owned by product surfaces
Run budgets and their failure behavior belong in The run surface. File and document-asset ceilings belong in Files. Comment body, quote, and thread ceilings belong in Comments. Those guides own the current numbers; live server validation inside run remains authoritative for exact enforcement. This page links to them instead of copying every value.
Relationship to pricing
Public plans and prices are published. The plan comparison lives at https://oddlynew.com/pricing, and the per-lane capacity each plan includes lives in Knowledge capacity and plan limits.