> ## Documentation Index > Fetch the complete documentation index at: https://docs.peachjam.dev/llms.txt > Use this file to discover all available pages before exploring further. # Weekly usage limits > Understand the shared weekly Builder allowance, usage history, and reset time. # Weekly usage limits > Understand the shared weekly Builder allowance, usage history, and reset time. On Free, each account has one weekly Builder allowance across its Free workspaces. A collaborator uses their own account allowance. On a paid plan, all projects and members in the workspace share the workspace allowance. Open **Settings → Plans & usage** to see: - the current workspace plan - the percentage of weekly usage left - the next Monday 00:00 UTC reset time - a graph of the last 30 days - usage grouped by project. Choose **More usage details** to open the full graph and project table. The detailed screen supports 30 days, 90 days, and a custom range of no more than 90 days. For a Free workspace, this report follows the account across its Free workspaces. For a paid workspace, it follows the selected workspace. The usage bar is the canonical workspace usage indicator. It fills according to the percentage of weekly usage that remains. Usage is a PeachJam service measurement. It does not represent money or an AI provider's cost. Work that is in flight can reserve usage until it finishes. This prevents concurrent builds from exceeding the account or workspace limit. ## Near or at the limit PeachJam shows a warning when 20% remains. At 0%, PeachJam stops before it sends another billable builder operation to the model provider. Existing project files and the last working preview stay available. For a Free workspace, an owner or admin can open **Settings → Plans & usage** to select a paid plan. Other members can see usage but cannot change billing. Paid-workspace plan changes follow the availability rules below. ## Subscription billing Paid plans renew monthly through Paddle. Weekly builder usage still resets each Monday. A checkout return stays pending until the PeachJam API confirms the Paddle transaction and applies the workspace plan. When paid-to-paid plan changes are enabled for the deployment, an upgrade increases the weekly limit after Paddle confirms the completed change. PeachJam keeps the usage that the workspace already consumed in the current week. A downgrade is scheduled for the end of the current paid period. An owner or admin can cancel that scheduled downgrade before the boundary. ## Cloud + AI usage Cloud runtime and PeachJam AI requests from generated apps share a separate Cloud + AI allowance. They do not increase or reduce the weekly Builder limit. Every workspace includes a free monthly Cloud + AI allowance. The allowance resets on the first day of each month at 00:00 UTC. The optional $20 monthly workspace add-on raises that allowance. PeachJam stops new Cloud and AI runtime work at the limit and does not charge an automatic overage. The usage page shows a second progress bar for Cloud + AI. It reports the percentage remaining and the monthly reset date.