kerkov.
GitHubInstall Kerkov
OPEN SOURCE / BUILT FOR SECURITY

Fewer blind spots.
More perspective.

Your AI security workspace. Investigate in conversation, connect the evidence, and see your attack surface take shape.

Explore the network map Explore the source
YOUR TERMINAL. YOUR TERMS.ALPHA

One line. You’re in.

Copy, paste, and start investigating.

curl -fsSL https://raw.githubusercontent.com/Kerkov-Security/kerkov/main/install.sh | bash
macOS & LinuxCLI · web console with --web
02Then run kerkov and choose your model.
Requires a published GitHub release.
Installation guide
Apache 2.0 licensed Your model, your credentials You control what runs CLI + local web console
01 THE NETWORK MAP

See the connections.
Follow the evidence.

Hosts, containers, services, and recorded access routes. Bring the engagement into one view, then inspect what connects it.

INTERACTIVE PREVIEW · SAMPLE DATA
kerkov / staging assessment LOCAL WORKSPACE

Network map

Your engagement, connected.

5 resources5 routesSAMPLE DATA
Select a host or route to explore
STAGING ENVIRONMENTENGAGEMENT 001
Observed Declared · unverified
100%
5 resources · 5 routes visibleIllustrative data · No scans run from this previewDrag to pan · + / − to zoom
01 /

Start from any origin.

See direct recorded routes from your runner or another origin. Understand the view from each point.

02 /

Every connection has context.

Inspect services, ports, and linked evidence. Observed routes and unverified declarations stay distinct.

03 /

Keep the whole picture.

Group host resources, recognize container endpoints, and explore the inventory saved to your engagement.

The map visualizes saved relationships, not live reachability or inferred transit paths.Explore the map guide
02 ONE CONNECTED WORKSPACE

From a question
to a clearer picture.

Work through an engagement in conversation. Your tools, specialist agents, inventory, and findings share the same context.

kerkov / staging assessmentSAMPLE
kerkovAUDIT MODE
❯

Map the staging API and review its access controls. Keep the findings linked to evidence.

✳

I’ll inspect the application, record the connections I can verify, and keep active testing behind your approval.

readInspect application routes
ledgerSave resources and connection evidence
approvalReview before active testing
❯ Follow a finding. Ask what’s next.

Investigate with real tools.

Read code, run commands, make HTTP requests, and drive a browser. Bring OpenGrep, ZAP, Syft, and Grype into the workflow.

Give specialists the right context.

Delegate focused work to agents with scoped tools. Follow their activity and bring structured reports back to the engagement.

You set the boundaries.

Choose your operating mode and approval policy. Save the engagement and pick up where you left off.

03 BRING YOUR MODEL

Your stack.
Your choice.

Use a hosted provider or a local model through Ollama.
The engagement stays with you.

Explore providers
AAnthropic✦GeminiNNVIDIA NIM↗OpenRouterDDeepSeekoOllama›_CodexYour credentials.
Your configuration.
A BETTER VIEW STARTS HERE

Open a terminal.
Find your perspective.

One command to install. A conversation to get started.

curl -fsSL https://raw.githubusercontent.com/Kerkov-Security/kerkov/main/install.sh | bash
Release installer · macOS & Linux
Installation guide Your first engagement