Docs menu
Limits & Quotas
The limits on a Primcloud account: resource caps, build minutes, time limits, deployment history, and log retention. Caps are the same on every plan and raised on request.
On this page
Resource caps#
Resource caps are the same on every plan and set high enough that real apps run well inside them. If you hit one for a real reason, contact support and we'll raise it on your account, with no plan change.
| Resource | Default | Notes |
|---|---|---|
| Applications per account | 1,000 | Across every region. |
| Environments per application | 100 | |
| Custom domains per application | 100 | The *.primcloud.app URL doesn't count. |
| Formations per environment | 20 | |
| Instances per formation | 100 | |
| Secrets per environment | 1,000 |
When you ask for a raise, tell us which cap, what you need it raised to, and what it's for.
Builds, releases, and tasks#
| Limit | Standard | Pro | Team |
|---|---|---|---|
| Included build minutes / month | 300 | 1,000 | 3,000 |
| Build overage | $0.007 per minute | $0.006 per minute | $0.005 per minute |
| Concurrent builds | 1 | 2 | 5 |
| Max single build | 20 minutes | 45 minutes | 60 minutes |
| Max single release process | 20 minutes | 45 minutes | 60 minutes |
| Max single task run | 20 minutes | 45 minutes | 60 minutes |
Build minutes are the time your deployments spend building. Minutes past your plan's allowance are billed at its overage rate on your next invoice. There's no hard cutoff, so a build late in the month won't be stopped for running over. A usage alert can warn you as you get close.
A build that runs past your plan's maximum is stopped and marked Build Failed, a release process is stopped and its deployment marked Release Failed, and a task is stopped. To get under the limit, split the work up, or ask us to raise it on your account.
Deployment history#
Each environment can roll back to, or redeploy, its most recent successful builds: 3 on Standard, 10 on Pro and Team. A successful build is a deployment that built your code, such as a push, a manual deploy, or a redeploy. Deployments that reuse a kept build (rollbacks, secret changes, compute changes) are kept with it, and so is the live release.
Deployments older than 90 days leave your history, but each environment always keeps its newest 25, and the live release and everything you can roll back to are never removed.
Log retention#
Application and HTTP request logs are kept for 7 days on Standard and 30 days on Pro and Team. See Logs.