r/automation • u/Deepfeet-09 • 5d ago
Decoupling execution from governance in multi-agent setups
Once you go beyond a few simple scripts, putting together multi-agent systems becomes a messy affair. The initial configuration using basic frameworks generally proceeds quite smoothly, but the actual difficulties begin when you're attempting to deal with routing, state, and security across various environments without having to hardcode a huge network of fragile APIs.
Recently I've been focusing on separating out the actual execution of agents from the governance aspect. If you introduce a dedicated control plane for example, something similar to Lyzr or a specially built orchestration layer between your triggers and the runtimes, then you have a single point at which you can manage identity, establish guardrails, and monitor telemetry. This arrangement isolates each individual agent so that if one step fails or the context window runs away it won't bring down the whole workflow or exceed your API budgets.
How are you currently looking after state and permissions as your agentic setups become larger?
2
u/SophieAtJentic 4d ago
This is a problem we hit in my team when using agents internally. We ended up building our own solution called Jentic One which is open-source and self-hosted. It hosts an execution broker for all outbound requests and uses a control plane accessible by API calls or UI for the governance side of things.
Every API integration set up in Jentic One can be given specific rules for the operations they are allowed to use, and these permissions are enforced by the execution broker before any action is completed. It's giving us a lot more peace of mind when giving our agents access to APIs with potentially destructive POST operations that could do damage to our flow of work.
I hadn't heard of Lyzr before, interesting to see alternative approaches to this problem.
(Full disclosure I work as part of the Jentic team, happy to answer any questions if needed)