Reference
Plan limits
Every Cloud plan has the limits below. You never choose CPU, memory or a server size: StackBlaze allocates resources automatically and meters what you use. All values are subject to change.
What each plan includes
| Limit | Free Trial | Developer | Pro | Business |
|---|---|---|---|---|
| Trial period | 7 days | — | — | — |
| Projects | 1 | 5 | 25 | 100 |
| Apps per project | 1 | 10 | 50 | 200 |
| Environments per project | 1 | 2 | 5 | 10 |
| Preview environments | — | — | ||
| Deployment regions | 1 | 1 | 3 | 3 |
| Custom domains + automatic SSL | ||||
| Unlimited free build minutes | ||||
| Max size per app | 0.5 vCPU · 0.5 GB RAM | 2 vCPU · 4 GB RAM | 4 vCPU · 16 GB RAM | 8 vCPU · 32 GB RAM |
| Max replicas per app | 1 | 1 | 3 | 10 |
| Scaling | No autoscaling | Basic vertical scaling | Horizontal autoscaling | Advanced autoscaling |
| Automatic resource allocation | ||||
| Databases (Postgres, MariaDB, Redis) | 1 | 2 | 10 | 30 |
| Database connections | 100 | 200 | 400 | 500 |
| Database backups (retention) | — | 7 days | 14 days | 30 days |
| Database high availability | — | — | ||
| Team members | 1 | 1 | 5 | 20 |
| Team permissions | Single user | Single user | Basic collaboration | Advanced permissions |
| Single sign-on (SSO) | — | — | — | |
| Log retention | Not promised | 3 days | 14 days | 30 days |
| Support | Community | Community | Community | Community |
Databases and builds
Databases deploy with one click and grow automatically within your plan. Their connection limits are set for you from the plan, so a small database can't run out of memory from too many connections.
| Limit | Free Trial | Developer | Pro | Business |
|---|---|---|---|---|
| Key Value (Redis) memory · max connections | 25 MB · 50 | Automatic · 200 | Automatic · 1,000 | Automatic · 2,000 |
| Concurrent builds | 1 | 2 | 5 | 10 |
| Build timeout | 10 min | 30 min | 60 min | 90 min |
Rate limits
Rate limits apply across all plans. Exceeding a rate limit returns HTTP 429 with a Retry-After header indicating when you can retry.
| Resource | Limit |
|---|---|
| GitHub webhooks | Processed as they arrive; retries follow GitHub’s delivery policy |
| Builds | Queued when your plan’s concurrent build limit is reached |
| Log streams | Live tail is per app/container; use search for history |
Bandwidth billing
Bandwidth is measured as outbound data transfer from your apps to the internet. Inbound traffic and internal traffic between apps in a project are free.
$0.05
per GB transferred, outbound
Free
Inbound and internal traffic
What happens when you hit a limit
When you reach a count limit (projects, apps, databases, environments, team members), creating a new one is blocked and existing ones keep running. Rate limits return 429 with Retry-After. To raise limits, upgrade your plan from Settings → Billing.