Kadeck Platform 7.1 and Kadeck Desktop 7
Kadeck Pipes, Topic Sets and the Flow Visualizer for Platform 7.1 and 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.
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.

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.
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:

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.
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.

Available in Kadeck Platform 7.1.
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.

Available in Kadeck Platform 7.1 and Kadeck Desktop 7. Saving topic sets and diagrams requires Desktop Professional or Platform.
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.

Available in Kadeck Desktop 7. Pushing a pipe requires Kadeck Platform 7.1 or later with a paid license.
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.
Several everyday dialogs have been reworked in both products:
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.
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.
The complete list of changes is in the release notes.