01
MCP servers
The tool layer an agent actually reaches through, wired in from a config file, invisible to a gateway.
Inventory
Every agent, MCP server, skill, and model on every host.
The AI layer leads, MCP servers, coding agents and CLIs, agent skills, and local models, with the classic software supply chain underneath as the base we also cover. Drig, Sekeye's host binary, is a thin, read-only, pull-only Go agent with no LLM on the box; all matching happens server-side against a signed catalog. macOS, Linux, and Windows; laptops and servers alike.
What we see
AI surfaces lead. The classic supply chain is the base.
The layer that installs itself, updates without asking, and inherits whatever credentials the shell already holds, plus the software supply chain that never went away and sits outside CI, where a lockfile audit never looks.
02
AI agents & skills
The coding agents and CLI runtimes holding your credentials and your shell, plus the skills and plugin dirs that extend them.
03
Local models
Weights pulled straight onto the host, usually with no review pass between the hub and the disk.
04
Browser extensions
Self-installed, auto-updating, and sitting inside an authenticated session all day.
05
IDE extensions
Editor plugins running with the developer's full privileges, increasingly AI-adjacent themselves.
06
Language packages
Installed outside CI, on a developer's machine, where a lockfile audit never looks.
07
OS package managers
The self-provisioned layer, user-space installers that answer to no fleet policy.
08
Applications
Baseline app inventory, so the picture of the host is complete.
09
Machine profile
The host's identity and state, laptop or server, treated as one fleet.
Thin by design
Never the reason a host is slow.
A single static binary, rule-based, that scans in milliseconds and gets out of the way. All the intelligence is server-side.
10 MB
single static Go binary
Milliseconds
full scan, not minutes
Single-digit MB
memory during a scan
Read-only
pull-only · no LLM on the box
Privacy commitments
What Sekeye never collects.
Permanent product commitments, not MVP simplifications. The ingest schema rejects any record that carries an env value.
- ×File contents beyond manifests and configs
- ×Secret or env var values, MCP configs give us names, never values
- ×Browser history
- ×Credentials
- ×Keystrokes