Tier Reference
Rate-limit tiers applied per credential, per environment. Free / standard / premium / unlimited.
Tier Reference
Each credential carries an independent rate_limit_tier. Limits are
applied per-credential, so your staging integration tests can burst
without impacting your production quota.
| Tier | RPM | RPH | Burst | Notes |
|---|---|---|---|---|
free | 60 | 500 | 10 | Default for new dev credentials. |
standard | 600 | 10000 | 60 | Staging default (PRD-161 §9 Q1). |
premium | 6000 | 50000 | 300 | Production apps with growing traffic. |
unlimited | — | — | — | No rate-limit enforcement. Dangerous — requires override + super-admin justification. |
Exact RPM/RPH/burst numbers are maintained in
apps/backend/src/infrastructure/throttler/rate-limit.constants.ts and
may be tuned without notice — this table is indicative.
How to request a tier change
Tier assignments are super-admin-only. Contact your Emofy account rep with:
- App name + environment (
dev/staging/production) - Expected peak RPM
- Business justification (shipped feature, customer tier, etc.)
The super-admin submits the change via the admin matrix UI; you'll see the new tier reflected in the developer portal's OAuth tab within a minute. All tier changes are audit-logged with actor + reason.
unlimited tier
unlimited removes rate-limit enforcement entirely. It requires an
explicit override=true flag on the PATCH + a super-admin reason. Abuse
is detectable in the audit log; if you're considering it, prefer raising
the premium numerics first.