Network-AI

Frameworks & Eval · tested 2026-08-07 · re-test due 2026-11-07 · by the Hlido desk, not the vendor

In short: A governance layer for multi-agent systems that names the real failure mode — agents don't crash, they silently overwrite each other — and discloses its own high-severity CVEs on the front page.

5 PASS · 0 FAIL of 5 public-surface claims

Quick answer

Network-AI scores 76/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-08-07). STEADY (76) for a correctly-identified and under-served problem, primitives that actually address it (mutex-backed propose/validate/commit, permission gating, tamper-evident audit log), MIT licensing, and conspicuous sec Pricing: Open source (free entry point documented).

Network-AI sits between agents and shared state, adding locking, permission gating, budgets, audit trails and workflow governance so parallel agent systems behave like production software. The problem statement is the sharpest in this wave: parallel agents "do not usually fail loudly — they fail by silently overwriting state, bypassing policy, drifting across workflow stages, and leaving you with no reliable audit trail." That is correct, under-discussed, and exactly what most orchestration frameworks assume away. The primitives match it: propose→validate→commit with a filesystem mutex instead of last-write-wins, permission scoring before sensitive operations, and an append-only HMAC/Ed25519 tamper-evident audit log. It wraps existing agents (LangChain, CrewAI, AutoGen, MCP) rather than replacing them. What raises confidence most is uncomfortable: the release snapshot on the homepage is v5.15.1, headlined "Security: ClaudeHookBridge & SandboxPolicy matcher bypass fixes — two high-severity vulnerabilities." A security-governance product publishing its own high-severity bypasses on its landing page is behaving the way we want vendors to behave, and it also tells you the product is young enough to have shipped two policy-bypass bugs in consecutive releases. 3,638 tests across 41 suites and 32 adapters are self-reported and unverified. MIT licensed. Reviewed from the public surface.

Why STEADY

STEADY (76) for a correctly-identified and under-served problem, primitives that actually address it (mutex-backed propose/validate/commit, permission gating, tamper-evident audit log), MIT licensing, and conspicuous security honesty — it publishes its own high-severity fixes rather than burying them. Held below VITAL because those same disclosures show policy-bypass bugs in consecutive recent releases, every metric (3,638 tests, 32 adapters) is self-reported, and there is no third-party audit of a component whose entire value is enforcement.

Public-surface checklist

What we saw

4 screenshots captured by the Hlido engine during the reviewed run (run-be5ebff148cf15a4-network-ai-org). Our own captures — not vendor marketing material.

Network-AI — run screenshot 1 (home.png)
home.png
Network-AI — run screenshot 2 (page_architecture.png)
page_architecture.png
Network-AI — run screenshot 3 (page_proof.png)
page_proof.png
Network-AI — run screenshot 4 (page_demos.png)
page_demos.png

What it does well

What it fails at

Red flags

Best for

  • Teams running genuinely parallel agents against shared state who have hit silent overwrites
  • Regulated contexts needing a tamper-evident record of what an agent was permitted to do
  • Multi-framework estates wanting one governance layer rather than per-framework controls

Not recommended for

  • Single-agent or strictly sequential workflows, where the coordination cost buys nothing
  • Deployments requiring an audited enforcement layer today
  • Teams unable to absorb frequent security-driven upgrades

Pricing & access

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-05.

Related agents

Agent relevance

API MCP SDK Behavioral-testable

Agentic-Commerce Readiness 77/100 · COMMERCE-READY

Independent readiness for agent delegation & transaction. How it’s scored · check live

Purpose-built to sit in the agent execution path: adapters for LangChain, CrewAI, AutoGen and MCP, with control primitives (Blackboard, AuthGuardian, JourneyFSM, budgets) that agents call rather than humans.

Agent-friendly score: 9/10

Evidence

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-1+editorial-narrative-v2 · Methodology version 2026.05 · Next review due 2026-11-07

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Hlido trust score

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/jovancoding-network-ai.svg)](https://hlido.eu/check/?agent=jovancoding-network-ai)

HTML

<a href="https://hlido.eu/check/?agent=jovancoding-network-ai"><img src="https://hlido.eu/badge/jovancoding-network-ai.svg" alt="Hlido trust score"></a>