Sequin · Rate Limits

Sequin Io Rate Limits

Sequin does not publish fixed numeric rate limits for the Management API. On self-hosted deployments, throughput is bounded only by your own hardware - Sequin sustains roughly 50k operations/sec (~40 MB/s) in published benchmarks. On Sequin Cloud, sustained streaming throughput is governed by your plan's monthly change-record / data-volume allowance rather than by a per-minute request cap. Data-plane delivery (to sinks and via the Sequin Stream pull API) is controlled by per-sink configuration such as batch size, max concurrency, and backpressure rather than a global limit.

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

It captures 5 rate-limit definitions, measuring requests, operations, records, and messages.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Change Data Capture, CDC, Postgres, Streaming, and Rate Limiting.

5 Limits Throttle: 429
Change Data CaptureCDCPostgresStreamingRate LimitingQuotas

Limits

Management API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the Management API.
Self-Hosted Throughput deployment
operations
hardware-bound (~50k ops/sec, ~40 MB/s benchmarked)
Constrained by your own infrastructure, not by Sequin.
Cloud Throughput Allowance account
records
per plan
Sequin Cloud meters monthly change records / data volume per plan tier.
Sink Delivery Throughput sink
messages
configurable
Governed per-sink by batch size, max concurrency, and backpressure settings.
Sequin Stream Pull Batch consumer
messages
configurable via batch_size
The /receive endpoint returns up to batch_size messages per request.

Policies

Backpressure
Sequin applies backpressure when a destination cannot keep up, rather than dropping change events.
Exactly-Once Processing
Change events are delivered with strict ordering and exactly-once processing guarantees, with ack/nack redelivery on the Sequin Stream pull API.
Backoff Strategy
Clients of the Management API and Stream pull API should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources