Agentically primed
Agentically primedAgents can run Novuz. Agents can run what Novuz builds.
Both the Novuz platform and the pipelines it delivers are built to be run by agents: the platform through its APIs, the pipelines through the Model Context Protocol. The conversion itself stays deterministic.
Agentically primed
Agentically primedAgents can run Novuz. Agents can run what Novuz builds.
Both the Novuz platform and the pipelines it delivers can be run by agents: the platform through its APIs, the pipelines through MCP. The conversion itself stays deterministic.
The platform is headless
Everything Novuz does through its UI it also does through APIs. Your orchestrator, your CI/CD pipeline, your SI’s tooling or an AI agent can trigger discovery, conversion, validation and deployment, inspect results, and gate the next step on a human approval.
The pipelines are MCP-ready
Through the Model Context Protocol, each converted pipeline can expose run, check status, retrieve lineage, inspect outputs and rerun a failed step as tools your agents discover and call, under your access, approvals and audit logging, on Databricks, Snowflake or Microsoft Fabric.
What stays the same: the conversion is deterministic. Agents decide what to ask for and when; the platform gives the same output for the same input, so every result can be tested, audited and repeated.
| Headless platform | MCP-ready pipelines | |
|---|---|---|
| Applies to | The Novuz modernization engine | The pipelines Novuz delivers |
| Used by | Delivery teams, partners, orchestrators, agents | Operations and data agents, downstream applications |
| Purpose | Run modernization programmatically and continuously | Run and manage the modernized estate through agents |
| Outcome | Faster, repeatable migration | Pipelines that are agent-ready from day one |
An agent gets only what you expose, under your own access, approvals and audit logging.
The platform
What an agent can do with the Novuz platform
Everything the Novuz UI does, an agent can do through the same APIs. Your orchestrator, your CI/CD pipeline, your SI's tooling or an AI agent can:
- Trigger discovery on a schedule or on demand.
- Start conversion runs and inspect progress object by object.
- Run validation and reconciliation and read the results.
- Gate the next step on a human approval.
- Deploy or export the converted code through your own pipeline.
The pipelines
What an agent can do with the pipelines Novuz delivers
Each converted pipeline can expose its operations as MCP tools your agents discover and call, on Databricks, Snowflake or Microsoft Fabric.
- Run a pipeline and check its status.
- Inspect the outputs of any run.
- Retrieve lineage for any number, back to the object that produced it.
- Rerun a failed step after a fix, with the same inputs.
Control
Access, approvals and audit logging
An agent gets only what you expose, under your own access, approvals and audit logging.
- Agents act under your identity provider and your access rules. An agent reaches no more than a person with the same role.
- You choose which operations to expose as MCP tools, per pipeline.
- Human approvals gate the steps you choose to gate.
- Every action an agent takes is logged in your environment.
FAQ
Agentically primed, in practice
Find out what your logic debt is costing you.
Every object counted, lineage, dead code and a fixed price in three business days. $3,000, credited.
Not sure which door? The scorecard takes ten minutes and tells you.