Quick answer
Clerk documents free retained-user allowance as 50,000 MRUs per application. MRU is a billing metric distinct from total historical user records.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| free retained-user allowanceMRU is a billing metric distinct from total historical user records. | 50,000 MRUs per application | Free | ClerkAug 22, 2026 |
Why does this limit matter?
Migration sizing should use retained active users rather than only database row count.
This value is scoped to Free; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Compare active retained users by application with the current billing dashboard.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Plan pricing, add-ons, and retained-user calculation rules can change.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related