"Trust us" is not a security model
Agents touch production code and customer data. Without enforced boundaries, every prompt is one injection away from an incident.
Use case · Enterprise agent governance
Govern what your agentssee, use and remember.
LeanCTX is the governance and proof layer for agent fleets: PathJail confines file access, a shell allowlist blocks dangerous commands, secrets are redacted before models see them, budgets cap spend per role, and a signed Evidence Bundle proves what happened — with FinOps cost export and framework coverage (EU AI Act / ISO 42001 / SOC 2). Local-first: nothing leaves the machine.
Same engine. Different workflow. Always the right context.
What it costs you today.
Spend without accountability
Token bills arrive as one number. Which team, which agent, which task? Most stacks cannot attribute a single dollar.
Audits have nothing to read
When compliance asks what an agent read and ran in March, a log folder of raw prompts is not an answer.
The capabilities that do the work.
Everything below ships in the open-source binary today. No roadmap items, no waitlists.
Your tools→LeanCTX→Model
PathJail
filesystem confinement: agents read only what policy allows
Shell allowlist
dangerous commands blocked before execution
Secret redaction
keys and credentials stripped before any model sees them
Injection detection
OWASP-aligned screening of untrusted content
Signed audit ledger
Ed25519-signed, hash-chained record of reads, commands and savings
Compliance evidence
signed Evidence Bundle v1 + offline leanctx-verify; EU AI Act / ISO 42001 / SOC 2 framework reports
Policy packs + FinOps
versioned policy packs with lean-ctx policy coverage; finops export to FOCUS / CloudZero / Vantage + Datadog /metrics
From zero to first gain.
terminal
# inspect the active security posture
$ lean-ctx doctor# score controls against a framework
$ lean-ctx policy coverage --framework eu-ai-act# export a signed evidence bundle for auditors
$ lean-ctx audit evidence --from 2026-01-01 --to 2026-03-31 --out evidence.zip# push net savings to your FinOps stack
$ lean-ctx finops export --target=focus# live observability for the whole layer
$ lean-ctx dashboardOne guide. Two journeys. Full reference.
01
guide · Security model
PathJail, allowlists, redaction and detection in depth.
Learn more02
journey · Security & governance journey
Policy packs, budgets and audit in practice.
Learn more03
journey · Prove It: signed evidence
The savings receipt, A/B eval, scorecard and Evidence Bundle.
Learn more04
reference · Compliance & frameworks
EU AI Act / ISO 42001 / SOC 2 coverage and evidence bundles.
Learn more05
reference · Context Governance Benchmark
Score your context controls; see lean-ctx policy coverage.
Learn more06
reference · Enterprise overview
SSO, fleet policies, air-gapped deployment.
Learn moreQuestions teams ask before adopting.
Nothing, and you can verify it. LeanCTX runs locally with zero telemetry. The audit ledger, cache and knowledge store are local files; network egress happens only where your own configuration sends it.
Entries are hash-chained and Ed25519-signed. Any modification breaks the chain, and lean-ctx savings verify proves integrity end to end, exportable for compliance.
Yes. lean-ctx policy coverage scores your active controls against the Context Governance Benchmark and maps them to the EU AI Act, ISO 42001 and SOC 2. lean-ctx audit evidence then exports a signed Evidence Bundle that a standalone leanctx-verify validates offline.
Yes. lean-ctx finops export emits FOCUS 1.2, CloudZero AnyCost or Vantage records, net of injection, and the daemon exposes Datadog and Prometheus /metrics. Cost becomes a line item attributed by day, project, agent, model and tool.
No. Policy checks run in-process in the same Rust binary that serves reads. Microseconds, not round-trips. Governance and compression share one pass.
Take back control of your context.
Free for local use, forever. CI enforces it. One binary, ten minutes to the first measured gain.