Reference
Limits
The fixed limits on builds, requests, logs and hostnames, and what each plan allows. Plan figures are provisional during the alpha.
Builds
| Limit | Value | Beyond it |
|---|---|---|
| Files read from the repository | 20,000 | The repository is too large for Kuppit to build |
| Time to extract the repository | 60 seconds | The same |
| Time to build the image | 15 minutes | The build ran out of time |
| Length of a build or start command | 4 KiB | Refused when saved |
| Port, automatic builds | 1 to 65535 | Refused when saved |
| Port, Dockerfile builds | 8080, fixed |
Requests
| Limit | Value | Beyond it |
|---|---|---|
Request body, as declared by Content-Length | 100 MB | 413 from the edge; a body without a declared length is not checked |
| Time for your service to start responding | 120 seconds | 504 from the edge |
Logs
| Limit | Value |
|---|---|
| How far back runtime and build logs go | 30 days, and never before the deployment was created |
| Reads per organization | 15 per minute, across every deployment's logs |
Hostnames
| Limit | Value |
|---|---|
| Hold on a removed custom hostname | 24 hours before anyone can attach it again |
| Custom hostname length | 253 characters |
| Generated label length | 63 characters |
Deployments
| Limit | Value |
|---|---|
| Deployments in flight per service | One. A second Deploy, redeploy or rollback is refused until it settles; a new push supersedes it instead. |
| Rollback depth | Every deployment that went live keeps its image and can be rolled back to. |
Plans
Plan limits are provisional during the alpha and may change. What your organization is allowed is shown in the dashboard where it applies; a limit raised for you is shown there too.
| Per project or service | Developer | Team | Business |
|---|---|---|---|
| Named environments per project | 1 | 5 | 10 |
| Preview environments open at once per project | 2 | 10 | 25 |
| Custom domains per service | 1 | 5 | 10 |
Production and preview environments never count towards the named-environment limit. Only a preview that does not already exist counts towards the preview limit, so pushes to an open pull request are never refused. Sharing an existing database is a choice on every plan, not a plan feature.
What a restricted organization can do
When a spending limit or a plan ceiling is reached, the organization is restricted: running services keep serving and their hostnames keep routing, and new builds, deployments, projects, environments, databases, domains and scaling up wait until it is resolved. Rolling back and cancelling a deployment are always allowed.
Was this page helpful?