Platform hub

Clerk limits

Frontend/backend API, invitation, organization, metadata, and MRU limits. Values below are scoped rather than flattened into one misleading platform-wide number.

Verified Aug 22, 2026Official docs
Quick answer:  Clerk has multiple independent constraints. Match the exact plan, model, runtime, invocation mode, or server configuration shown in each row.

Current documented limits

ConstraintCurrent valueScopeVerified source
backend request allowanceEndpoint-specific and frontend limits can apply in addition to the backend allowance.Production: 1,000 requests/10s; development: 100/10sPer Clerk instanceClerkAug 22, 2026
invitation creationOrganization invitations use separate documented counts.100/hour individual; 25/hour bulkInstanceClerkAug 22, 2026
members per organizationB2B-enabled plans can configure higher or unlimited membership.5 default; 20 maximum without B2B add-onOrganizationsClerkAug 22, 2026
free retained-user allowanceMRU is a billing metric distinct from total historical user records.50,000 MRUs per applicationFreeClerkAug 22, 2026

How to apply Clerk limits safely

The monitored baseline covers backend request allowance, invitation creation, members per organization, free retained-user allowance. Treat these as separate constraints rather than one platform-wide capacity number: a workload can fit one row and still fail another because the plan, model, endpoint, runtime, region, invocation mode, or account scope differs.

  1. Match the production workload to the exact scope printed beside each value and confirm it in the active Clerk console, configuration, or response headers.
  2. Measure the serialized request, token volume, duration, concurrency, storage, or connection demand at realistic percentiles, then preserve headroom for bursts and retries.
  3. Check every adjacent layer—client, SDK, gateway, proxy, queue, database, and downstream service—for a smaller effective limit before changing architecture.

Specific limit pages

These pages exist because the constraint has a distinct implementation or troubleshooting intent. Closely related keyword variations stay consolidated.

Official sources

View Clerk change history