Relyance AI news and product updates

Relyance now lets customers trace user input all the way to the LLM vendor it is sent to. The same release expanded third party agent mapping to show each agent's tools, an agent blueprint and full chains from agent to server to agent.

Buyer relevance. Privacy and legal teams can answer where prompts containing personal data actually go, which data maps built before AI agents cannot show. That evidence supports vendor assessments and AI Act documentation.

Relyance AI's 14 Oct release lets customer hosted InHost deployments store their AWS inventory data directly in the customer's own S3 bucket, so the inventory Relyance builds of cloud assets and the data they hold sits in storage the customer owns.

Buyer relevance. Legal and privacy teams that must keep data maps of regulated or confidential systems inside their own cloud get a residency option for that inventory, which simplifies data location reviews. The note covers AWS inventory only, so ask where other scan outputs are kept.

Relyance AI's 21 Sept release tightened Strict InHost mode so sampled record values and error text stay out of scan results. InHost runs the Relyance scanner in a cloud account the customer owns and copies only the results back to Relyance. The same release adds sanitized supporting context to data classification findings, which previously showed no context at all.

Buyer relevance. Teams that keep scanning inside their own cloud can now be sure raw record values never leave it, even in error messages. Sanitized context also makes findings easier to check without exposing the data behind them.