New rate limit model for Ory Network

Ory Network moves to a more fine-grained rate limit model. Instead of fixed
per-endpoint-path limits, project rate limits are now split into buckets
grouped by service, access level (admin vs. public), and operation cost
{service}-{access}-{threshold}).
Per-bucket thresholds are derived from five months of production traffic across the Ory Network, so a spike on one kind of operation no longer eats into the limits of unrelated endpoints.
Rate-limited routes now also return X-RateLimit-Limit, -Remaining, and -Reset response headers.

The new limits roll out gradually per subscription tier - Developer and new workspaces first, then Production, Growth, and Enterprise.
No action is required: a project keeps its current behavior until its workspace is migrated.

For more details please review the blog announcement and the updated technical rate limit guide.