
Last Updated: April 3, 2026
We have made some important updates to how Probo.CI manages disc space and asset storage. If your team uploads database dumps or other files to use in your builds, or if you have ever wondered why a build environment disappeared sooner than expected, this post is for you.
Every build environment Probo.CI creates takes up storage. Your organization’s subscription plan includes a storage allowance that covers all of your active build environments across every project. When that allowance is used up, Probo.CI automatically removes older environments to make room for new ones - this is handled by a background process affectionately called the Reaper.
We have improved how the Reaper decides which builds to remove. The rules are now simpler and more predictable:
Older builds are removed first. The Reaper works its way back from the oldest environments until your storage is back within your allowance.
Pinned builds are only touched if your pinned builds take up your entire quots. If there is a build your team needs to keep - a client review, a release candidate, a build you are actively debugging - pin it from the build page in the portal and the Reaper will leave it alone as long as possible.
When builds are reaped. Builds are reaped under three conditions: manually from the portal, when a pull/merge request is merged, and when a pull/merge request is closed. Reaping often happens within a few seconds after one of these actions.
The goal is to make sure your team always has access to what matters most while keeping your storage usage manageable in the background.
When a build is reaped, it is removed from the portal. In this way there is no historical archive of builds. If you need to rebuild a build that has been reaped, you can locate the branch and create a build from that. All the way down to the specific commit on that branch.
Probo.CI lets you upload files to use in your builds - things like database backups, credential files, and media archives. These uploads are stored in a dedicated space for each project called a bucket.
We have introduced a storage limit of 10 GB per project bucket. This limit applies to the total size of all files currently stored for a project.
If your project’s bucket reaches 10 GB, further uploads will be declined until you clear out files you no longer need. You will see a clear message when this happens so you know exactly what to do. Deleting old or unused assets from the portal will free up space immediately.
A few things worth knowing about how asset storage works:
The best way to avoid hitting your limits is to stay on top of what you have stored:
If your team is regularly hitting storage limits and needs more room, upgrading your plan will increase your allowance. Visit our pricing page to compare plans or get in touch with us and we can help you find the right fit.
If you have any questions about these changes or need help managing your storage, please reach out to us at hello@probo.ci. We are happy to help.

When you sign up for a Probo.CI registration code, you will get a two week trial of the plan of your choosing. For more information on how to get started, click here .
LEARN MORE ABOUT PROBO.CI'S PRICING