Skip to main content

​
Check out other resources

​
Support portal

Conduktor’s support portal lets you:
  • report an issue or raise a request - this is the quickest way to get in touch
  • check progress and manage your tickets
  • Check out knowledge base articles
Support Portal
When reporting an issue, please give us as much context and detail as possible. The more information you provide, the faster we’ll diagnose the issue and offer a fix/suggest a workaround.

​
Data privacy using Conduktor

​
Configuration: on your disk

Conduktor Gateway is installed on your infrastructure and stores its configuration on your disk and Kafka cluster. It’s not stored or sent anywhere else. Conduktor Gateway will store usernames and passwords you supply to connect to different technologies such as Apache Kafka, Schema Registry etc.

​
Data: not sent anywhere

The message data only moves between your Conduktor Gateway and your Apache Kafka clusters and ecosystem (such as schema registry, Kafka Connect, ksqlDB). This is never sent anywhere else.

​
Where is Conduktor installed?

Conduktor Gateway runs as a Docker container that you can deploy using on any Docker or Kubernetes type environment, either self-hosted or cloud based.

​
Product telemetry

Console and Gateway report deployment facts, health signals and usage counts back to Conduktor so we can support you proactively. Kafka record data and credentials are never included. Find out what product telemetry contains and why we collect it.

​
Image vulnerabilities

Our engineering pipelines scan our images and their dependencies for known vulnerabilities (CVEs, Common Vulnerabilities and Exposures). The Gateway image and its software bill of materials (SBOM) are scanned on every pull request, Gateway is checked for new CVEs every night and Renovate keeps dependencies up to date. Our base images are rebuilt every night and their scan results are public in conduktor/container-images . We review scan results before every release and fix vulnerabilities according to our vulnerability management policy. An independent company runs a penetration test of Console and Gateway every year, and we’re happy to work with customers who run their own tests.

​
Security and compliance

An independent auditor examines our security controls every year in a SOC 2 Type II audit. We share the latest SOC 2 report and an executive summary of our latest penetration test under a non-disclosure agreement (NDA): ask your Conduktor contact. Our incident response plan sets out how we handle security incidents: each one is logged, classified and tracked through to resolution. Read our blog about SOC 2 . The credentials entered in Console are stored as secrets that are encrypted to/from the database (via AES encryption algorithm). The key is accessible only via your internal DevOps team.

​
Retired products

​
Conduktor Playground

Conduktor Playground, a free hosted Kafka cluster, has been retired. To follow a Kafka course or try Conduktor, run Kafka and Console on your machine with the quick start, then point your Kafka clients at localhost:19092 instead of cluster.playground.cdkt.io:9092. The local cluster has no security configured, so you don’t need the SASL and SSL settings from your playground.config file.

​
Conduktor Desktop

Conduktor Desktop has been retired. Move to Conduktor Console.