Secrets · Plans and data
Limits
A package sets how many environments a project has and how many variables each holds. Reads are never counted.
Limits by package
Loading the limits…
What counts
- Environments: the project's environments, the ones listed on its page at id.my-beast.com. They're counted there, when one is added.
- Variables per environment: the names an environment holds now, Secret and Visible alike, counted in each environment on its own. The keys id.my-beast.com writes for your other My Beast products count too. A removed variable doesn't, though its history stays.
Reading isn't counted: pulls, API reads, downloads and showing a value are limited only by the limits below, the same on every package.
Past a limit
- A new environment is refused at id, naming the package and how many environments it has room for.
- A new variable in a full environment is refused, with the package's room, how many the environment has, and a link to a bigger package. Remove the ones nothing reads any more, or move up.
- An import whose new names don't fit is refused whole: nothing of it is imported.
- What you have keeps working. Changing values, removing variables, reading with tokens and downloading go on as before, and a smaller package takes nothing away: past its limit, only adding waits until there's room.
Limits on every package
| What | Limit |
|---|---|
| A value | 32 KB |
| A pasted .env | 256 KB |
| A name | 64 characters |
| Active service tokens | 10 per environment |
| Reads with a token | 120 a minute per token, 300 a minute per address |