Supported Kafka providers
Conduktor Console and Gateway are compatible with:| Provider | Console management | Gateway proxy |
|---|---|---|
| Apache Kafka (self-managed) | ✓ | ✓ |
| Confluent Cloud | ✓ | ✓ |
| AWS MSK | ✓ | ✓ |
| Redpanda | ✓ | ✓ |
| Aiven | ✓ | ✓ |
| WarpStream | ✓ | ✓ |
| Azure Event Hubs (Kafka API) | ✓ | ✓ |
What Conduktor adds to any Kafka provider
Regardless of which Kafka provider you use, Conduktor adds:- Unified UI: manage topics, consumers, schemas, and connectors from one interface across all clusters
- RBAC: fine-grained role-based access control per user, group, and resource, independent of provider-specific IAM systems
- Encryption: field-level and full payload encryption via Gateway interceptors, with KMS integration (Vault, AWS, Azure, GCP)
- Data masking: PII protection that masks sensitive fields for unauthorized users at display time
- Governance: schema adoption tracking, self-service coverage metrics, and audit logging
- Self-service: developers request Kafka access through governed workflows instead of tickets
Migrate between Kafka providers
If you’re moving between Kafka providers (for example, from self-managed Kafka to Confluent Cloud, or from Confluent to AWS MSK), Conduktor Gateway can help by acting as an abstraction layer:- Clients connect to Gateway, not directly to the Kafka cluster
- Swap the underlying Kafka cluster in Gateway’s config without reconfiguring clients
- Use Gateway failover to redirect traffic to a new cluster without downtime