| 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 | |
| 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 |
| 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 |
| 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 |
| 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. |
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.
| Developer | Team |
|---|
| Members | 1 | Unlimited |
| Named environments per project | 1 | 5 |
| Preview environments open at once per project | 2 | 10 |
| Custom domains per service | 1 | 5 |
What each plan costs, and what Team includes, is on the billing page.
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.
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.
An organization that has used its trial credit is restricted the same way. If seven days pass without a payment method, its running services are paused as well; adding a card lifts both.
Suspension is reserved for the daily spending ceiling, prolonged non-payment, a trial left without a payment method past its grace period, and operator action. It stops everything that costs money: hostnames stop routing, web services stop accepting requests at the provider as well as at Kuppit's edge, workers are scaled to no instances, schedules stop invoking, and databases refuse connections and suspend their compute. Nothing is deleted. Rolling back is not allowed, because there is no traffic to roll back to; cancelling a deployment still is. When the suspension lifts, everything comes back as it was configured, without a deployment.