Comments URL: https://news.ycombinator.com/item?id=48666280

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=48570688

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=48148866

Points: 2

# Comments: 0

I have built Recursant, an AI agent governance platform that governs agents across stacks and clouds to maintain compliance. In many large enterprises this is a real compliance issue with different teams using different frameworks and runtime environments, which creates control risk.

I hope to get some feedback on it. It is a viable alternative to the large vendor controlled stacks. Architecturally it is quite unique given its use of the Istio / sidecar pattern. This enables agent isolation at the network layer.

Thanks Anders

Comments URL: https://news.ycombinator.com/item?id=48118988

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=48040450

Points: 4

# Comments: 0

I have just released Recursant to the public. I have been working on it for a while. It is a control plane for governing AI agents across stacks. It provides full observability, guardrails, and control on the network level by routing all traffic through a side car.

Problem statement: many large, regulated enterprises (think banks, telcos) have one engineering team on LangGraph, another on CrewAI, marketing on AgentForce, and data teams on Databricks Agent Bricks. They need their agents to talk to each other with consistent policy enforcement, one audit trail, and a single set of guardrails, yet allowing different functions to run on their own stacks. Recursant solves that problem using the service mesh pattern

Recursant has two components: a registry and the mesh . The registry contains all live agents. The mesh uses sidecars to route traffic and enforce on the network layer.

Aim is for Recursant to provide a real-time EU AI Act Annex IV compliance, so it is not generated from static documents. This saves time and effort for large enterprises subject to the requirement.

Linmitations:

- Recursant currently plugs in to CrewAI, Langgraph, and n8n . The aim is to support proprietary platforms such as ServiceNow and AgentForce as much as psosible. - The Recursant SDK still needs work to support as many agents as possible - I would also like to provide support for some of the 'personal agent' platforms such as OpenClaw, NanoClaw, and Hermes - Only tested on k8s, not public cloud - Documentation is sparse and needs to be developed.

I hope this project is useful to some of you.

Comments URL: https://news.ycombinator.com/item?id=48036330

Points: 2

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=47909020

Points: 2

# Comments: 0

To reduce the chance of breaches, I built ClawLock, a supervisor (sidecar with process isolation) for OpenClaw that injects controls around tool use. The user defines a passport for what the tools can and cannot do and ClawLock governs it. For high-risk transactions like in-browser purchases or shell command, a deterministic policy engine and an LLM-as-judge are used to detect any potential threats prior to execution.

ClawLock is currently in its infancy. It is primarily tested on Linux. I would appreciate any feedback on your experience using it on MacOS and WSL.

Comments URL: https://news.ycombinator.com/item?id=47598821

Points: 2

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=46351355

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=42032048

Points: 2

# Comments: 0