Concepts
Resource Limits
Learn more about how to structure your implementation to avoid resource limits.
Turnkey is scalable to millions of users and millions of transactions.
However, we have limits on the number of resources within a single organization to avoid performance slowdowns and overly complex permission models. You can scale your organizational resources beyond these limits via sub-organizations. You can create an unlimited number of sub-organizations within a single organization.
Currently, the resource limits within a single organization are as follows:
Note that if you create an expiring API key that would exceed the limit above, Turnkey automatically deletes one of your existing keys using the following priority:
However, we have limits on the number of resources within a single organization to avoid performance slowdowns and overly complex permission models. You can scale your organizational resources beyond these limits via sub-organizations. You can create an unlimited number of sub-organizations within a single organization.
Currently, the resource limits within a single organization are as follows:
| Resource | Maximum parent org allowance | Maximum sub-org allowance |
|---|---|---|
| Sub-Organizations | unlimited | 0 |
| HD Wallet Accounts | unlimited | unlimited |
| HD Wallets | 100 | 100 |
| Private keys | 1,000 | 1,000 |
| Users | 100 | 100 |
| Policies | 100 | 100 |
| Invitations | 100 | 100 |
| Tags | 100 | 10 |
| Authenticators per user | 10 | 10 |
| API keys per user (long-lived) | 10 | 10 |
| API keys per user (expiring) | 10 | 10 |
| OAuth providers per user | 10 | 10 |
- Expired API keys are deleted first
- If no expired keys exist, the oldest unexpired key is deleted