Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
graph-go — simply nodes and graphs | Kitploit
Tools/GitHubGitHub/guilherme-grimm/graph-go
Cloud Infrastructure SecurityContainer SecurityNetwork MappingConfiguration AuditingDevSecOpsDatabase SecurityLog Analysis
GitHubguilherme-grimm/graph-go

graph-go

simply nodes and graphs

View Repository
12454115 days agoReviewed by Kitploit
Share

graph-go

See your infrastructure. Zero Config.

Point graph-go at your stack and get a live, interactive map of every database, table, service, and storage bucket — with real-time health monitoring.

License: AGPL v3 graph-go showcase: Docker auto-discovery, a container appearing live, and Kubernetes swimlanes

▶ Watch in full quality (MP4)


graph-go is a CLI-first infrastructure mapper. It auto-discovers your infrastructure by connecting to the Docker daemon, inspecting running containers, and probing databases and storage services. The UI is served by the backend and reflects real backend state — no manual inventory needed.

CapabilityDetails
Auto-discoveryDetects infrastructure from Docker containers and Kubernetes clusters — no manual inventory needed
KubernetesNamespaces, Deployments, StatefulSets, DaemonSets, Pods, Services — with informer-based real-time watching
DockerClassifies running containers, extracts credentials, watches Docker events, honors graphgo.* labels to override type/DSN/node-type/name or ignore a container
PostgreSQLTables, foreign key relationships, schema topology
MongoDBDatabases and collections
MySQLTables, foreign key relationships
RedisKeyspaces and key distribution
ElasticsearchIndices, cluster health, shard status
S3 / MinIOBuckets and top-level prefixes
HTTP servicesHealth endpoints, dependency mapping between services
Real-time healthWebSocket-powered live status updates every 5 seconds
Interactive graphSwimlane layout, namespace group containers, pan/zoom, filter by type/health, search nodes

Docker labels

graph-go respects a small set of graphgo.* container labels (set them on any container you want to control):

LabelEffect
graphgo.ignore=trueSkip this container entirely
graphgo.type=postgresForce the adapter type (postgres, mongodb, mysql, redis, elasticsearch, s3, http)
graphgo.dsn=...Inject a connection string (DSN for postgres/mysql, URI for mongodb, falls back to dsn otherwise)
graphgo.node-type=gatewayOverride the visual node type (service, gateway, auth, api, queue, cache)
graphgo.name=...Override the node name shown in the graph and used in node IDs / logs

Use these to rescue misclassified containers, point graph-go at a custom DSN, or hide a container from the graph without removing it.


Quick Start — try it in 30 seconds

Boot the seeded demo stack with the CLI. This is the fastest way to see graph-go against a realistic environment and the intended onboarding path for first-time users:

git clone https://github.com/guilherme-grimm/graph-go.git
cd graph-go
go run ./cmd/app demo

Open http://localhost:8080. The command runs attached via Docker Compose. Press Ctrl+C to stop the attached session.

The first run can take several minutes on a cold machine because Docker may need to pull base images and build the local demo images. Later runs are much faster.

The demo stack expects these host ports to be free: 8080, 5432, 27017, 9000, and 9001.

If you need an explicit teardown afterward:

docker compose -f docker-compose.demo.yml down

Run against your own stack

One container, one port. Mount the Docker socket read-only and graph-go auto-discovers everything running on the host:

docker run -d -p 8080:8080 \
  -v /var/run/docker.sock:/var/run/docker.sock:ro \
  --group-add "$(stat -c %g /var/run/docker.sock)" \
  ghcr.io/guilherme-grimm/graph-go:latest

The image runs as a non-root user, so --group-add grants it the socket's group (stat -c is Linux; on macOS start with --group-add 0). If Docker discovery still falls back to YAML-only, the startup log says what to change (including the exact --group-add value when that is the fix).

graph-go only reads from the Docker API (list, inspect, events). :ro does not restrict API calls, though: anything that can reach the socket can control the daemon. For least privilege, put a read-only API proxy such as tecnativa/docker-socket-proxy in front of the socket and point graph-go at it with DOCKER_HOST=tcp://<proxy>:2375 (no socket mount or --group-add needed). docker-compose.demo.yml shows a working setup.

Open http://localhost:8080. Auto-discovery handles Docker containers and (when a kubeconfig or in-cluster service account points at a reachable cluster) Kubernetes resources without any config file.

For services that live outside Docker/Kubernetes (remote databases, managed cloud services), mount a config file — see Configuration.


Pre-built binary

Single self-contained binary — UI is embedded, but the entrypoint is still the CLI.

# Linux amd64 (requires the GitHub CLI; browse Releases for other platforms)
gh release download --repo guilherme-grimm/graph-go --pattern 'graph-go_*_linux_amd64.tar.gz' --clobber
tar xzf graph-go_*_linux_amd64.tar.gz
./graph-go serve   # or just `./graph-go` - same thing

Open http://localhost:8080. Other platforms on the Releases page.


Commands

CommandWhat it does
graph-go demoBoot the seeded Docker Compose demo stack from the repository and stream its output in the foreground.
graph-go serveStart the HTTP server with auto-discovery and live updates (default - same as running with no args). Once the first discovery finishes it prints a ✓/✗ line per adapter to stderr, with what it found or why it failed (skipped with --log-format json).
graph-go scanRun discovery once and emit the graph to stdout. --format json (default) for piping into jq or CI checks; mermaid, markdown (Mermaid in a fenced block, renders on GitHub) or dot (Graphviz) for diagrams. graph-go export is an alias.
graph-go validateCheck the config file and exit non-zero if it's invalid. Reports every missing field, unknown connection type, and unknown key (which serve silently ignores). No server is started.
graph-go mcpServe the topology to AI agents over the Model Context Protocol (stdio). See Use with AI agents (MCP).
graph-go versionPrint version, commit, and build date.
graph-go --health-checkHit local /health and exit 0/1. Used by the container HEALTHCHECK; not for interactive use.

Global flags (apply to every subcommand): --config, --log-level, --log-format. See graph-go <command> --help for the full per-command surface.

Typical flow:

  1. graph-go demo for a realistic local walkthrough.
  2. graph-go serve to run against your own infrastructure.
  3. graph-go scan for one-shot automation, exports, or CI checks — e.g. graph-go export --format markdown --log-level=warn > ARCHITECTURE.md for a diagram that renders on GitHub.

Use with AI agents (MCP)

graph-go mcp gives coding agents (Claude Code, Cursor, any MCP client) a deterministic view of your infrastructure, so they stop guessing from compose files and manifests.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    786
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    506
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    429
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    345
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    262
  • 6

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    256

Explore all tools

Browse our collection of tools

View all tools →