Already running FERN? A version-aware upgrade notification appears in the same table row when a newer match model is available. One click applies the latest AI/ML improvements and unlocks the new mode selector — no downtime, no guesswork. Skip the toggle and match on your terms. For more information, see FERN with Modes.

We've also added dozens of new address output fields and status indicators, so you can inspect how each component was verified or corrected. This gives you richer insight into address cleansing results across regions and formats.

For more information, see Address cleanse options, Mapping output attribute, and Address cleansing status fields.

Assign groups to entity types to organize them by data domain. In the Hub UI, grouped entity types now appear together when searching records or creating a new profile — making it easier to navigate and manage your data model. For more information, see topic Entity type grouping.

With this release, you now have two options:

• Reltio Developer MCP Server – Open-source and self-hosted. Ideal for prototyping and trials.
• Reltio AgentFlow MCP Server – Fully managed by Reltio. Delivers secure, governed, and role-aware access to trusted data for AI agents and orchestration tools without the infrastructure burden. Designed for enterprise production scale.

For more information, see Reltio Model Context Protocol (MCP) Server at a glance, Reltio AgentFlow™ MCP Server, Authentication flow for the AgentFlow MCP Server, and MCP tools.

For more details, see Group segments by folders.

The connector now supports client credentials-based authentication, offering a more secure alternative to Basic Auth.

For more details, see Catalog Reltio metadata in the Collibra physical layer.

For more details, see Reltio Address Cleanser update - Jun 2025.

For more details, see Configuring Azure Private Link.

Just create segments in the Hub, then set up accounts, integrations, and destinations using the Activation service to leverage Reltio Integration Hub (RIH). Activation handles the rest, from syncing to logging, on your schedule.

For more details, see Activation service for segmentation.

You asked, we listened: Reltio ID is now a General Availability (GA) feature!

Reltio ID is a durable, system-managed identifier automatically assigned to each new entity when Reltio ID generation is enabled at the entity type level. IDs are generated during entity creation via API, UI, or Data Loader. For existing entities, Reltio IDs can be generated using the GenerateReltioIdTask.

For more information, see Reltio ID overview.

All uploads are already optimized, but this enhancement delivers extra power for the biggest jobs in AWS environments. Support for other cloud providers to follow.

For more information, see Data Loader at a glance.

Still using the Monitoring Statistics page in the Tenant Management app? Heads up — we're retiring it on June 16, as previously announced in this notice.

For more details, see Usage Reporting at a glance.

For more information, see Bulk update relation start or end entities.

For more information, see Get Entity and Get Relationship.

This enhancement helps enforce internal policies, support compliance requirements, and maintain a clean, transparent process history.

Note that this feature isn't currently supported in the Hub UI. If a workflow requires mandatory comments at startup or during task actions, attempts to initiate or act on the workflow via the Hub UI fail, as users cannot enter comments in that interface.

For more information, see the commentRequired property in Business process definition overview and Enter a mandatory comment.

For updated instructions, see Create DVFs in the Data Modeler.

Now, you'll have a full weekend to validate changes in TEST before they reach PRD. This 2-stage deployment replaces our previous 3-stage model, simplifying your update flow and giving your teams more time to prepare.

This change takes effect Friday, June 6, 2025.

For more details, see Deployment process.

• View profile audience details on the Segments page
• Check entity segments on the Profile page
• View all tenant segments in the Profile Stats Dashboard

For more information, see topics Create a segment, Segments facet and Data insights operation.

For more details, see Reltio Data Pipeline for Snowflake architecture.

This change makes it easier to manage and document distributed task behavior consistently, no more switching between parameter names across jobs.

For more information, see topic Bulk Delete Entities.

We've introduced a new capability in the Reltio Lightspeed™ Data Delivery Network that lets you enable synchronous predicate index updates — so your data changes are instantly available through Reltio Lightspeed queries.

For more information, see Understanding synchronous updates in Reltio Lightspeed.

If your current custom policy is out of range, you won't be able to change security parameters until the password length is corrected. Ensure to configure this parameter correctly the next time you make changes to the password policy.

For more information, see Set a customer password policy and for any queries, Contact a support person.

This makes configuring roles and policies across tenants faster and less error-prone.

For more information, see Generate external ID.

You can now run Data Validation Functions (DVFs) on specific source systems, not just Operational Values. This helps you pinpoint and fix data quality issues at the source.

Use the new applyOn setting to target crosswalk values from selected sources. Default behavior remains unchanged for existing DVFs.

For more information, see topics Apply data validation functions at crosswalk level and Define Data Validation Functions.

You now have more control over attribute resolution when fallback strategies are triggered. The sourcesForOV parameter is now supported within fallback survivorship strategies. This lets you specify a different set of source systems to use for fallback logic — separate from those used in the primary strategy.

Here's what's new:

• You can define a sourcesForOV list specifically for the fallback strategy.
• The fallback list can differ completely from the primary strategy's sourcesForOV.
• When fallback is triggered, only the sources listed in the fallback sourcesForOV are used.
• If sourcesForOV is not defined for the fallback, the system continues to use its existing fallback behavior.
• If earlier fallback levels filtered out values, only those filtered values are considered — but with the full original set of their crosswalks.
• If a fallback level returns no winners, the filtered values from the last level with non-zero winners are reused — again with their full original crosswalks.

This enhancement provides more precise control over trusted source prioritization, especially in complex data stewardship scenarios involving conditional survivorship.

For additional information, see Survivorship Rules.

The Reltio Model Context Protocol (MCP) Server is now available, offering a secure, open-standard API gateway that enables AI agents, large language models (LLMs), and orchestration tools to interact with trusted master data in real time. Think of MCP as the USB-C for AI agents — plug in and go.

With both open-source and fully managed editions, the MCP Server simplifies integration by eliminating the need for custom connectors or static exports. It supports Agentic capabilities, allowing AI agents to autonomously perform data-related tasks such as resolving matches, enriching profiles, or validating records.

This release accelerates AI adoption by streamlining secure data access, reducing operational costs, and grounding AI in trusted, up-to-date data.

For more details, see Reltio Model Context Protocol (MCP) Server at a glance.

To enable this behavior, check back later for details.

We're shifting from three to two major product releases each year. This updated cadence allows us to deliver more impactful features, improve planning, and reduce disruption. You can expect major releases to arrive in April and October going forward.

For details on upcoming preview and general availability dates, see our release schedule.

If you have any questions, please reach out to Support.

We're deprecating the Monitoring Statistics page in the Tenant Management app. Starting June 9, 2025, this page will no longer be available.

Looking for tenant usage data? You'll find everything you need — and more — in the Usage Reporting app. It delivers richer metrics, better filters, and a more intuitive experience.

To help with the transition, we're placing a one-time banner on the Monitoring Statistics page:

For more details on this deprecation, see Monitoring Statistics – June 2025.

Ready to meet better insights? Find out more in Usage Reporting at a glance.

You can now build custom dashboard under Insights within the Reltio Integration Hub, making it easier to monitor flow executions, identify errors, and gain real-time insights — all in one place for faster troubleshooting and smoother integrations.

Insights is available for the standard delivered role ROLE_INTEGRATION_CUSTOMER_ADMIN and you can also control its availability to users with Custom roles to access the Integration Hub.

Come back soon as we're adding the details to Integration Hub navigation.

This week's release is dropping on April 8 instead of April 7. Thanks for bearing with us as we took an extra day to lock everything in.

We've enhanced the Reverse Geocoding feature to return multiple address results for a given set of geographic coordinates. You can now define a search radius and maximum number of results — giving you the flexibility to apply custom logic to select the most relevant one. This improvement helps you handle ambiguous or overlapping locations with greater precision. For more information, see topic Get addresses with geographic coordinates.

Contact your Account Executive or Customer Success Manager to discuss the best offering for your business.

We are enhancing security by transitioning from AWS access key and secret authentication to IAM role-based authentication using AssumeRole to access Reltio-owned AWS resources. This change aligns with AWS best practices, reducing credential exposure and improving access management. If you currently use AWS access keys to access Reltio-owned AWS resources, we recommend transitioning to IAM roles as soon as possible.

For more details, see AWS access key and secret in favor of IAM roles for Reltio-owned resources.

We've introduced a new generationLogic parameter, named generateUidWhenAllOvMissing, to improve surrogate crosswalk key generation. Previously, when all attributes for an entity lacked operational values (OVs), the system generated an MD5 hash using null values, leading to potential duplicates. Now, with this new parameter, a UUID is generated instead, ensuring unique keys even when all OV values are missing.

This update helps prevent unintended entity merges and improves data consistency. It's available in Surrogate Crosswalks configuration for all tenants.

For more details, see Configuring surrogate keys.

We've simplified how you load interactions into your tenants. Previously, to load interactions, you needed to define a schema. Now, you're able to load interactions with no defined schema. This means that you aren't required to map attributes, allowing you for a quicker setup before the job starts.

This enhancement is available in the Console > Data Loader application and in the Data Loader.

For more details, see Load interactions without defining a data model.

Customer password policies now inherit the following properties from the default policy if not explicitly defined:

• numberOfFailedLoginAttempts
• numberOfFailedMFALoginAttempts
• inactivePeriodInDays

This simplifies configuration by allowing you to focus on the specific settings you want to customize, while maintaining consistency with the default security standards. For more details, see Set a customer password policy.

The User Management API operations now return a single, standardized error response and HTTP status code for both valid and invalid usernames, ensuring a consistent experience in case of errors. For details on the API operations, see User Management API.