Disc Space Quotas in Probo.CI

We enforce disc space quotas in two separate but related systems: build environments, and uploaded assets. Understanding how each works helps you manage your storage usage and avoid unexpected build or upload failures.

1. Build Disc Space Quotas

   Each organization’s build disc usage is governed by its subscription plan. The quota is set in gigabytes (GB) and applies to the total disc space consumed by all active build environments across all repositories within your organization.

   1.1 How the Limit Is Set. Your organization’s disc space quota comes from your subscription plan.

   1.2 How Usage Is Tracked. Disc usage is tracked at the organization level by aggregating the real storage consumed across all active builds. This total is compared against your subscription quota whenever a build completes. Each build’s storage only by the contents of the build and not the overhead of the underlying system.

   1.3 Automatic Quota Enforcement. When a build reaches a ready state, the Reaper checks your organization’s current disc usage against its quota. If usage exceeds the limit, the Reaper automatically selects and deletes older builds until usage falls back within the allowed limit. This process is called reaping.

   Builds are selected for reaping in this order:

   • Older builds are removed before newer ones
   • Builds marked as pinned are exempt from reaping entirely

   When a build is reaped due, its container environment is destroyed and the build record is removed.

   1.4 Pinning Builds. If you have a build environment you need to preserve regardless of disc pressure, you can pin it. Pinned builds are never selected for reaping. Use this sparingly, as pinned builds still count toward your total disc usage.

   1.5 Increasing Your Build Quota. Your disc space quota is determined by your subscription plan. If your organization regularly hits its limit, upgrading your plan will increase the amount of storage available for active build environments. Visit our pricing page to compare plans or contact us at hello@probo.ci.

2. Asset Disc Space Quotas

   The asset receiver manages files you upload to Probo.CI for use in your builds - such as database dumps, media archives, or other large files. These assets are stored separately from build environments and are subject to their own quota system.

   2.1 Per-Bucket Limit. Assets are organized into buckets, typically one per project. Each bucket has a hard storage limit of 10 GB. This limit applies to the total compressed size of all assets stored in the bucket.

   2.2 What Happens When the Limit Is Reached. If an upload would cause a bucket to exceed 10 GB, the upload is rejected. No automatic deletion occurs - existing assets are not removed to make room. You must manually delete assets you no longer need before new uploads will be accepted. A usage bar is visible on all project pages to indicate how much usage you are using in your project.

   2.3 Asset Cleanup. When you upload an asset with the same filename as an existing asset in the same bucket, the previous version is automatically replaced. This helps manage storage by ensuring you are not accumulating multiple versions of the same file unintentionally.

   2.4 Subscription Requirement. The asset receiver also verifies that your organization has an active subscription before accepting uploads. If your subscription is inactive or expired, uploads will be rejected regardless of available storage.

   2.5 Managing Your Assets. To free up space in a bucket, delete assets you no longer need through the portal or API. Once storage drops below the 10 GB limit, new uploads will be accepted again.

3. Summary of Quota Limits

   System	Quota Scope	Default Limit	Enforcement
   Build environments	Per organization	Plan Based	Automatic - older builds are reaped
   Asset receiver	Per bucket	10 GB (fixed)	Passive - uploads rejected at limit

4. Questions

   If you have questions about your organization’s disc quotas or need help managing storage, please reach out to us at hello@probo.ci.