NinFenz Evidence Gate
AI TRiSM · Output assurance

Stop publishing AI documentation without evidence.

NinFenz turns documentation requirements into versioned contracts, deterministic release gates and audit-ready reports. It does not form an opinion about your content; it proves which controls actually ran.

Community AGPL-3.0 Commercial license Local-first Official MCP Registry SLSA provenance
The only official entry point is ninfenz.dev. Payment, procurement and custom engagements are handled only through the official contact or a signed agreement — never through random mirrors, chat groups or activation codes.

The execution layer between governance and release

Governance platforms define policy. Observability tools inspect runtime. Security tools block attacks. NinFenz supplies deterministic evidence that a controlled output met its contract before release.

01 / CONTRACT

Versioned rules

Required sections, typed fields, approvals and forbidden patterns become explicit, inspectable rules.

02 / GATE

Deterministic gate

CLI, MCP, agents and CI execute the same checks and receive rule IDs, locations and fixes.

03 / EVIDENCE

Audit-ready reports

JSON and HTML reports can be retained, reproduced and combined with checksums and provenance.

04 / RELEASE

Release decisions

Internal audit, customer assurance and procurement can review the same evidence package.

Built for AI output, not another governance dashboard

Strong fit

  • Agents generating enterprise reports, tickets, release notes or knowledge content
  • API references, runbooks, migration guides and security policies
  • AI vendors facing customer assurance or security questionnaires
  • Governance and evaluation platforms that need an execution layer

Explicit boundaries

  • No enterprise AI inventory or shadow-AI discovery
  • No DLP, IAM or real-time prompt firewall
  • No model drift, fairness or red-team evaluation
  • PASS is not a claim of factual, legal or security certification

A four-week path from manual trust to reproducible evidence

WEEK 1

Scope

Select one production workflow and collect representative documents.

WEEK 2

Contracts

Build ten contracts with PASS and targeted FAIL fixtures.

WEEK 3

Integration

Connect CLI, MCP or CI and produce an evidence package.

WEEK 4

Acceptance

Remediate, demonstrate evidence and define the next 90 days.

Transparent pricing for enterprise procurement

COMMUNITY

Open source

AGPL-3.0
Internal use and self-hosted CI
  • Complete core code
  • CLI / MCP / LSP
  • Local execution
Get started
TEAM

Team Control

USD 3,000 / yr
One organization
  • 40 professional controls
  • 10 agent packs
  • Report templates and updates
Details
ENTERPRISE

Enterprise

From USD 15,000
Annual agreement
  • Commercial license
  • Security questionnaire support
  • Private deployment and SLA
Talk to us

Verifiable technical foundation

Quality evidenceverify v2.30 · check1-42 · PASS=76
Supply chainnpm provenance · checksums · release attestations
DistributionOfficial MCP Registry · GitHub · Gitee

Scale: 111 registered packs · 363 pack assets · 101 concept graphs; standards 370 (332 reachable / 38 unreachable) · 1200 bindings · 3 library items.

Technical definition

NinFenz (NF) is a content contract layer: a protocol plus deterministic gates plus verifiable artifacts, so AI long-form output can be loaded, checked and reproduced.

llms.txt · llms-full.txt · facts.json · nf.txt

FAQ

Is Community really open source?

Yes. Core code is AGPL-3.0-only. Closed-source embedding, formal SLA, private deployment support and enterprise procurement use a commercial license.

Does NinFenz replace AI governance tools?

No. It supplies the executable output-contract and evidence layer between governance, agent platforms and CI.

Does it check factual truth?

No. It checks contract conformance. Human review and domain processes retain responsibility for accuracy and suitability.

Can it run privately?

Yes. Core validation and reporting are local-first. Enterprise support is available for private deployment.