Is Rossoctl the same project as Kagenti?

Yes. The Kagenti repository on GitHub now redirects to Rossoctl.

Does Rossoctl need OpenShift or Istio?

Not any more. Its docs mark OpenShift and Kind as Ready and other clusters as Beta, and Istio is an optional flag. Omnia runs on any Kubernetes and doesn’t need a mesh.

Can an Omnia agent call one running on Rossoctl?

Yes. Omnia references remote agents by URL over A2A, with outgoing auth, and uses their skills as local tools.

omnia vs rossoctl

Rossoctl (formerly Kagenti) handles who the agent is. Omnia tests and releases it.

Rossoctl exchanges a user’s token for one that’s good for a single tool. Its docs don’t yet cover testing an agent, versioning a release or upgrading one.

A new build of the claims agent is ready.

on omnia

The build is a new version of the pack. Simulated claimants work it through the real tools before it serves, one of them inventing a second injury. It passes, gets a share of new claims, keeps its numbers up and is promoted. Had they dropped, the previous version would have taken the traffic back. docs

on rossoctl

Rossoctl identifies the build by the version field on its agent card. Testing isn’t documented, and upgrading from one release to the next is listed as a subject with no page yet. their docs

Every release is tested and gated

Adversarial callers and duplex voice calls run alongside the simulated claimants. A version that fails the suite isn’t released. docs

Rossoctl: Not documented. The UI lets you try an agent by hand. source

A release is a thing you can name

Prompts, tools, policy and tests are one versioned pack, pulled from git or OCI. The rollout moves traffic to that version step by step, and a conversation finishes on the version it began on. docs

Rossoctl: The agent card’s version field identifies the running build. Rollout isn’t documented. source

Tool policy you can put in production today

A broker checks each tool call against your CEL rules, looking at the arguments and at who the caller is. If the broker can’t answer, the call is refused. docs enterprise

Rossoctl: Tool-call validation is Alpha, and the docs say not to use the Beta MCP gateway as an access-control boundary. source

At a glance

Topic	Omnia	Rossoctl, per its docs
Any Kubernetes	yes Installed with Helm. docs	partly Kind and OpenShift Ready; other clusters Beta. source
Agents from other frameworks	yes Run under the same governance; reachable over A2A or MCP. docs	documented Any container that speaks A2A. source
End-user identity to tools	yes OIDC or edge trust, carried to every call. docs	documented Token exchange per tool. source
Simulated users before release	yes Multi-turn, against real tools. docs	not documented Not documented. source
Stepped rollout, auto rollback	yes Traffic shifts in steps and rolls back on its own. docs	not documented Not documented. source
Argument-level tool policy	yes Enforced on every call; fails closed. docs enterprise	partly Alpha. source
Voice	yes Duplex voice, and tests for it. docs	not documented Not documented. source

Common questions

Is Rossoctl the same project as Kagenti?: Yes. The Kagenti repository on GitHub now redirects to Rossoctl.
Does Rossoctl need OpenShift or Istio?: Not any more. Its docs mark OpenShift and Kind as Ready and other clusters as Beta, and Istio is an optional flag. Omnia runs on any Kubernetes and doesn’t need a mesh.
Can an Omnia agent call one running on Rossoctl?: Yes. Omnia references remote agents by URL over A2A, with outgoing auth, and uses their skills as local tools.

Put your own agent through the gate.

Install Omnia in your cluster and run it free while you build.

Rossoctl claims are from The Rossoctl project (formerly Kagenti)’s published documentation, checked 22 October 2026. Spot something out of date? Tell us.

Install it in your cluster Or walk through it with us →