Migrating to Conduktor Scale
We want to extend our thanks to all our users who have helped shape Conduktor Desktop with their trust and feedback. After years of supporting you in utilizing Kafka, Conduktor Desktop is stepping aside at the end of 2025. Why? Because your needs have evolved—and so have we.
You can read the full announcement here.
Introducing Conduktor Scale
Rest assured, we have you covered with Conduktor Scale - a centralized, web-based platform built for modern data streaming, delivering the security, speed, and performance your team needs to stay ahead.
With the new Conduktor, you'll enjoy:
- Modern Web-Based Interface
- Enhances collaboration, maintainability, and user management through a centralized environment.
- Real-Time Monitoring and Alerting
- Integrations with messaging platforms and custom event triggers.
- Streamlined Workflows
- APIs, CLI, and Terraform support to improve GitOps workflows and infrastructure management.
- Powerful Automation Features
- Automatic connector restarts, SQL querying, and self-service tools.
- Deeper Integrations
- Works seamlessly with managed service providers like AWS and Confluent.
- Enhanced Security
- Granular Role-Based Access Control (RBAC), audit logging, and data masking for compliance.
Preparing to Migrate
Key Changes
Unlike the Desktop version, the new Conduktor platform is deployed centrally on a server (e.g. ECS, EKS) rather than installed on individual machines. This centralization offers:
- A single deployment to manage patches and upgrades
- Improved governance with visibility over user activities and data access
- Enhanced collaboration features such as shareable URLs and shareable consumer filters
High-Level Architecture
Conduktor consists of two core Docker images:
- conduktor-console
- Provides the UI and core features for managing Kafka resources
- conduktor-console-cortex
- Supports monitoring, alerting, and integrations with observability platforms
Key Dependencies
-
PostgreSQL Database
- Stores platform configurations, roles, and user accounts
- For this, we recommend using a managed service with automated backups, such as Amazon RDS
-
Storage for Metrics
- Local or object storage (AWS S3, Azure Blob) for historical time-series data
Deployment Options
Deploying Conduktor in a server environment is simplified using:
Licensing
If you are migrating to the Community edition of Scale, a license key is not required to start Conduktor. However, please note that Enterprise capabilities will not be available.
On the other hand, if you are migrating to Scale Standard or Scale Plus, you will receive a license key that should be configured as an environment variable.
Re-Integrating Your Kafka Clusters
Once your deployment is running, configure your Kafka clusters:
- Navigate to Settings > Clusters to add your cluster details
- Configure clusters once with sufficient privileges for all users
- Utilize our granular RBAC model for fine-grained access control
For an Infrastructure-as-Code approach, cluster configurations can also be managed via CLI or environment variables:
Inviting Your Team
You can invite users in two ways:
- Local Users: Add them directly within the application
- Single Sign-On (SSO): Integrate with your identity provider via LDAP or OIDC
For SSO configuration, set the required environment variables and refer to our documentation for popular identity providers:
Assigning Permissions
Leverage the RBAC model to assign permissions:
- Navigate to Settings > Users & Groups
- Assign Service Access to restrict application areas
- Assign Resource Access to control access to specific Kafka resources
Example: Grant viewer-only permissions to a topic or consumer group
Troubleshooting & Support
If you encounter any issues during migration, our support team are available to assist.
Thanks for choosing Conduktor!