Skip to content
OmnodexOmnodexOmnodex Docs

Security Model

Omnodex is a security tool, so its own security posture matters. This page describes the threat model, trust boundaries, and design decisions that keep your data safe.

Threat Model

Section titled “Threat Model”

Omnodex operates in a sensitive position: it sees everything your AI agent does. The security model is designed around the principle that this data should be under your control at all times.

Trust Boundaries

Section titled “Trust Boundaries”
BoundaryWho Controls It
Event captureRuns locally on your machine
Event storageWritten to your local filesystem
Analysis (free tier)Runs locally on your machine
Cloud sync (hosted tier)Encrypted on your machine before upload
Cloud storageEncrypted blob - we cannot read it

What We Never See (Hosted/Cloud Tiers)

Section titled “What We Never See (Hosted/Cloud Tiers)”

Even when you use cloud features:

  • We never see your raw event data
  • We never see your credentials or API keys
  • We never see the content of tool calls or responses
  • We never hold your encryption key

The metadata we can read, such as your email address and when each machine last synced, is listed in What Omnodex Can See.

Local-First Architecture

Section titled “Local-First Architecture”

The free tier is entirely local. Nothing leaves your machine:

  • Events are written to a local file
  • Analysis runs locally
  • The dashboard is a local web server
  • Recording and analysis make no network calls (the CLI checks for updates in the background; turn this off with OMNODEX_NO_UPDATE_CHECK=1)

Observation by Default

Section titled “Observation by Default”

In the default monitor mode, Omnodex only observes. Hooks record what the agent does and never change, block or inject anything. Shadow mode adds a note to each finding saying whether Omnodex would have stopped the call, and still lets every call run. Only guardrails mode (Pro), which you turn on with omnodex enforce guardrails, stops or holds calls, and only the ones your settings name. See Shadow Mode and Guardrails.

Supply Chain Considerations

Section titled “Supply Chain Considerations”

The Omnodex core (all interceptors, event log, rule engine, CLI, and local dashboard) is open source under the AGPL-3.0. You can:

  • Inspect every line of the local pipeline’s code
  • Verify what the hook actually sends
  • Audit the event schema for unexpected fields
  • Build from source to eliminate supply chain risk

Cloud components (hosted dashboard infrastructure, advanced rule distribution, threat intelligence) are proprietary and available on paid tiers. The local pipeline never depends on cloud components - it is a complete, self-contained product.

Next Steps

Section titled “Next Steps”