How BrewInTH counts your storage, and volumes that grow by themselves

Since 21 Oct 2026 your package counts uploaded files, what is really on persistent storage and database data. Volumes grow on their own at 60% and can shrink.
You open Projects and find a new panel under your project cards called Resource distribution. Or an email arrives saying a project's "persistent storage (/bw-data) grown 1.0 GB → 1.5 GB". Do you owe more? Do you need to do anything? Maybe you picked a large persistent volume a while ago and worry that it's eating your package's space.
Since 21 October 2026, BrewInTH counts your package's storage by what you actually use, and persistent volumes grow on their own. This guide explains what counts, where to see the figures, how automatic growth works, how to switch it off or cap it, how to shrink a volume you sized too generously, and what to do when space runs out.
In short
📦 Your package counts three things across every project: uploaded files, what's really on persistent storage, and your databases' data
🆓 The size you chose for persistent storage, backups and Redis don't count
📈 At 60% full, a volume grows by 50% on its own, up to a cap of 80% of the package's storage, at no extra cost
🎛️ Switch growth off or set a cap in the Resource distribution panel; shrink a volume under App settings
🌐 When the package is full, your sites keep running, but uploads and new releases wait until you free up space or upgrade
What counts toward your package's storage
Each package comes with one allowance of storage shared by the whole account. At the time of writing that's 20 MB on Free, 200 MB on Starter and Seed, 1 GB on Maker, 10 GB on Growth and 25 GB on Pro (compare the plans). It's measured against three things, added up across all your projects:
- Uploaded files you haven't deleted, including the source ZIP of every version and the files of static sites. Old versions keep counting until you delete them.
- Persistent storage in use: what's actually on each project's
/bw-data, such as images your users upload or an SQLite file. It's measured every hour while the app runs. - Database data in PostgreSQL, MySQL, MariaDB and MongoDB.
What doesn't count: the size you chose for persistent storage (pick 160 MB, store 25 MB, and 25 MB is what counts), backups and Redis.

Before 21 October, the size you picked came off your package straight away, even while empty, and databases didn't count. If you've read those rules somewhere, it's now the other way round.
Where to see the figures
The "Resource distribution" panel on the Projects page
Open Projects and scroll below your project cards. The panel shows:
- The account total: how much you really use, out of how much, as a percentage
- One bar split by kind: uploaded files, volumes, databases and free space
- A row per project, largest first, with Uploaded files, Volume used / chosen, Databases and Total, plus an Auto-grow switch and a Project cap setting
The line under the table states the platform's current rules: the cap per project and the point where growth starts. The team can change those figures, so if the console says something different from this article, go by the console.
The resource strip and the Usage tab of each project
On a project's page, right under the public link, is a strip of six figures, from Uploaded files, Storage /bw-data and Database to Bandwidth this month. A figure at 80% turns orange, and at 95% red. Click any of them to open the project's Usage tab, which adds backups, a Grown by the platform history and 30-day charts. A "—" in the storage figure means it hasn't been measured yet; a site that's asleep keeps its last figure.
The Usage page in the side menu breaks down every kind of space for the whole account, including backups, which don't count toward the package (Your BrewInTH Usage page explains each box).
How persistent storage grows on its own
The size of a project's persistent storage is the most its app can write. Every hour the platform measures it, and once it's 60% full, the platform grows it by 50% (at least 256 MB a step), up to the project's cap. The app keeps running while it grows, there's nothing to republish, and it costs nothing extra. Each time, the account owner gets an email with the old and the new size.

An example: on Growth (10 GB), your AI gave a project 1 GB of persistent storage. When the files reach about 600 MB, it grows to 1.5 GB, then to about 2.3 GB, 3.4 GB and so on, up to 8 GB, the cap on this package.
The cap per project is 80% of the package's storage, whatever the other projects chose. At the time of writing:
- Free: 16 MB
- Starter, Starter Plus and Seed: 160 MB
- Maker: 819 MB
- Growth: 8 GB
- Pro: 20 GB
Since the chosen size no longer counts, several projects can have large volumes at once: on Growth, two projects can each be set to 8 GB, as long as what's actually stored across the account stays within 10 GB. Still, starting with a sensible size, say 1 GB, and leaving growth on is easier to look after.
The platform won't grow a volume that's at its cap, a project whose growth you switched off, or anything at all while the package's storage is full. In those cases you get an email when the volume reaches 80%, and again at 95%. These emails go to the account owner; if your account has no email address yet, add one under Report / alert email on the Account settings page.
While a volume grows, Recent activity on the Overview may list a Pause or resume job: that's the platform applying the new size, and the site isn't paused.
Switch growth off, or cap a project
Growth is on for every project by default. To change that, use the Resource distribution panel, on the row of a project that has persistent storage:
- Auto-grow: switch it off and the platform stops growing this volume. You'll get warning emails as it fills up instead.
- Project cap: the default is Platform cap (8 GB on Growth, for example). Pick a lower value, from 256 MB up; growth stops there, and the persistent storage panel won't offer more than that either.
A cap suits a test project, or an app that keeps writing logs or a cache to persistent storage, so one project can't fill the whole package and hold up the others. (On Free, Starter, Starter Plus and Seed the platform cap is already below 256 MB, so there's nothing else to pick.) A cap doesn't make an existing volume smaller; for that, shrink it as described below.
Shrink a volume you sized too generously
First, ask whether you need to. The size you chose no longer uses up your package, so shrinking only helps when you want to limit how much this app can write, and the site goes down briefly while it happens.
Steps
- Open the project, go to the App settings tab and find Persistent storage (/bw-data).
- Pick a smaller value under Size. The Save button turns into Shrink.
- Read the note that appears, then type the project's name in Project name, exactly as it's written.
- Press Shrink and follow it under Recent activity on the Overview (the job is called
volume.shrink).
The platform stops the app, backs up everything on the volume, moves the files to a new volume and starts the app again. The console says the site is down for a minute or two; with lots of files it can take longer, so pick a quiet hour. The backup stays in the Volume backups (/bw-data) panel with the kind pre_shrink, and the old volume isn't destroyed: the platform keeps it in its trash (how to restore from a backup).
Conditions
- The new size can't be below 256 MB, so a volume that's already smaller, as on Free, Starter and Seed, can't shrink any further.
- The files on the volume may fill at most 90% of the new size, leaving at least 10% free.
- The volume must have been measured in the last 24 hours. If the app is asleep, open the site to wake it, wait for the next measurement (within about an hour) and try again.
- No backup or restore of this project's persistent storage may be running.
If growth is still on, the volume will grow again once it reaches 60% of its new size. To keep it at that size, switch Auto-grow off or set a cap as well.
Out of space: find out which space is full

A project's persistent storage is full
The app can't write new files to /bw-data: user uploads fail, or it can't save to its SQLite file. This happens once the volume can't grow any further, and your other projects aren't affected. Delete files you no longer need, switch growth back on or raise the cap, or upgrade the package to lift the cap.
The package's storage is full
The three things together exceed the package, and the console shows the banner The package's storage is full. Every site keeps running, but for now you can't:
- upload new files, whether from your AI or through the Upload & go live page
- publish a new release
- grow persistent storage, automatically or by hand
- restore deleted files
The fixes, quickest first:
- Delete old version ZIPs on the Files tab. The space comes back at once. Files the running version uses can't be deleted, and deleted files can be restored later when there's room (how to restore deleted files). Keep the ZIP of any version you might want to roll back to.
- Clear unused files from persistent storage, such as old caches or logs. The figure drops at the next measurement, within about an hour.
- Upgrade the package under Plans & billing.
You'll get warning emails when the package reaches 80% and 95%, before it's actually full.
Let your AI find what's taking the space
If you already use a coding agent on this project, send this in the same chat. It reports first and waits for your go-ahead.
My BrewInTH package's storage is almost full. Check and report first; don't delete or change anything yet.
1. How many uploaded files does this project have, how large are they in total, and which ones does the running version not use?
2. Run a command in the app to list the 10 largest folders under /bw-data (du -sh, for example).
3. Is there code that writes logs, caches or temporary files to /bw-data and never removes them?
4. Suggest ways to cut usage, such as resizing images when users upload them or clearing old caches automatically, then wait for my approval before you act.
FAQ
Does automatic growth cost extra?
No. The platform grows the volume within the storage your package already has, and the growth email says so. What counts toward your package is still what you actually store, not the size after growth.
How much persistent storage does the Free package get?
Up to 16 MB, and the account's 20 MB also has to hold your uploaded files and your database data. That's enough for a test app or a small SQLite file. If people will upload photos to your site, choose a paid package.
Do I lose files when I shrink?
No. Everything is backed up before the move. If something goes wrong, restore the pre_shrink backup from the Volume backups (/bw-data) panel.
Do databases grow on their own too?
All of an account's databases on the same machine share one storage pool. The platform grows that pool by the same rule, up to twice what the package provides (Free goes from 512 MB to 1 GB, for example), and emails you when it does. You'll find it on the Usage tab, in the Account pool column. The data inside still counts toward your package as usual (Redis doesn't count).
Summary
Since 21 October 2026, BrewInTH counts your package's storage from uploaded files, what's really on persistent storage and your databases' data; the size you chose doesn't count. Persistent storage grows on its own at 60%, up to a cap of 80% of the package. You see and set all of it in the Resource distribution panel, you shrink a volume under App settings, and if the package fills up your sites keep running: delete old ZIPs before you decide to upgrade.
See your account's resource distribution →
