Conduktor · Rate Limits

Conduktor Rate Limits

Conduktor Console and Gateway are self-hosted (and Conduktor-managed) products, so the Console and Gateway REST APIs are not metered behind a public per-account rate limit the way a SaaS API would be; throughput is bounded by the deployment's own resources. Conduktor Gateway, however, can itself enforce Kafka client rate limits and quotas through safeguard interceptors (for example produce/consume rate limiting). Specific numeric limits are deployment-defined and not reconciled in this artifact.

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

It captures 3 rate-limit definitions, measuring requests and kafka_operations.

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

Tagged areas include Apache Kafka, Streaming, Data Governance, Kafka Management, and Gateway.

3 Limits Throttle: 429
Apache KafkaStreamingData GovernanceKafka ManagementGatewayRate LimitingQuotasThrottling

Limits

Console REST API deployment
requests
see deployment configuration
Bounded by the self-hosted/managed Console deployment's resources; no documented public per-account limit.
Gateway Admin REST API deployment
requests
see deployment configuration
Bounded by the Gateway admin endpoint's resources; no documented public per-account limit.
Gateway Safeguard Rate Limiting cluster
kafka_operations
configurable via interceptor
Gateway safeguard interceptors can rate-limit produce/consume operations and enforce client quotas; limits are set per interceptor.

Policies

Self-Hosted Capacity
API throughput is governed by the resources allocated to the Console and Gateway deployments rather than a vendor-imposed quota.
Gateway-Enforced Quotas
Operators can configure Gateway interceptors to enforce Kafka client rate limits and quotas on traffic passing through the proxy.

Sources