All your streams.
One screen.
40,000+ developers govern, discover, process, and integrate data streams across multiple Kafkas, using Lenses.
Let developers do their thing
Unify data access and permissions globally
Have confidence by applying the most powerful and granular permission model across all streaming technologies, with Multi-Kafka IAM and Streaming Data Policies:
From opening up all topics in dev, to assigning a team to manage a type of resource in production.
Find and explore streaming data across domains, with SQL
Data can stream, but it can’t hide with Lenses.
Teams can discover data across different departments, compare topics across domains, and troubleshoot data to use in downstream applications with Global Topic Catalog and SQL Studio.
Prepare data for easier consumption with SQL
Shifting your development left means earlier data ownership. Give developers a common language for preparing streaming data with SQL Processors.
Transform, reshape, aggregate and join streams, then run them across your entire streaming ecosystem. Boom.
Deploy data streams independently, anywhere your business needs
Don’t wait to integrate your streaming data across your organization, and check connectors are working. Do it yourself.
Manage connectors and consumer groups, and monitor their health from one screen.
Bring your own architecture
Developers
Platform admins
Technology leaders
Lenses MCP FAQ
Companies replicate Kafka clusters for several reasons: disaster recovery and business continuity, data sharing between teams or external partners, vendor migration to avoid lock-in, workload migration between environments (on-prem to cloud), and data subsetting for testing with production-like data.
Read more >Kafka replication typically works by consuming messages from source topics and producing them to destination topics, often with additional features like schema registry synchronization, consumer offset translation, and topic configuration replication.
Read more >MirrorMaker 2 (MM2) is the open-source standard but requires complex Kafka Connect setup and lacks modern features. Commercial alternatives like Confluent Replicator offer support but inherit MM2's complexity. Cloud-native solutions like AWS MSK Replicator are easier but vendor-specific.
Read more >For K2K, yes. But not all other solutions do. While some tools like MirrorMaker 2 and Confluent Cluster Linking support exactly-once semantics, others like Confluent Replicator and AWS MSK Replicator do not, potentially leading to duplicate messages.
Read more >Lenses K2K automatically handles schema registry synchronization between clusters, including different schema registry types. It manages schema evolution and compatibility checks, supporting Avro, Protobuf, and JSON schemas.
Read more >Lenses K2K is a java-based application designed to run on Kubernetes, ideally close to the target Kafka cluster that you are replicating to.
The Lenses Developer Experience will help you identify the correct Kubernetes cluster to deploy to, and do all the deployment.
Read more >There is a free version that's restricted and accessible to download. A restricted version will also be included in Lenses Community Edition. For all enterprise features, you need to be a subscribed Lenses customer. Contact our teams for more information on pricing.
Request quote >K2K is available as a standalone container. But you will be responsible for the deployment, governance, and monitoring. We recommend the simplicity and power of managing K2K through the Lenses Developer Experience, found in Lenses 6.
Try Lenses for youself
20 minute demo
Get a guided tour of Lenses
Receive a trial key to install on your clusters
Perfect for production and large-scale streaming deployments



