Hi there,
This release expands Nexadata's reach into enterprise environments. Connector Copilot now supports OData APIs natively, introduces a full Zero Data Retention (ZDR) compliance infrastructure, and adds a new transformation that gives you precise control over record identity in downstream systems. Here's what's new in the Mid-Spring Release.
Connector Copilot now natively supports OData APIs, complementing the existing OpenAPI spec-based approach. Systems like Microsoft Dynamics, SAP, and Acumatica expose their data through OData, and Connector Copilot now supports OData versions V2, V3, and V4.
True to its agentic nature, the Connector Copilot autonomously parses the OData metadata, determines how to traverse the service, constructs valid requests, and builds a fully configured dataset. No manual spec work, no custom code.

Once you provide an OData service URL, the Connector Copilot will:
$metadata document to discover entity types and properties$top, $skip, nextLink)Enterprise customers with strict data residency and retention requirements now have a clear, auditable path to deploy Nexadata in a fully ZDR-compliant configuration. This release delivers ZDR support across two layers: at the platform level and at the AI infrastructure level.
Nexadata now supports a configurable ZDR mode that prevents end-user prompt content from being stored at rest. When ZDR mode is enabled, prompts submitted through the Copilot Suite are used in-flight for AI reasoning and discarded. They are never written to persistent storage.
This directly addresses a compliance barrier that enterprise customers face when deploying AI-assisted tools in regulated environments.
Nexadata now supports Amazon Bedrock as an alternative AI inference provider. This enables per-request ZDR without requiring a separate enterprise contract, and gives compliance teams an additional lever to meet their data governance requirements.
Nexadata's core architecture is unchanged: Claude continues to serve as the reasoning layer, and all data processing remains within Nexadata's deterministic execution layer.
A new transformation is now available: Generate Unique ID. This complements the existing Add Row Numbers transformation by generating a globally unique identifier for each record rather than a sequential row number.
Unlike row IDs, which are sequential and scoped to a single run, unique IDs are:
View Generate Unique ID documentation →
We're continuing to push the boundaries of what Connector Copilot can connect to, and investing in more powerful pipeline authoring. Here's what we're working on:
Thanks for being part of the Nexadata journey!
— The Nexadata Team