Platform Limits
As a guideline for our community, we expect most users to fall within the limits for each plan. Our goal is to be as permissive as possible while not allowing an unreasonable burden on our infrastructure. If you have a special use case that requires higher limits, please reach out to our support team.
Plan Limits
| Name | Developer | Team | Team Add-Ons | Enterprise |
|---|---|---|---|---|
| Users | 25 | 500 | -- | Custom |
| Projects | 10 | 250 | -- | Custom |
| Environments per Project | 4 | 15 | -- | Custom |
| Configs per Environment | 10 | 100 | -- | Custom |
| Config Syncs * | 5 | 100 | 500 | Custom |
| Integrations | 10 | 100 | -- | Custom |
| Webhooks | 5 | 50 | -- | Custom |
| Logs | 3 days | 90 days | -- | Custom |
| Trusted IPs per Config | -- | 20 | -- | Custom |
| Reminders | 5 | 50 | -- | Custom |
| Service Accounts | -- | 250 | -- | Custom |
| Service Tokens | 50 | 500 | -- | Custom |
| CLI Tokens per User | 5 | 20 | -- | Custom |
| API Read Rate Limit ** | 240/min | 480/min | -- | Custom |
| API Secrets Read Rate Limit ** | 120/min | 240/min | -- | Custom |
| API Write Rate Limit ** | 60/min | 120/min | -- | Custom |
* This applies to Config Syncs created in the dashboard (or via the Secrets Sync API). Kubernetes Operator "syncs" and CLI secret fetches are not considered Config Syncs in this context.
** This applies to direct requests to the API along with requests made by the CLI and Kubernetes Operator. The rate limit is per access token.
Abuse Limits
| Name | Developer | Team | Enterprise |
|---|---|---|---|
| Secrets per Config | 1,000 | 1,000 | 1,000 |
| Config Payload Size | 500 KiB | 500 KiB | 500 KiB |
| Secret Name Character Length | 200 | 200 | 200 |
| Secret Value Size | 50 KiB | 50 KiB | 50 KiB |
Updated 29 days ago