Heroic Labs · Rate Limits

Heroiclabs Rate Limits

Heroic Labs' Nakama does not publish explicit per-endpoint rate limit thresholds as fixed product constraints. Because Nakama is an open-source server that can be self-hosted or run on Heroic Cloud with dedicated CPU and database resources, throughput is primarily bounded by the hardware allocation selected rather than by imposed API quotas. Key operational constraints documented by Heroic Labs include database connection pool limits, session token expiry windows, and configurable request timeouts. No DAU, MAU, or CCU limits are enforced on any Heroic Cloud plan.

Heroiclabs Rate Limits is the machine-readable rate-limit profile for Heroic Labs on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 6 rate-limit definitions.

Tagged areas include Game Backend, Multiplayer, Real-Time, WebSocket, and Matchmaking.

6 Limits
Game BackendMultiplayerReal-TimeWebSocketMatchmakingLeaderboardsSocial GamingOpen SourceLiveOpsgRPC

Limits

DAU / MAU / CCU Limits platform
Applies to all Heroic Cloud plans including Satori.
Session Token Expiry authentication
Developers can set autoRefreshSession=false and manage token refresh manually.
Request Timeout api
Database Connection Pool database
Self-hosted deployments can configure CockroachDB or any PostgreSQL wire-compatible database pool size independently.
WebSocket Connections real-time
Determined by server resource allocation; no hard published cap.
RPC Throughput api
Operators of self-hosted Nakama can configure reverse proxy rate limiting (e.g., via nginx or Envoy) as an additional layer.