Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean Clerk has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 4 scoped observations for Clerk. The baseline covers backend request allowance, invitation creation, members per organization, free retained-user allowance. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| backend request allowanceEndpoint-specific and frontend limits can apply in addition to the backend allowance. | Production: 1,000 requests/10s; development: 100/10s | Per Clerk instance | ClerkAug 22, 2026 |
| invitation creationOrganization invitations use separate documented counts. | 100/hour individual; 25/hour bulk | Instance | ClerkAug 22, 2026 |
| members per organizationB2B-enabled plans can configure higher or unlimited membership. | 5 default; 20 maximum without B2B add-on | Organizations | ClerkAug 22, 2026 |
| free retained-user allowanceMRU is a billing metric distinct from total historical user records. | 50,000 MRUs per application | Free | ClerkAug 22, 2026 |
Tracked constraints and impact
Frontend/backend API, invitation, organization, metadata, and MRU limits. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
Clerk Backend API Rate Limits
Clerk Backend API Rate Limits, verified against Clerk's official documentation with scope, implementation impact, caveats, and a direct check.
Clerk Invitation Rate Limits
Clerk Invitation Rate Limits, verified against Clerk's official documentation with scope, implementation impact, caveats, and a direct check.
Clerk Organization Member Limits
Clerk Organization Member Limits, verified against Clerk's official documentation with scope, implementation impact, caveats, and a direct check.
Clerk Free Monthly Retained Users
Clerk Free Monthly Retained Users, verified against Clerk's official documentation with scope, implementation impact, caveats, and a direct check.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current Clerk baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Frontend, backend, invitation, and metadata request limits
Organization membership and creation limits
Free monthly retained user allowance