ParadeDB · Rate Limits

Paradedb Rate Limits

ParadeDB is a set of PostgreSQL extensions consumed over the Postgres wire protocol, not a metered HTTP API, so it imposes no request-per-minute or token-style rate limits. Throughput is bounded instead by Postgres connection limits (max_connections), CPU/memory/IO of the host, parallel worker settings, and any limits set by the underlying managed-Postgres or ParadeDB Cloud provider. Specific values are deployment-dependent and not reconciled here.

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

It captures 3 rate-limit definitions, measuring connections, workers, and cpu_memory_io.

The profile also includes 2 backoff/retry policies defined.

Tagged areas include Search, Full-Text Search, Analytics, PostgreSQL, and Database.

3 Limits
SearchFull-Text SearchAnalyticsPostgreSQLDatabaseRate LimitingQuotas

Limits

Postgres Connections instance
connections
see deployment configuration (max_connections)
Bounded by Postgres max_connections and any pooler (PgBouncer) settings.
Parallel Workers instance
workers
see deployment configuration
Analytics queries scale with max_parallel_workers / max_parallel_workers_per_gather.
Compute Resources instance
cpu_memory_io
host-dependent
Query throughput is bounded by host CPU, memory, and IO, not an API quota.

Policies

No API Rate Limiting
ParadeDB exposes SQL over the Postgres wire protocol; it does not enforce HTTP request or token rate limits.
Resource-Bound Throughput
Tune max_connections, work_mem, and parallel-worker settings, and size the host or managed plan to the workload.

Sources