Ory Network rate limiting
Ory Network uses rate limits to protect your applications against abuse and ensure fair resource allocation across all customers. Ory is currently migrating to a new project rate limiting policy. New workspaces are automatically on the new policy; existing customers are being migrated by subscription tier.
Which system applies to you?
| You are... | Your system |
|---|---|
| A new customer (workspace created after [DATE]) | Rate limits - new |
| An existing customer — migration not yet completed | Rate limits - legacy |
| An existing customer — migration completed | Rate limits - new |
You can check which policy your workspace is on in the Ory Console under Settings → Rate Limits, or by checking your migration notification email.
What's changing?
The legacy rate limit policy applied project rate limits per endpoint-path and limits were fixed per subscription plan and environment. The new project rate limit policy is a more structured model that distributes project rate limits across different types of API operations. API operations are now organized into buckets based on service, access level, and rate limit threshold. This allows the Ory platform to handle traffic more efficiently while giving you clearer and more consistent behavior when interacting with the APIs.
Migration plan
The new rate limits will be introduced gradually to ensure a smooth transition. No action is required on your end. Ory will notify you before your workspace is migrated. During the migration, your project rate limit behavior remains unchanged until the cutover completes.
Migration schedule:
| Phase | Plan | Date |
|---|---|---|
| 1 | Developer | [DATE] |
| 2 | Production | [DATE] |
| 3 | Growth & Enterprise | [DATE] |
The types of rate limits, for project-based and endpoint-based, remain the same in both rate limit policies.
Learn more about rate limits
- Rate limits - new—applies to new customers and migrated workspaces
- Rate limits - legacy—applies to existing customers pending migration