Where do a customer’s existing agents and platform fit within Lyzr’s agent control architecture?

You’ve already invested in building agents on your chosen platform.

Your agents and platform stay exactly where they are. They run in your environment, under your control.

OpenController by Lyzr, the control plane for enterprise AI agents, sits on top as a governance and observability layer.

It doesn't replace your stack. It secures it.

OpenController is Lyzr's answer to the control plane problem in enterprise AI: the governance layer between agent development and production.

A Control Plane, Not a Replacement

The core principle is simple: bring your own agent.

OpenController is designed to be framework-agnostic.

It accepts agents built on LangChain, CrewAI, LangGraph, or a raw SDK. You don't need to rebuild anything or migrate to a new development environment.

Your team keeps the tools they know.

The value of Lyzr's control plane is in adding governance, not in forcing a new way to build. It closes the gap between a working prototype and a production-safe agent that compliance and security teams can trust.

How Your Stack and Lyzr's Control Plane Connect

The integration is an architectural shift, not a code rewrite. Instead of your applications calling agents directly, they call OpenController.

The flow looks like this:

1. Your application, service, or user front-end initiates a task for an agent.
2. The call goes to the dedicated OpenController endpoint for that agent, not the agent itself.
3. OpenController intercepts the call and applies all configured policies: access controls, budget limits, data masking rules, and any required human-in-the-loop approval gates.
4. Once cleared, OpenController forwards the request to your agent, which is still running in its own environment (your VPC, your on-prem server, your cloud).
5. OpenController’s observability layer records the entire transaction. It captures the inputs, the tool calls, the LLM interactions, and the final output.

This creates a complete, unified audit trail for every agent action, regardless of the underlying framework.

Frequently asked questions

Do we have to rewrite our agents to use OpenController?

No. OpenController accepts agents built on any framework; nothing needs to be rebuilt. It integrates via standard API calls, acting as a proxy that adds a layer of control.

Does this work with agents running on-prem or in our own VPC?

Yes. OpenController is designed to govern agents wherever they run.

The control plane communicates with your agent endpoints securely, whether they are in a public cloud, a private cloud, or an on-premise data center.

What if our agent is actually a collection of sub-agents?

OpenController can trace the entire execution graph. It can show one end-to-end trace even when an agent calls multiple sub-agents as tools, giving you full visibility into complex workflows.

The Takeaway: Add Control, Don't Replace

Lyzr's architecture adds a control plane above your existing work. It doesn't force you to migrate into a new platform.

You keep your agents, your framework, and your infrastructure. You gain the governance, observability, and security needed to run them in production.

Let's talk about how OpenController can fit your specific architecture.

Want to see how it fits your stack? Talk to us about OpenController by Lyzr.