Kadeck Platform 7.1 and Kadeck Desktop 7

Kadeck Platform 7.1 and Kadeck Desktop 7

Kadeck Pipes, Topic Sets and the Flow Visualizer for Platform 7.1 and Desktop 7.

Today, November 20, 2026, we are announcing Kadeck Platform 7.1 and Kadeck Desktop 7. Both releases bring Kadeck Pipes, Topic Sets and the Flow Visualizer to teams and individual engineers who work with Apache Kafka, together with redesigned dialogs for connections, topics and schemas. Kadeck Platform 7.1 also tells your team when records arrive in a topic, or stop arriving.

Repair a dead letter queue without writing a consumer

A Kadeck Pipe writes the records of a topic to another topic, processed the way a topic view shows them. To repair a dead letter queue, open the topic in the Data Explorer, correct the records with the JavaScript Processor and the filters you already use, and click Pipe in the toolbar with the original topic as the target. The record list of the view is the preview of what the pipe writes. There is no repository, build pipeline or deployment involved.

Before a pipe starts, Test run takes one record through decoding, processing and encoding and shows the result of every step. Nothing is written. A pipe set to Run once completes when it reaches the end condition of the view or the end of the topic; Keep running continues with every record that arrives. An optional lineage header, kadeck.pipe, marks each written record with the name of the pipe.

The Convert to Kadeck Pipe dialog with orders.dlq as source, orders as target, Run once selected and a test run result
A topic view of orders.dlq becomes a pipe that writes the corrected records back to orders.

Available in Kadeck Platform 7.1 and Kadeck Desktop 7. In Kadeck Desktop, a pipe on your computer runs once, while the application is open.

Deliver filtered or reshaped records to another topic or cluster

A pipe that keeps running turns a view into a standing data flow. It reads one source topic and writes to one target topic, on the same connection or another one. The view decides what arrives: rename attributes, drop fields, write with a different codec, or pass on only the records that match a condition.

Pipes are built for operation by a team:

  • Delivery: a pipe delivers at least once. It commits its position only after the target cluster has acknowledged the records.
  • Failed records: a record that cannot be decoded, processed, encoded or produced does not stop the pipe. It is dropped or written to a dead letter topic, with headers that name the stage and the reason.
  • Data protection: a pipe applies the data masking and protection policies of its author and writes the masked values. The administration setting Enforce data protection is on by default.
  • Control: the new Pipes page lists the pipes of all clusters you have access to, with their state, source and target, and lets you pause, resume, stop or duplicate them. The details of a pipe show throughput and lag. Pipes can also be created and controlled through the Public API, and their lifecycle is recorded in the audit log.
Details of a running Kadeck Pipe from the topic customers to crm.customers on another cluster, with record figures and a dead letter topic
A pipe that keeps running delivers masked, reshaped records to another cluster and sends failed records to a dead letter topic.

Available in Kadeck Platform 7.1. Kadeck Platform Free includes one active pipe at a time; alerts for a failed, paused or lagging pipe are part of the paid editions.

Know when a pipeline fails or goes silent

A Topic Data Arrival Alert counts the records arriving in a topic over a rolling time window and notifies your team when the count crosses a threshold. Set a More than threshold on a dead letter queue, and the team hears when failed records start to arrive. Set it to Less than 1 record in 10 minutes on a business topic, and you learn that a producer or an upstream pipeline has stopped.

Alerts are configured per topic from the Data Catalog: choose Configure Alerts, select where to notify, and set the threshold, the time window and a cooldown period that keeps one incident from producing a stream of messages. Notifications go to Slack, Microsoft Teams, PagerDuty or email. Together with a pipe that filters the records matching a condition into their own topic, an alert can watch for any kind of record you define.

A Topic Data Arrival Alert on the orders.dlq topic: notify the operations Slack channel when more than 1 record arrives within 1 minute, with a 15 minute cooldown.
An alert on a dead letter queue notifies the team when failed records arrive.

Available in Kadeck Platform 7.1.

Follow a record across topics

Topic Sets group up to eight topics or views in the Data Explorer. You can look at each view on its own or select All combined to read the records of all views in one list, sorted by timestamp by default, with a Topic column and a color per view. Filters and the JavaScript Processor apply to the combined view or to each view individually.

The Flow Visualizer turns a topic set into a diagram. You arrange the topics on a canvas and connect them through the applications between them. A trace then follows one value through the set: a record key, a header, a value attribute or an OpenTracing trace ID. Kadeck numbers the matching records on the topic nodes in order, and a click on a number highlights the record in the list.

A topic set of orders, payments and shipments in the Flow Visualizer, with a trace numbering one record key across the three topics
A trace by record key numbers the matching records on their way through the topics of a set.

Available in Kadeck Platform 7.1 and Kadeck Desktop 7. Saving topic sets and diagrams requires Desktop Professional or Platform.

Start a pipe on your desktop and let the Platform run it

In Kadeck Desktop 7, a pipe can run once on your computer, or you can push it to your team's Kadeck Platform, where it keeps running without Kadeck Desktop.

To push pipes, you link a connection in Kadeck Desktop to the same cluster on Kadeck Platform: enter the address of the Platform and an API key on the new Kadeck Platform tab of the connection. The test run and the pipe are then executed by Kadeck Platform with the rights of the API key's user, and that user's data masking policies always apply. Pipes on the Platform that read from or write to a linked cluster appear in the Pipes folder of Kadeck Desktop.

Kadeck Desktop pushing a pipe from orders to orders.high-value to Kadeck Platform, where it is shown as running
A pipe created in Kadeck Desktop is pushed to Kadeck Platform and keeps running there.

Available in Kadeck Desktop 7. Pushing a pipe requires Kadeck Platform 7.1 or later with a paid license.

Connect a managed Kafka service in fewer steps

Adding a connection now starts with your provider. New connection wizards for Confluent Cloud, Amazon MSK, Aiven, Redpanda, Azure Event Hubs and IBM Event Streams ask for what the provider hands out and fill in the rest. Any other Apache Kafka cluster is set up as before.

The connection dialog itself has been redesigned, with one line per setting and Schema Registry, Kafka Connect and JMX each on their own tab.

Available in Kadeck Platform 7.1 and Kadeck Desktop 7.

Review schema changes and tune topics

Several everyday dialogs have been reworked in both products:

  • Schema details with version compare: see the fields of a schema, step through its versions, and compare any two of them line by line and field by field.
  • Topic dialog: a live preview of the topic, partitions and replicas with a click, and cleanup policy and retention as plain choices.
  • Topic configuration: common settings such as cleanup policy, retention and compression as one-click controls, a searchable list of all other settings, and a reset to the cluster default.
  • Produce dialog: new producer settings for compression and acknowledgements.

Kadeck Desktop 7 also has a new Settings page with a search over all settings, and the Lineage tab of a topic now draws its producers and consumers in the look of the Flow Visualizer.

Available in Kadeck Platform 7.1 and Kadeck Desktop 7, except where noted.

Availability

Kadeck Platform 7.1 and Kadeck Desktop 7 are available now. Kadeck Desktop for Windows, macOS and Linux and the Kadeck Platform container image can be obtained at kadeck.com/get-started.

  • Plans: the Free plan covers two clusters, up to 10 users on Kadeck Platform Free, and one active pipe. Desktop Professional is $19 per user per month, billed yearly. Platform is $32 per user per month from 10 users, billed annually. See pricing for the full comparison.
  • Naming: Kadeck Teams and Kadeck Enterprise are now called Kadeck Platform, and Kadeck Teams Free becomes Kadeck Platform Free. Only the name changes; existing licenses continue to work.
  • Upgrading from Kadeck 6: the upgrade to Kadeck Platform 7 is free for Kadeck Platform 6 users and cannot be undone. Back up the database and read the upgrade article first.

The complete list of changes is in the release notes.