Skip to main content
AIDiveForge AIDiveForge

Exogram vs Legibility Field Kit

Exogram and Legibility Field Kit are both guardrails & safety tracked by AIDiveForge. Below is a side-by-side comparison of pricing, capabilities, platforms, and ownership — sourced from each tool's live website and verified before publishing.

Exogram

Exogram

Exogram is an execution governance layer that intercepts AI agent actions — payments, database writes, customer emails, record updates — and applies a policy decision before anything hits your infrastructure. The vendor describes a four-way enforcement decision: allow, deny, escalate, or log. Policy rules are checked at runtime, not after the fact, which means a $25,000 invoice approval blocked against a $1,000 limit never reaches your payment system. The immutable audit trail is positioned for SOC 2, HIPAA, and financial compliance workflows. The tool is not itself an agent runner — it assumes you already have an agent; it governs what that agent is allowed to touch.

Legibility Field Kit

Legibility Field Kit

The kit is a zero-dependency Python CLI that runs three checks against your AI decision records: does every change name a specific human owner, is time-to-reverse recorded for reversible actions, and does each entry carry a complete OTW receipt — Owner, Time, Witness. Run `audit` against a directory of governance files and it surfaces every defect in seconds. The scoring command turns those findings into a maturity grade across the three tests, giving compliance teams a number to track sprint over sprint. The wall appears fast: the kit reads files, flags gaps, and stops — it does not integrate with your ticketing system, your CI pipeline, or your approval workflow.

AttributeExogramLegibility Field Kit
PricingPaidPaid
Free trialNoNo
Open sourceNoYes
Has APIYesNo
Self-hosted optionNoYes
PlatformsSaaS, CloudPython
Released2025-05
Pros
  • Runtime policy enforcement at the tool-call boundary, so unauthorized payments and database mutations are blocked before they execute rather than flagged after the damage is done.
  • Four-way enforcement decisions — allow, deny, escalate, log — which means regulated workflows get a human review step without building a custom approval queue on top of your agent stack.
  • Immutable audit logs positioned for SOC 2 and HIPAA compliance, so teams in regulated industries have a defensible record of every action an agent attempted and what decision was returned.
  • Pre-built integrations with LangChain, CrewAI, AutoGen, Vercel AI SDK, and LlamaIndex, so teams already running these frameworks add a governance layer without rewriting their agent code.
  • An open protocol spec (EAAP) published as RFC-0001, so teams who need to audit, extend, or independently verify the governance model are not working against a black-box contract.
  • Zero external dependencies, so the tool runs in an air-gapped or locked-down environment without a dependency audit of its own — which means regulated teams do not have to clear a supply-chain review just to use the auditor.
  • The `init` command scaffolds governance files before a system goes live, so teams start with compliant structure rather than retrofitting it after a finding.
  • OTW receipt detection — Owner, Time, Witness — catches the specific pattern where 'the team' or 'engineering' appears in the owner field, which is the defect that makes approval records legally meaningless under most accountability frameworks.
  • Apache-2.0 license with self-hosted option, so your governance records and their audit results never leave your own infrastructure — critical when the files themselves contain sensitive decision rationale.
  • Maturity scoring across three discrete tests gives compliance leads a metric that moves, so governance improvement has a number attached rather than being a qualitative assertion.
Cons
  • Exogram governs actions but does not orchestrate agents — teams that need branching logic, memory, or coordination between multiple agents still maintain a separate orchestration layer, which means adding Exogram adds a second system to debug when an escalation fires unexpectedly.
  • No self-hosted deployment option is described on the vendor page, which means teams whose compliance requirements mandate on-premises data residency — common in financial services and healthcare — cannot use Exogram without routing agent traffic through external infrastructure; those teams move to building policy enforcement into their own API gateway instead.
  • The tool launched in approximately May 2025, so production case studies at scale are not yet publicly available; teams evaluating for high-volume payment workflows are working from architecture documentation and demos rather than documented incident records from comparable deployments.
  • The kit audits files that already exist — if your team's governance process lives in Jira tickets, Confluence pages, or Slack threads rather than structured files in a directory, there is nothing for the tool to read, and the first project becomes manually exporting records into a format the CLI can parse.
  • There is no CI integration, webhook, or pre-commit hook provided out of the box, so the audit runs when someone remembers to run it; teams that need enforcement at the moment a decision is logged — not after the fact — add their own pipeline glue, at which point they are maintaining that integration themselves.
  • The repository shows two stars and a single commit at time of listing, which means community-tested edge cases, maintained issue trackers, and peer-vetted documentation are absent; teams with complex governance schemas that do not match the demo structure have no community forum to consult and will be reading source code to understand behavior, which pushes some teams toward building a custom linter in-house instead.
Bottom line

Legibility Field Kit is open source; only Exogram exposes a public API. Choose based on which difference matters most for your workflow.

Frequently asked questions

What is the difference between Exogram and Legibility Field Kit?

Exogram is Paid, while Legibility Field Kit is Paid and open source. Compare pricing, free trial, API, platforms, and pros/cons in the table above on AIDiveForge.

Is Exogram better than Legibility Field Kit?

It depends on your workflow. Use the side-by-side attributes (pricing, open source, API, self-hosted, platforms) to decide. AIDiveForge does not rank a universal winner — we publish verified facts so you can choose.

Exogram vs Legibility Field Kit: which should I pick?

Pick Exogram if its pricing model, openness, or platform fit matches your constraints; pick Legibility Field Kit otherwise. Check free-trial availability on each listing if you want to test before committing.

Comparison data is sourced and verified by the AIDiveForge data pipeline. AIDiveForge is editorially independent.