# blitz.cloud plan limits - apps, memory, storage and databases

> Exact limits of the blitz.cloud free plan: apps, memory, storage and databases. How memory is reserved per app, CPU, and what is not limited.

Web page: https://blitz.cloud/docs/limits/
Updated: 2026-10-18

The blitz.cloud free plan allows up to 5 apps, 512 MB of reserved memory shared across them, 10 GB of storage and one managed database, with database backups kept for 7 nights. An app nobody visits for 15 minutes goes to sleep and wakes on the next visit. Pro raises these limits for 7 EUR per month.

## Plan limits

| | Free | Pro |
|---|---|---|
| Apps | 5 | 50 |
| Reserved memory pool | 512 MB | 4 GB |
| Storage | 10 GB | 50 GB |
| Managed databases | 1 | 5 |
| Database backups kept | 7 nights | 30 nights |
| Burst ceiling, memory | 9 GB | 20 GB |
| Burst ceiling, CPU | 16 cores | 35 cores |
| Outgoing traffic speed, per app | 50 Mbit/s | 200 Mbit/s |
| Builds at once | 1 | 3, ahead of the queue |
| Build minutes per month | 300 | 2000 |
| Private networks | 1 | Up to 5 |
| Nightly copies of app files | No | 30 nights |
| Price | 0 EUR | 7 EUR per month, VAT included |

Hitting a limit blocks that one action, with a sentence naming the limit and what would free up room. Apps that are already running are never stopped because of it.

An app made of several parts, like a web part, an API and a worker from one compose file, counts each part that keeps running as one of the plan's apps.

When Pro ends and you use more than the free plan includes, everything keeps running for 14 days. After that the newest apps and databases over the limit are paused. Nothing is deleted, and it all comes back when you take Pro again.

## How memory is counted

The memory pool counts memory that is reserved, not memory that is in use. Each app reserves a fixed amount depending on its size, and may use more than that up to its own ceiling when the server has room.

| Size | Reserved memory | Memory ceiling | Reserved CPU | CPU ceiling |
|---|---|---|---|---|
| Small | 128 MB | 512 MB | 0.05 cores | 0.5 cores |
| Medium | 256 MB | 1 GB | 0.1 cores | 1 core |
| Large, Pro only | 768 MB | 2 GB | 0.2 cores | 2 cores |

Apps from Docker images start at the small size, and App Store apps start at the size their entry says (the [App Store page](https://blitz.cloud/docs/app-store/#storage-and-memory) lists which ones are medium; Immich is the only large one, which is why it needs Pro). You can change an app's size yourself in Settings, Advanced, as long as it isn't made of several parts and there's room in your plan's memory pool.

When an app runs out of memory twice within six hours at its size, we give it the next size by ourselves, as long as your plan's memory pool has room. Its Activity tab says when we did. If there's no room, the app's page and its Activity tab say so and what frees some. A size we raised goes back down one step after two weeks in which the app used well under the smaller size's ceiling. A size you chose yourself stays as you set it.

Databases reserve memory from the same pool:

| Database | Reserved memory | Reserved storage |
|---|---|---|
| PostgreSQL | 128 MB | 1 GB |
| MariaDB | 192 MB | 1 GB |
| Redis (Valkey) | 64 MB | 0.5 GB |
| Cache that comes with a store app | 48 MB | none |

A cache belongs to its app and doesn't count as one of the plan's databases, only its memory counts. See [apps that bring a cache](https://blitz.cloud/docs/app-store/#apps-that-bring-a-cache).

So each small app takes 128 MB of the free plan's 512 MB, and an app plus a PostgreSQL database takes 256 MB. The app count and the memory pool are both limits, and you reach whichever runs out first.

## How storage is counted

Storage also counts reservations. A Docker image with kept folders reserves 1 GB, an App Store app reserves up to 5 GB (a few keep everything in their database and reserve none), and databases reserve as listed above. Nextcloud and its MariaDB together reserve 6 of the free plan's 10 GB.

The meters in Settings count sizes the way the plans are sold, so a full 10 GB plan reads "10 of 10 GB".

## Sleeping apps

An app with an address that nobody has visited for 15 minutes is scaled to zero. It wakes when a person opens it in a browser. Requests from programs, such as uptime monitors, scripts, webhooks or API clients, don't wake it: they get an answer that the app is asleep, and it stays asleep. It holds no memory while it sleeps. On Pro an app you don't keep awake sleeps after two hours. You can keep it awake, and then programs reach it at any time. Bots and background workers without an address never sleep, and neither do private apps. On the free plan a background worker stops after 2 days with no sign-in, no deploy and no visit to the dashboard. We email you one day before, and Start runs it again. In an app made of several parts, only the parts with an address sleep. A database sleeps when every app linked to it sleeps or is paused, and starts again before the app does. A database without a linked app keeps running. More in [databases](https://blitz.cloud/docs/databases/).

The first visit to a sleeping app waits while it wakes, about 10 seconds, and then gets the app's own answer. That includes forms and other POST requests sent from the browser, so a form sent to a sleeping app arrives as it was sent. A browser only sees our waking page if the wake takes longer than 5 seconds, and the page reloads by itself once the app is ready.

## Build minutes

Every build counts from the moment it starts until it ends, whether it works or not. Builds that failed because of us don't count. On the free plan, the overnight updates of apps built from GitHub count too, except a rebuild for a security fix. On Pro and Business they don't count. The count starts again on the first day of each month (UTC). The free plan has 300 build minutes a month, Pro has 2000, and Business has no limit. When the month's minutes are used up, nothing new is built until the next month, pushes included, and the reason shows where you started the build and in the app's Activity. A build that is already running finishes, and running apps keep running. Settings shows how many minutes you've used this month.

## Outgoing traffic

Each app can send at up to 50 Mbit/s on the free plan and 200 Mbit/s on Pro. That is a speed limit, not a quota: there's no monthly allowance and no bill for traffic.

## What is not limited

- There's no traffic quota and no request counter today.

## What is blocked

- Outgoing mail on ports 25, 465 and 587 is blocked for every app, to stop spam. Use an email API over HTTPS instead.
- Apps can't reach other accounts' apps or databases, the platform's internal services, or private IP ranges.
- Crypto miners are paused before they run, and the owner gets a mail naming what we found.

## Other limits

| Limit | Value |
|---|---|
| Kept folders per app | 6 |
| Environment variables per app | 64 |
| Open log streams per account | 2 |
| Main address renames | Once every 14 days |
| Restarts before a crashing app is stopped | 15 |
| Architecture | amd64 only |