Your BrewInTH Usage page: storage, bandwidth and package quotas
What the Usage page counts, each package's quota, what happens after the 80% warning, and how to cut storage and bandwidth before you upgrade.
Your site starts getting visitors, and one day an email arrives: "80% of your monthly bandwidth used". Or your AI reports that an upload failed because there is "not enough package storage". What do those numbers actually count? Do you need to upgrade right away, or is deleting a few old files enough?
This article walks through the Usage page in the BrewInTH console, box by box: what each package allows, what happens when you reach a limit, and how to cut storage and bandwidth before you decide to pay for more.
In short
📊 The Usage page in the left menu shows account-wide file storage and this month's bandwidth
📊 Bandwidth is counted per UTC calendar month and resets on the 1st at 07:00 Thai time
📊 You get a warning at 80%; the Free package stops serving at 100%, paid packages keep serving up to 150%
📊 Full storage does not take your site down, but new uploads are refused — delete old files in the Files tab
📊 Smaller images, videos on YouTube and static sites save a lot of bandwidth
Where is the Usage page?
Sign in to the console and click Usage in the left menu. The page covers the whole account (every project together) and refreshes its numbers every few seconds on its own.
Box 1: Stored files
The first number is the size of every file uploaded so far across all your projects — each file of a static site, or the ZIP of every version of an app — followed by the package quota, for example 12 MB / 20 MB.
Worth knowing: files of older versions still count until you delete them. If you deploy often, the ZIPs of every round slowly pile up.
Box 2: Upload reservations
Each time you or your AI start an upload, the platform first reserves room for the file. So this box is usually zero and only shows a number while an upload is in progress. If an upload never finishes, the reservation expires on its own.
Box 3: Bandwidth
This is how much data your sites sent to visitors this month — pages, images, scripts and API responses — recorded by the part of the platform that actually serves them. Every request counts, search-engine bots included.
The daily chart and the table by project
- Daily bandwidth shows the last 30 days; point at a bar to see the date and the figure. Use it to spot unusual spikes, such as the day you shared your link in a Facebook group.
- By project shows each project's file storage and bandwidth this month. Click a project's name to manage it.
What each package allows
Figures from the BrewInTH pricing page at the time of writing:
| Package | File storage | Bandwidth per month |
|---|---|---|
| Free | 20 MB | 1 GB |
| Starter (฿99/month) and Seed (฿749/year) | 200 MB | 10 GB |
| Maker (฿1,499/year) | 1 GB | 50 GB |
| Growth (฿2,899/year) | 10 GB | 200 GB |
| Pro (฿5,699/year) | 25 GB | 500 GB |
Always check the pricing page for the current figures.
Storage is shared by the whole account, not split per project: two projects on Starter share the same 200 MB. Persistent storage (/bw-data) that you turn on for an app also comes out of the package's space; you can see its size in each project's App settings tab.
What happens when bandwidth reaches a limit
The platform checks every minute and announces each step once — as a banner on the Usage page and as an email to the account owner, if an email address is linked to the account.
- 80% — an early warning. The site works as usual; the message says when the quota resets and suggests upgrading ahead of time if you expect to go over.
- 100% — sites on the Free package pause (visitors get status 429). Sites on a paid package keep serving, with extra room of half the quota.
- 150% (paid packages only) — the extra room is used up, and sites pause as well.
Paused sites come back on their own when the quota resets on the 1st of the next month, or the moment you upgrade on the Plans & billing page. Your data, databases and files stay where they are.
If no email address is linked to your account, you won't get the warning emails. Add one in your account settings so you hear about it before your visitors do.
What happens when storage is full
Full storage does not take a live site down — it keeps working. But new uploads are refused with "Not enough package storage", which means you cannot deploy a new version until there is room again.
Two ways out:
- Delete files you no longer need. Open the project, go to the Files tab and click Delete next to old files, such as the ZIPs of earlier versions. The room comes back at once. Files used by the running version cannot be deleted (you'll see "This file is part of the active release"), so the site cannot break this way. If you want to keep a way back, don't delete the files of the previous version you might roll back to.
- Upgrade the package if the files you really need are bigger than the quota.
How to cut storage and bandwidth
What BrewInTH already does for you:
- Text is compressed automatically. HTML, CSS, JavaScript and JSON are compressed before they are sent, and bandwidth counts the bytes actually sent after compression.
- Unchanged files of a static site are not counted twice. If a visitor's browser already has the file, the platform only answers "still the same", sends nothing and counts no bandwidth.
What you (or your AI) can do:
- Shrink images. Phone photos are often several MB each. Converted to WebP and no wider than 1600 pixels, they usually drop to a few hundred KB.
- Keep videos on YouTube and embed them. Video is by far the biggest bandwidth user.
- Keep the ZIP small. Leave out
node_modules,vendor,.gitand test files; the platform installs dependencies during the build. - Delete old ZIPs in the Files tab from time to time.
- Build sites that only show information as static sites. They are faster, cheaper and never need to sleep.
A prompt to have your AI slim the site down
This site is hosted on BrewInTH and is close to its package's storage/bandwidth quota. Please:
1. Find every image in the project larger than 300 KB, convert it to WebP no wider
than 1600 px and update the code to use it (keep the originals outside the deployed folder).
2. Add loading="lazy" to images that are not at the top of the page.
3. If the project contains videos, tell me first, then switch them to YouTube embeds.
4. Check that the ZIP you upload has no node_modules, vendor, .git or unused files.
5. Give me the size before and after, then deploy again.FAQ
When does bandwidth reset?
On the 1st of every month in UTC, which is 07:00 on the 1st in Thai time. The warning messages also show the reset date.
I got the 80% email. Should I upgrade now?
Not necessarily. Open the Daily bandwidth chart, see how much you use per day and multiply by the days left in the month. If you'll probably stay under, you can leave it. If a day spiked because of large images or videos, try the tips above first.
Does my database count towards file storage?
The Stored files figure on the Usage page counts uploaded files; it does not include the data in your databases.
Where do files my users upload to my site count?
If your app keeps them in persistent storage (/bw-data), they use the persistent storage size set in the App settings tab, which comes out of the package's space. When visitors open those files, that counts as bandwidth.
Can I buy extra bandwidth or storage on its own?
Not at the moment — there is no add-on for bandwidth or storage. The way to get more is a larger package.
Summary
The Usage page shows everything in one place: account-wide storage, this month's bandwidth, a daily chart and figures per project. The first warning comes at 80%, so there's no need to panic: look at the chart, shrink images, move videos, delete old ZIPs, and upgrade when your site really grows.
Open the Usage page in the console →