EdgeDB · Rate Limits

Edgedb Rate Limits

EdgeDB/Gel does not publish explicit rate limits for its HTTP EdgeQL or GraphQL APIs in its public documentation as of June 2026. The HTTP API enforces a single-query-per-request constraint and does not support DDL or transaction commands. Connection and query throughput are constrained by the compute unit size of the provisioned instance. Standard HTTP 429 Too Many Requests responses apply if limits are enforced server-side.

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

It captures 2 rate-limit definitions, measuring queries_per_request and connections.

The profile also includes response codes documented for throttled.

Tagged areas include Rate Limiting, Database, and HTTP API.

2 Limits Throttle: 429
Rate LimitingDatabaseHTTP API

Limits

EdgeQL HTTP API - Queries Per Request key
queries_per_request · request
1
EdgeQL HTTP API - Concurrent Connections org
connections · usage
-1

Sources