- Remediate: Pix in triage, three modes, fix paths
- Build: Coding agents, MCP, skills, hooks, Belai
- Govern: AI Firewall, 13 providers, one policy
- Prove: Inventory and compliance, AI-BOM, EU AI Act, ISO 42001
Remediation guidance, in the flow of triage
Pix turns every finding into a decision and a fix path, grounded in your stack and in the calls your team has already made.
Context-aware guidance
Pix reads your tech stack, deployment context and earlier decisions before it recommends anything.
AI Coding Agents
Query the VDB from inside your AI coding agent. The vulnerability answer arrives in the editor, while the branch is still open.
Fix path generation
Pix turns a CVE into a concrete code change, with step-by-step remediation covering dependency upgrades and patches.
We pay the data cost once, upstream
Every advisory is reconciled against the package registry, the distribution advisory and the upstream commit before it reaches you. A wrong affected-version range costs one developer the same hour whether the finding was real or not, and that is the bill bad data sends every team running a scanner on raw CVE feeds.
Pix answers in three modes. Rubber Duck: a fast, plain-spoken sounding board for debugging and triage. Kremvax: an auditability analyst for the evidence trail: what was scanned and why a decision holds up. Dark Avenger: a deep investigator that connects the audit trail to the wider threat picture.
Press Shift+Tab in Pix to cycle modes. Three ways to ask Pix
Hand the queue to agents that never clock off.
A security crew works a finding to a draft pull request behind four gates, with System One decisions on every tool call, on a machine whose image you can verify.
- System One: withheld: injection
- AI Firewall: passed
- Package Firewall: refused: malware
- Egress: passed
Your agent installs the dependency. Something should check it first.
A guide per agent, because the path each one reads is different. An agent only knows what its tools tell it. Vulnetix answers at the moment it adds a package, in the agent's own context, and stays silent when your policy is already satisfied. Reach it through the MCP server with no install, or wire hooks and skills locally with one command.
31 MCP tools and 18 workflow prompts
KEV deadlines, exploit intelligence, EPSS and SSVC, ranked remediation and pre-install risk checks, answered from live data. One URL, one header, in twelve MCP clients.
18 Skills, 5 subagents and 3 guard hooks
Typosquat checks, safe fixes, VEX publishing, PR security review and a dependency guard at the tool call. Apache-2.0.
$ vulnetix agent install
Detects the agents you have, wires each one. Free on every plan. AI analysis on the MCP server unlocks on Pro.
A safer LLM coding harness
Belai ships the guardrails the big labs leave out. Sealed delimiters with a nonce and SHA-256 hash, a security classifier on every untrusted tool result, and fail-closed posture gates, built into the harness rather than bolted on.
- Research malware through an agent that classifies tool output before it trusts it, so the bytes stay evidence rather than a running process.
- A forged context block, an unknown nonce, or a failed hash is stripped at egress. An agent cannot widen its own tool surface.
- The role manager segments untrusted content and Belai logs nothing. Your context window stays yours.
- A fixed-argv native tool catalogue, plan and goal modes, and a prompt library as files.
Govern every LLM call without touching a client library
One gateway in front of OpenAI, Anthropic, Mistral, Groq and nine more providers, 13 in all. Your engineers change base_url and nothing else. Model allowlists, regex guardrails and PII redaction apply identically whether the call came from a curl, a Codex turn, a Kiro session or a Claude Code tool result. The gateway and your key vault are free at every tier; policy unlocks on Pro and guardrails on Teams.
chat
OpenAI SDKs, LangChain, curl, most everything
responses
Codex CLI, whose config accepts no other wire API
messages
Anthropic SDKs, Claude Code, Claude Desktop
kiro
Kiro IDE and CLI, signed in with a stored Kiro login instead of an API key
- BYOK: Bring your own provider keys. They are held per organisation as KMS-encrypted ciphertext and decrypted just in time, never riding the request.
- LOGS: No prompts logged. Streaming responses are relayed untouched, as Server-Sent Events (an AWS event stream for Kiro).
- ROLLOUT: Roll a rule out as flag, then redact, then block, so nobody discovers the policy by having a build fail.
Agent governance · Teams
Rules for the tools, MCP servers, skills and clients your agents carry. The strip action removes one tool from a request, so the model is never offered it and the session keeps working.
What the repository declares, and what actually ran
AI-BOM from the code
Four evidence passes find every coding agent, SDK and model a project uses, including agents that leave only a commit trailer. CycloneDX 1.7, env var values never read.
Inventory from live traffic
Every tool, MCP server, skill and client your agents send through the gateway, including the MCP server someone wired in locally. Free on every plan.
Your AI inventory is already the evidence
The same inventory, firewall telemetry and triage decisions feed three AI reports, period-scoped and exportable as PDF, OSCAL and an evidence bundle.
Transparent and auditable: metadata only, every decision on the record.