Latest releases
If a month is not listed, no releases were published during that month.
Data Foundation
September 2026
September 23
New Feature
Introduced data discovery in the data registry: Data catalog administrators can now search regional data planes for unregistered datasets, review schema details, and register tables in one step. This helps make more trusted data available for analytics and dashboards while preserving existing role-based access controls.
August 2026
August 19
Enhancement
Added new filters and dashboards for incoming data monitoring: Data operations engineers can now filter incoming data by contact ID, customer name, and hostname, and access three new dashboards: Incoming Vulnerability Management Data, Incoming Mainframe Data, and Incoming Security Healthcheck Data, for improved visibility and analysis.
May 2026
May 13
Enhancement
Improved multi-tenancy filtering and tenant scoping: A new multi-tenancy filter has been added at the query layer with support for dual lookup keys, along with table-level tenant metadata to better define tenant scope. These updates improve filtering accuracy and prevent incorrect tenant tagging, especially for global tables.
May 6
Enhancement
Enhanced broker registration to GCP IAM: Broker registration to the Global Control Plane (GCP) and Identity & Access Management (IAM) now includes initiating the migration of access policies from the Distributed Control Plane (DCP) to GCP, supporting a unified IAM model. This enhancement helps improve consistency and governance of access across services. The update applies to data engineers using standard Bridge access groups and does not introduce any immediate change to existing user access.
Enhancement
Bridge Regional Plane apps updated: The Bridge Regional Plane applications have been aligned with the Argo Deployment Framework to ensure consistency and streamline operations. Integrating AIOps capabilities is critical for proactive monitoring and management in the Kyndryl Platform Region (KPR) environment, with the aim of significantly improving system reliability and operational efficiency.
New Feature
Tokenization and detokenization capabilities are now available for specific Elasticsearch indices: Kyndryl Bridge introduces tokenization and detokenization to protect sensitive data by enforcing authorization, encrypting data, and securely storing it via Manetu. Sensitive fields are replaced with UUID/IRI tokens, enabling secure access, controlled detokenization for authorized users, and improved compliance through seamless tokenization of existing data. Manetu secures sensitive information by validating authorization, encrypting it, and safely storing it. It uses unique Internationalized Resource Identifiers (IRIs) for externally stored anonymized tokens. A policy engine regulates access by replacing sensitive fields in Elasticsearch with UUID/IRI tokens, while only Manetu retains the encrypted data. Authorized users can detokenize data as needed, and Logstash helps migrate and tokenize existing data to improve security and compliance.
March 2026
March 11
New Feature
The Data Registry page is now available in Kyndryl Bridge Data Foundation: Bridge users can easily access and explore domains, subdomains, and tables in one place. There is an option to create a table to visualize better how the data is generated and how the indices are displayed. This capability saves time by reducing the need to search across multiple systems. It also improves data analysis across other applications that leverage Data Foundation, enabling the creation of detailed query layers.
February 2026
February 25
New Feature
The data registry page is now available in Data Foundation: Users can easily access and navigate domains, subdomains, and tables from different catalog types within one interface. The data registry provides information from Data Lake, Elasticsearch, and MongoDB, which simplifies data discovery and enhances visibility into access policies and schema versions. This streamlined approach saves time by eliminating the need to search through multiple systems. Additionally, it enables users to better analyze data from other applications, allowing them to create comprehensive query data layers.
Enhancement
Extensions Console UI enhancements: The extensions console has been updated to enhance the user experience, in accordance with Shidoka v2 guidelines. The extensions instance page has introduced a new field for custom extension environment variables. The catalog settings feature has improved logic and has been rebranded as the extension's registry. Furthermore, UI enhancements have been implemented to deploy extensions within the Instance creation wizard to improve the common catalog experience. Users can now use a view-only experience, edit draft extensions, and have date-time field labels display correctly while browsing extensions in the UI. Extension instances can now be rolled back to the previous release if they fail during an upgrade.
Enhancement
Extensions Service enhancements: The extensions service has also been updated to comply with Shidoka v2 guidelines. The database schema setup has been automated for improved efficiency when the extension service starts. The extensions service now allows deleting shared instances of an extension along with their associated subscriptions. Additionally, it includes a feature to check for duplicates, which displays the name and an error message if duplicates are found.
Enhancement
Extensions Controller enhancements: The extensions controller application now supports new Azure-scheduled T-shirt sizes for extensions. The default persistent volume size has also been reduced from 10 Gigabytes to 1. Significant fixes were also applied to support special characters within JSON fields passed from users of the extensions UI.
Orchestration Catalog
September 2026
September 30
Enhancement
Orchestration Catalog integrates with Bridge Access Management: Orchestration Catalog Services now connects with Bridge Access Management during onboarding. This enhancement enables tag-based access control so policies and roles can use access tags for more granular automation access.
Learn more: Access TagsAccess Tags