Kontext
Kontext SecurityKontext places a local daemon between coding agents such as Claude Code, Codex and Cursor and the tools they call, evaluating Cedar policy before supported actions run and recording each decision in a hash-linked ledger. Policies are written and rolled out from a hosted workspace, starting in observe mode before they enforce. Kontext, a Munich company, builds it.
Openness
4 medium confidence- license
- MIT (daemon, hooks, CLI and local Guard runtime)+MIT (bundled step-safety model, copyright Microsoft Corporation)
- source
- public
- core features withheld
- yes — the local-only kontext guard path runs hooks in observe mode, and Cedar enforcement comes only through the managed daemon, which enrolls with an install token from the hosted workspace and fetches its policies there; no policy service is published, and the workspace is free to 5,000 transactions a month and paid beyond
- commercial
- Kontext hosted workspace (policy authoring and rollout, dashboards, risk and cost review; Free, Team and Enterprise plans)
The Kontext daemon that evaluates policy and records decisions is MIT-licensed and runs on the user's machine, but on its own it only observes. Blocking an action needs the managed daemon, which enrolls with a token from Kontext's hosted workspace and fetches its policies there, and that workspace is free only up to a monthly allowance.
- https://docs.kontext.security/guides/how-decisions-work.md recorded 2026-11-20
The docs say "The workspace sends policy to the endpoint and receives records afterward", and that the endpoint keeps the last policy it received while offline.
- https://kontext.security recorded 2026-11-20
The site's pricing lists Free at $0 with 5,000 transactions a month, Team at $500 a month with 100,000 transactions, and custom Enterprise pricing.
- https://raw.githubusercontent.com/kontext-security/kontext/main/docs/guard.md recorded 2026-11-20
The Guard page says "kontext guard ... is the standalone, local-only path" with no login, and that the managed daemon "uses its install token to fetch managed configuration"; its public/private boundary puts the daemon and Cedar policy in the public CLI.
- https://raw.githubusercontent.com/kontext-security/kontext/main/internal/guard/cli/cli.go recorded 2026-11-20
The standalone Guard command prints "Local hooks run in observe mode. Cedar enforcement is provided by the managed daemon configured through kontext setup or MDM."
- https://raw.githubusercontent.com/kontext-security/kontext/main/internal/guard/stepsafety/model/LICENSE recorded 2026-11-20
The bundled step-safety model directory carries an MIT License, "Copyright (c) Microsoft Corporation".
- https://raw.githubusercontent.com/kontext-security/kontext/main/LICENSE recorded 2026-11-20
The root LICENSE is the MIT License, "Copyright (c) 2026 Kontext contributors".
Adoption
1 low confidenceAdoption is read from Homebrew installs of the kontext package in homebrew-core over the trailing month. The README's first install route is a self-updating cask from Kontext's own tap, which Homebrew's analytics do not cover, and Windows builds are zip downloads, so most installs fall outside this figure.
- https://formulae.brew.sh/api/formula/kontext.json recorded 2026-11-20
Homebrew's kontext package ("Identity, credentials, and governance for AI agents", homepage kontext.security, MIT) builds from github.com/kontext-security/kontext v1.24.1 and reports 106 installs in 30 days.
Capability
1 medium confidenceKontext keeps a hash-linked, optionally signed ledger of the policy decisions it reaches on an agent's tool calls. Run on its own, it only records what policy would have blocked, because denying a call needs a policy fetched from Kontext's hosted workspace. It gives the agent no identity of its own, and has no delegation chain or step where a person approves a held action.
- https://raw.githubusercontent.com/kontext-security/kontext/main/docs/guard.md recorded 2026-11-20
The Guard page says Ed25519 receipt signatures can be enabled with KONTEXT_GUARD_LEDGER_SIGNING=1 and that VerifyReceipts "checks receipt hashes, previous-hash links, and local Ed25519 signatures".
- https://raw.githubusercontent.com/kontext-security/kontext/main/internal/guard/store/sqlite/receipt_signing.go recorded 2026-11-20
VerifyReceipts walks the local receipt chain, checking each receipt hash, its previous-hash link and, when signing is on, its Ed25519 signature.
- https://raw.githubusercontent.com/kontext-security/kontext/main/internal/managedobserve/daemon.go recorded 2026-11-20
The managed daemon takes its mode from managed.json ("observe records would-decisions, enforce returns real denies") and builds its Cedar policy client from the configured cloud URL.
- https://raw.githubusercontent.com/kontext-security/kontext/main/internal/runtimehost/host.go recorded 2026-11-20
Start refuses any mode other than observe without a managed policy source: "enforce and remote modes require a managed Cedar policy source".
- https://raw.githubusercontent.com/kontext-security/kontext/main/README.md recorded 2026-11-20
The README says Kontext "evaluates policy before consequential actions run, and records the decision and outcome in an authorization ledger", denying in enforce mode at supported synchronous hooks.
Verified 2026-11-20, except some scores, still awaiting re-confirmation