-
Notifications
You must be signed in to change notification settings - Fork 2
Quotas Tiers and Entitlements
This is an operator page. It explains what limits a tenant carries and how a default self-hosted deployment stays out of their way.
Every tenant sits in a tier class. The class sets the tenant's quotas, such as the number of open sessions and the amount of stored data. Higher classes carry larger limits. The control panel shows a tenant's current usage against its limits.
Some features are gated by an entitlement rather than a numeric limit.
feature_grants records what a tenant is entitled to, for example dedicated
game-server allocation. A tenant without the grant cannot use the feature even
when the server has it enabled. This is how billing and plan level map to
feature access.
A default self-hosted deployment does not enforce quotas. New tenants are created
unenforced unless you set QUOTAS_ENFORCE_NEW_TENANTS=true, and existing tenants
stay as they are. Run your own hardware, and the limits do not apply until you
choose to turn them on.
Enforcement matters mainly on a managed deployment, where each tenant pays for a tier and the entitlement API applies the tier and grants from an external billing service.
A tenant admin can request a quota change from the control panel. An operator reviews and applies it. The request flow keeps a record of who asked for what, so each raise is reviewed and logged.
See Configuration Reference for the enforcement and entitlement-API switches.