Deploys · Plans and data
Limits
Deploys' packages differ in how many apps a project deploys. Deploys, rollbacks and their logs aren't counted.
By package
Loading the limits…
What counts as an app
Every app the project has counts, from its first deploy on: an app is each --app key Deploys has heard of. Its environments, deploys and rollbacks don't count, however many there are.
The workspace's owners see how many apps each project has, against its package, on Settings → Usage.
Past the limit
A new app's first deploy past the limit still runs, but is not recorded: Deploys refuses it, and mybeast-deploy says so, with the package and its limit, before your command starts:
mybeast-deploy: not reported: https://services.my-beast.com/deploys answered 422: The <package> package has room for <limit> apps, and <project> has <limit>. A bigger package has more. - the command runs all the sameThe apps you have keep deploying. A smaller package takes none of them away: it only stops new ones. For a bigger package, see Deploys' page.
When the project's subscription ends, Deploys takes in nothing new: each deploy runs unreported, and mybeast-deploy says the subscription ended. Renewing it at id lets the next deploy through.
The same on every package
| What | Limit |
|---|---|
| A deploy's log | 50,000 lines; lines past that are counted, not kept |
| A line of the log | 2,000 characters; a longer one is cut |
| A batch of the log | 512 KB (mybeast-deploy sends up to 256 KB) |
| Commits a deploy lists | 50, the ones since what was live |
| A saved deploy or rollback command | 500 characters, one line |
| API requests | 600 a minute per key |