Zero-click and CVE response
Hunts deserialization sinks, SSRF and critical CVEs, then drafts a virtual patch before attackers find the way in.
Autonomous cyber defense
Kelvar's always-on agents watch your code and alerts, forge the fix, and record every action in a ledger you can verify.
curl -fsSL https://github.com/Faisalnwz01/vigil/releases/latest/download/install.sh | sh
macOS 14+ on Apple Silicon. Research preview.
Connects to GitHub today. Cloud guards are in preview
Point it at a repo. Kelvar audits it, records what it confirms, and returns a verdict you can gate a merge on.
$ python3 -m vigil.cli scan ./target-app
{
"verdict": "block",
"summary": { "critical": 1, "medium": 1 },
"findings": [
{ "check": "zero_click", "severity": "critical",
"path": "webhook_handler.py", "line": 4,
"message": "unsafe deserialization sink (zero-click RCE vector)" },
{ "check": "deps", "severity": "medium",
"path": "requirements.txt", "line": 1,
"message": "requests 2.30.0 affected by CVE-2023-32681" }
]
}
Ask an agent to audit a folder it can't see yet. It builds itself a read-only room, reads, and reports. Nothing is trusted until a check passes.
chat"Audit target-app for zero-click and CVE risk." The Zero-Click Rapid Defender picks it up.
authoring.applyA child worker is authored with read access to that one path and nothing else.
file.readSource files and dependency manifests, inside a sandbox limited to the admitted path.
security.findingSix confirmed on the sample repo: three critical, two high, one medium. Each carries file, line and advisory, and lands on the Findings screen.
file.writeIt prepares a minimal fix in an isolated git worktree. A deterministic verifier must pass before the ledger records a mark.
Each project pairs a specialist agent with a sandboxed room and a policy, so every check runs with only the access it needs.
Hunts deserialization sinks, SSRF and critical CVEs, then drafts a virtual patch before attackers find the way in.
AWS, GCP and Azure guards are in preview and do not scan yet. GitHub is the connected guard today. Read-only by default.
Audits lockfiles, workflows and look-alike packages on every pull request.
Finds leaked API keys and private keys in code, history and logs, and keeps SOC 2, HIPAA and PCI evidence current.
Triages SIEM and webhook alerts, links signals across surfaces and escalates only confirmed incidents.
Add GitHub or a SIEM feed. Cloud guards are in preview. Access stays read-only until you opt in to write-back.
Agents audit continuously and record each confirmed finding with the evidence behind it.
Risky merges and payloads are stopped at the gate. Fixes arrive as small patches built in an isolated worktree.
Findings, blocks and patches are written to an append-only, hash-chained ledger. A result is marked verified only after a deterministic check passes, never on a model's say-so.
Read the architecture$0
Local scans for secrets, vulnerable dependencies and misconfigured infrastructure code, from the CLI.
Run it free$49 per developer, per month
A daemon with watchers: pull request gate, on-push scanning, dependency and config drift, Slack alerts.
Book a demo$99 per developer, per month
Adds interception that blocks merges on critical findings, IaC and cloud config checks (live cloud guards are in preview), and a signed audit trail for SOC 2.
Book a demo$5k per month, and up
The Kelvar team runs the agents for you, so security coverage does not depend on a new hire.
Book a demoNeed it inside your own network? On-premise appliances start at $75k per year.
Not unless you allow it. Guards connect read-only, write-back is opt-in, and every change an agent makes is recorded in the ledger with the evidence that justified it.
On your own machine or on an on-premise appliance. Scans are local-first, and nothing leaves your environment except the model calls you choose to enable.
Any provider you connect, including local and custom models through an OpenAI-compatible endpoint. The kernel does not depend on a specific vendor.
Confirmed findings appear on the Findings screen with file, line and advisory. From there you can hand one to the patch agent, which prepares a minimal fix in an isolated worktree.