Axual 2025.3 release introduces KSML 1.1 integration for automated stream processing deployment, group-based resource filtering for multi-team governance, and experimental MCP Server for AI-driven platform operations. Includes JSON schema support, Protobuf processing (beta), and enhanced audit tracking for enterprise Kafka implementations.

Axual 2025.3 addresses the governance complexities that emerge as Kafka implementations scale across enterprise teams.
As streaming platforms grow beyond single-team deployments, maintaining visibility and control becomes increasingly challenging. This release focuses on streamlining stream processing deployment, enhancing resource visibility, and exploring AI-driven platform interaction.
The integrated KSML 1.1 workflow enables teams to deploy stream processing applications with automatic authentication configuration and multi-format schema support, reducing deployment overhead while maintaining centralized governance.
Enhanced self-service capabilities provide group-based resource filtering and expanded audit tracking, ensuring teams can manage their resources independently while maintaining visibility across the platform.
Additionally, our experimental MCP Server allows natural language interaction with your streaming platform, enabling teams to query resources and deploy applications through AI agents while preserving authentication and governance controls.
These capabilities build on Axual's foundation of enterprise streaming governance, providing the control and visibility required for mission-critical data infrastructure.
KSML is a wrapper language and interpreter around Kafka Streams that lets you express any topology in a simple YAML syntax. Simply define your topology as a processing pipeline with a series of steps that your data passes through. Your custom functions can be expressed inline in Python. KSML reads your definition and constructs the topology dynamically via the Kafka Streams DSL.
V2: KSML is a declarative wrapper around Kafka Streams that enables teams to define streaming topologies using YAML syntax instead of compiled Java code. Custom processing functions are written in Python and embedded directly in the topology definition, allowing iteration without deployment cycles.
Breaking change: Aggregate operations now require explicit state store configuration. See the migration guide in the complete release notes.
You can read the complete KSML 1.1 release notes here or dive into the documentation.
KSML expands access to stream processing across development teams. The YAML-based definitions and Python functions eliminate Java compilation requirements, enabling faster iteration on streaming topologies.
Its main benefits are:
An example of a KSML Temperature Monitoring app is shown in the following picture:

The KSML 1.1.0 integration with Self-Service automates authentication and connection configuration for KSML applications. Application owners can select their preferred authentication method (SASL credentials or mTLS certificates), and the platform automatically provisions the appropriate Kafka bootstrap servers and security configuration. The integration supports all Schema Registries available in KSML 1.1.0, enabling KSML applications to process messages in multiple schema formats.

This integration benefits teams running KSML applications through Axual’s managed platform. Application owners gain automated security provisioning and multi-format schema support without manual bootstrap server configuration or credential management. Platform administrators maintain centralized governance over authentication methods and schema registry access while enabling self-service deployment of stream processing applications.
As streaming platforms grow, tracking resource ownership across teams becomes complex. Groups accumulate topics, applications, and connectors over time, making cleanup operations and compliance audits difficult. The group owned resources view provides a filtered inventory of all resources owned by a specific group. This enables teams to quickly assess their resource footprint, identify unused resources and maintain an accurate view of their streaming infrastructure ownership.

Group members use this view to manage their team's streaming resources and perform regular cleanup of deprecated topics and applications. Platform administrators gain visibility into resource distribution across teams for capacity planning and governance reviews. The consolidated view also supports compliance requirements by documenting which organizational units own specific data streams and processing applications, maintaining clear ownership records for audit purposes.
The Axual MCP Server implements the Model Context Protocol, enabling AI agents like Claude, Cursor, and other MCP-compliant clients to interact with Axual's management API through natural language. This experimental integration allows teams to perform platform operations through conversational interfaces while maintaining Axual's authentication and authorization controls. The MCP Server translates natural language requests into authenticated API calls, enabling tasks such as topic creation, application registration, KSML deployment, and resource queries without directly invoking the API. All operations respect existing role-based access controls and audit logging, ensuring governance policies are enforced regardless of the interface used. The server is available on request for both Axual Cloud and self-managed Axual Platform deployments.
Detailed demo videos will be available in the near future.
The Axual MCP server is built for anyone who needs to operate, automate, or prototype workflows against Axual’s streaming platform without wrestling with low-level APIs:
In our release notes, you will find other, more minor, updates to our product, which we are continuously improving with your feedback.
Inspired by what you've read? Facing challenges with Kafka in an enterprise environment? We're here to assist. Here are your next steps:
Request a demo and talk to our experts
Axual 2025.3 provides the governance controls and operational visibility required for enterprise streaming platforms that span multiple teams and compliance requirements. The enhanced self-service capabilities, integrated KSML workflows, and expanded audit tracking ensure your Kafka infrastructure maintains control without sacrificing development agility.
Ready to strengthen governance across your streaming infrastructure? Contact us today to explore how Axual 2025.3 addresses the compliance and operational challenges facing enterprise Kafka implementations.