Capacity reference
Plans, Limits, and Quotas
Vibecodr limits are split by resource lane so users can see what is constrained and choose the right recovery action.
Plan and quota reference for Vibecodr creator workflows.
Implementation focus
Use this when an operation fails because capacity, quota, upload shape, or plan eligibility does not match the workload.
Expected outcomes
- Identify which resource lane hit a limit.
- Choose cleanup, project-shape changes, period reset, or plan change intentionally.
- Avoid unsafe workarounds such as hiding data in public metadata.
- Understand how vanity, Pulse State, storage quota, and imports differ.
Limits are separate on purpose
Vibecodr plan limits are shaped around different resources instead of one vague bucket. Storage quota, project ZIP size, file count, build output, Pulse runs, Pulse State operations, secrets, connections, and vanity domains can each fail for different reasons and recover through different actions.
A plan can have room in one lane while another lane is full. For example, a creator might have storage left but hit a Pulse State monthly quota, or have Pulse runs left but exceed a ZIP size limit during import.
- Storage quota covers account-owned stored material, not every edge request.
- Import limits protect archive size, file count, and build cost before work continues.
- Pulse State limits count operation-memory use, not general app database rows.
- Vanity limits count claimed `vxbe.space` names.
Use the right recovery action
Quota errors should tell you which lane is constrained. The safe response is to reduce usage in that lane, change the project shape, wait for a period reset when the quota is periodic, or move to a plan that fits the workload.
Do not work around limits by hiding large data in public metadata, bundling credentials into source, or turning repeated operations into unbounded browser retries. Those choices usually create worse reliability and safety problems.
- For storage pressure, use storage cleanup tools and preserve live artifacts before deleting.
- For import pressure, remove unrelated files and build locally only as a shape check.
- For Pulse State pressure, reduce duplicate-protection cardinality and retention where safe.
- For vanity pressure, release unused names before claiming more.
Example and read next
Example: an import fails even though account storage looks available. Check the specific lane: ZIP size, file count, build output, Pulse State operations, secrets, connections, or vanity limits may be the constraint.
Use these related pages when you need the next layer of guidance. They point to the most likely follow-up tasks, not every page that happens to touch the same system.
- Read next: /pricing
- Read next: Storage Lanes
- Read next: Import a Project
- Read next: Pulse State