Skip to main content
AIDiveForge AIDiveForge

Exogram vs Subtext

Exogram and Subtext are both inference engines & infra 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.

Subtext

Subtext

Subtext is an open-source, self-hosted tool that surfaces a local language model's internal representations — specifically the J-space global workspace identified in Anthropic research — as the model reads and generates, before output tokens appear. You get a browser-based live view and the ability to record, export, and replay sessions for later analysis. The stack is Python-based and runs against local models, so there is no cloud dependency and no data leaves the machine. The ceiling appears quickly: Subtext has no API, no integration hooks, and no support for models it cannot instrument directly — which means anything running behind a remote endpoint stays opaque.

AttributeExogramSubtext
PricingPaidFree
Free trialNoNo
Open sourceNoYes
Has APIYesNo
Self-hosted optionNoYes
PlatformsSaaS, CloudPython, local inference
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.
  • Exposes J-space internal representations in real time before output tokens are committed, so you can observe the model's reasoning process rather than reverse-engineering it from outputs after the fact.
  • Session recording and browser-based replay via `record_session.py`, which means you can share a captured session with a colleague or step through a failure case hours after it happened without reconstructing the exact prompt conditions.
  • Fully self-hosted with no cloud dependency, so sensitive prompts and model states never leave the machine — critical for any research involving proprietary data or unpublished model weights.
  • Ships with a `verify_accuracy.py` script and a linked reference paper, so teams can audit whether the J-space instrumentation is behaving as the methodology describes rather than taking the visualization on faith.
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.
  • No API and no integration hooks mean every observation stays inside the tool. Teams who want to log J-space states to a database, trigger alerts on specific internal patterns, or feed observations into an evaluation framework have to parse exported files themselves — that DIY layer adds maintenance burden fast.
  • Instrumentation is limited to local models the tool can attach to directly. The moment your model moves to a hosted endpoint — OpenAI, Anthropic, or any other remote API — Subtext goes dark. Teams running production models in the cloud will find nothing here to replace their existing black-box debugging approach, and at that point they switch to tools built around token-level logging or external evaluation harnesses instead.
  • Multi-turn session tooling exists (`test_multiturn.py`) but the project has 25 commits and no open issues or pull requests — community surface area is thin. Teams who hit an edge case with a specific model architecture have no forum, no community plugin layer, and no documented escalation path beyond reading the source.
Bottom line

Exogram is paid while Subtext is free; Subtext 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 Subtext?

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

Is Exogram better than Subtext?

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 Subtext: which should I pick?

Pick Exogram if its pricing model, openness, or platform fit matches your constraints; pick Subtext 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.