Plans and limits
Every plan includes the whole product. Plans differ in how much you can build, run and store.
Plans
Free costs nothing and has hard limits. Starter is €10 and Pro €20 a month plus VAT, billed monthly with no trial. EU consumers pay 23% VAT on top (€12.30 and €24.60); EU businesses with a valid VAT ID get reverse charge. Checkout shows the final amount before you pay. See Pricing and the Billing terms. You manage your plan in Account settings.
Limits by plan
Limits apply to your organization. Monthly limits reset on the first day of each month and daily limits at midnight, both in UTC.
| Limit | Free | Starter | Pro |
|---|---|---|---|
| Projects | 2 | 10 | 20 |
| Deployments per day | 20 | 100 | 500 |
| Builds at the same time | 2 | 6 | 10 |
| Build time per month | 120 min | 300 min | 600 min |
| Container active time per month | 250 h | 720 h | 1,600 h |
| Container CPU time per month | 25 h | 72 h | 160 h |
| Container memory per month | 225,000 GB-s | 648,000 GB-s | 1,440,000 GB-s |
| Function requests per month | 250,000 | 1,000,000 | 2,000,000 |
| Function execution per month | 10,000 GB-s | 50,000 GB-s | 100,000 GB-s |
| Workers CPU per month | 3,000,000 ms (50 min) | 30,000,000 ms (500 min) | 100,000,000 ms (1,666⅔ min) |
| Stored build artifacts | 1 GiB | 2 GiB | 10 GiB |
| File storage | 1 GiB | 5 GiB | 20 GiB |
| File transfer per month | 25 GiB | 100 GiB | 500 GiB |
| Logs per month | 256 MiB | 1 GiB | 5 GiB |
| Containers, functions and storage buckets | 50, 50, 20 | 75, 75, 30 | 100, 100, 40 |
A build starts when the month's unused build time covers its estimate: the longest of the project's last 5 builds plus a quarter, or 10 minutes for a first build, counting builds already running. Each build then counts its actual time: one that runs past its estimate still finishes and its extra time counts as used. When the build time left is less than a build's estimate, that build is refused until the reset or a plan change. App request counts and response traffic have no separate plan allowance, but Worker execution consumes the organization's monthly CPU budget. CPU is measured after startup, including background work; startup CPU and time waiting for I/O are excluded. See Workers for instance resources and runtime limits.
Container sizes
A container app runs in one of these sizes. New apps start on euro-small; you can pick another size your plan allows. Every size scales to zero when idle. A container app runs at most 1 instance on Free, 2 on Starter and 3 on Pro.
| Size | CPU | Memory | Plans |
|---|---|---|---|
| euro-small | 0.1 vCPU | 256 MB | Free, Starter, Pro |
| euro-medium | 0.25 vCPU | 512 MB | Free, Starter, Pro |
| euro-large | 0.5 vCPU | 1 GB | Starter, Pro |
| euro-xlarge | 1 vCPU | 2 GB | Starter, Pro |
When you reach a limit
- Actions that would go over a limit, such as creating a project, deploying or uploading a file, are refused with
quota-blockedand say what you can do: wait for the reset, delete something, or change plan. Your usage page shows where you stand. - Exhausting the Workers CPU budget or either Function monthly allowance blocks new Worker and Function executions across the organization with 429
quota-blocked. Wait for the UTC monthly reset, or upgrade Free or Starter to a plan with enough allowance. Pro must wait for the reset. Retrying after a few seconds or deleting a project does not restore consumed CPU. - Container apps and static sites that are already running keep serving. Static assets served without running a Worker also remain available.
Changing plan
A plan upgrade changes the monthly Workers CPU allowance without clearing CPU already used. Worker instance resources stay fixed on each deployment's route; a new deployment selects the current plan's resource class. See Runtime limits.
A paid plan cancelled at the end of its period keeps its limits until that period ends, then moves to Free. Existing projects stay visible, but actions that need more than Free allows are blocked until your usage fits Free or you choose a paid plan again. The Billing terms cover payments, withdrawal and refunds.