Secrets Pricing
The included secrets allowance, how packs are added and removed, and why project variables are never charged.
Secrets are charged by how many you store, in packs, above a free allowance.
| What | Rate | Detail |
|---|---|---|
| First 5 secrets | Free | Included with every organization, no subscription required |
| Each pack of 5 | $2 / month | Added prorated when you exceed the limit, removed automatically when you drop back under it |
| Project variables | $0 | Unlimited, and never counted against the secrets limit |
The free allowance
Every organization starts with a number of secrets included at no cost, and no subscription is needed to use them.
Packs
Past the free allowance, secrets are bought in fixed-size packs. Buy as many as you need — there is no ceiling.
A pack is added as a prorated subscription item the moment you exceed the current limit, so you are charged for the part of the period you actually hold it.
Packs are removed automatically
Delete enough secrets to fall back inside your existing allowance and the surplus pack is removed for you. You are not left paying for capacity you stopped using, and there is no separate downgrade step to remember.
Project variables are free
Non-sensitive configuration — URLs, feature flags, plain settings — belongs in project variables, which are unlimited, readable, and never metered. They do not count against the secrets limit.
The rule of thumb: if reading the value out loud would be a problem, it is a secret. Everything else is a variable.
Putting ordinary configuration in the vault is the most common reason an organization buys packs it does not need.
Versions are not charged
Updating a secret starts a new version. Versions are not counted separately — only the number of secrets you hold matters.