BitRavens
Coming 2027
AI agents that your tech infrastructure
Plug and play with any system or workflow. See how everything connects in one living map, with what-if simulations, EOL and CVE checks, insights, docs and access checklists. You decide how much goes on it.
Works with
Which one do you use?
> Map my workspace into BitRavens and document what you find. › orders-svc: Dockerfile says Postgres 12 and Redis 7 › orders-svc uses OPENAI_API_KEY: noted by name, never the value › Documented 9 systems from READMEs, CLAUDE.md and ADRs › Skipped .env values and ~/.ssh/id_ed25519 ok proposed 9 nodes and 11 edges, owners from CODEOWNERS ! postgres-main: Postgres 12 is EOL, 2 open CVEs i insight: postgres-main is a single point of failure for 3 systems ? What is 192.0.2.50:1433?
{
"mcpServers": {
"bitravens": {
"type": "http",
"url": "https://bitravens.com/mcp",
"headers": {
"Authorization": "Bearer ${BITRAVENS_API_KEY}"
}
}
}
}
$ bitravens what-breaks postgres-main orders-svc down depends_on (hard) checkout down via orders-svc admin degraded via orders-svc (soft) $ bitravens checklist offboarding ada Revoke SSH on db-server, admin on billing (via platform-team) Hand over orders-svc, sole owner: pick who takes it Steps rotate the Stripe key ada created
# .github/workflows/infra-map.yml on: [pull_request, push] jobs: infra-map: runs-on: ubuntu-latest env: BITRAVENS_API_KEY: ${{ secrets.BITRAVENS_API_KEY }} steps: - uses: actions/checkout@v4 - run: claude --mcp-config mcp.json -p "Map this change. On main, apply it." - run: npx bitravens check ✗ bitravens / impact test removing redis takes checkout down … bitravens / approval waiting on @platform-team, owner of redis
curl -X POST https://api.bitravens.com/v1/nodes \ -H "Authorization: Bearer $BITRAVENS_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "name": "postgres-main", "type_label": "postgresql", "properties": { "version": "12" }, "edges": [{ "to": "db-server", "kind": "runs_on" }] }' 201 matched PostgreSQL (verified) · version 12 ! EOL since Nov 2024, 2 open CVEs: plan an upgrade