CIG

Compute Intelligence Graph is a self-hosted infrastructure intelligence platform for discovery, graph modeling, querying, cost analysis, and security review across cloud environments.

Primary public domain: https://cig.lat/

Current State

The repository contains a working core platform plus a few scaffolded areas that are not finished yet.

Implemented

• Dashboard application with resource views, graph visualization, costs, security, and Playwright E2E coverage
• Fastify API with REST, GraphQL, WebSocket, auth, rate limiting, and metrics
• Neo4j graph engine with traversal and circular dependency handling
• Discovery orchestration plus Python Cartography service
• RAG/chatbot pipeline and agent packages for query reasoning and actions
• CLI for install, connect, deploy, seed, reset, and status workflows
• Docker Compose and Terraform infrastructure scaffolding

Still Scaffolded or Partial

• apps/landing is present but still minimal
• apps/wizard-ui is mostly a bare Next.js scaffold
• packages/sdk is scaffolded and not feature-complete

Repository Layout

apps/
  dashboard/     Main Next.js dashboard UI
  landing/       Public landing site scaffold
  wizard-ui/     Installation wizard scaffold
packages/
  agents/        OpenClaw and OpenFang agent logic
  api/           Fastify REST, GraphQL, and WebSocket API
  chatbot/       RAG and vector retrieval pipeline
  cli/           CLI commands and credential handling
  config/        YAML config loading and validation
  discovery/     Discovery orchestration and scheduler
  graph/         Neo4j graph engine
  iac/           Terraform modules
  sdk/           SDK scaffold
services/
  cartography/   Python FastAPI discovery service
infra/
  docker/        Container build definitions
  terraform/     Infrastructure definitions
docs/            Organized project documentation

Quick Start

Prerequisites

• Node.js 20+
• pnpm 9+
• Docker Engine or Docker Desktop
• Docker Compose

Install

pnpm install

Start local infrastructure

docker-compose -f docker-compose.dev.yml up -d

This starts the local service dependencies used by the platform, including Neo4j and Chroma.

Start application code

For focused development, start only what you need:

pnpm dev:dashboard
pnpm dev:api
pnpm dev:landing

You can also start the whole workspace:

pnpm dev:all

When multiple Next.js apps run together, they will use the next available local ports.

Build

pnpm build

Or build a single workspace:

pnpm build:dashboard
pnpm build:api

Common Scripts

Development

pnpm dev:dashboard
pnpm dev:landing
pnpm dev:wizard-ui
pnpm dev:api
pnpm dev:agents
pnpm dev:chatbot
pnpm dev:cli
pnpm dev:discovery
pnpm dev:graph
pnpm dev:sdk
pnpm dev:all

Validation

pnpm test
pnpm lint
pnpm version:validate
pnpm version:status

Release

pnpm release:dry
pnpm release:patch
pnpm release:minor
pnpm release:major

Testing

• Unit and integration tests run with pnpm test
• Dashboard E2E tests run from apps/dashboard with pnpm test:e2e
• Security testing notes: docs/testing/security.md
• Performance testing notes: docs/testing/performance.md

Documentation

• Docs index: docs/README.md
• Architecture notes: docs/architecture/README.md
• Development notes: docs/development/README.md
• Deployment notes: docs/deployment/README.md
• Reference notes: docs/reference/README.md
• Historical material: docs/archive/README.md

Additional root-level project records:

• Current status snapshot: PROJECT_STATUS.md
• Versioning workflow: VERSIONING_GUIDE.md
• Versioning upgrade notes: UPGRADE_SUMMARY.md

Notes

• The root README is intended to describe the current codebase conservatively.
• Historical planning documents have been moved under docs/archive/ to separate them from active documentation.
• If you are trying to understand implementation status, treat the codebase and the docs index as the source of truth before older blueprint documents.
• Conversational Interface (RAG)
• Infrastructure Actions
• CLI & Installation
• Multi-Cloud Support
• Cost & Security Features

🟡 In Progress

• Testing & Hardening (85%)
• Documentation & Release (40%)

See PROJECT_STATUS.md for detailed status.

---

🔧 Version Management

This project uses @edcalderon/versioning v1.4.7 for:

• ✅ Version synchronization across all packages
• ✅ Auto-generated workspace scripts (dev:all, build:all)
• ✅ Private package leak prevention
• ✅ Cleanup utilities
• ✅ Branch-aware versioning

All packages maintain version 0.1.0 in sync.

---

📝 License

TBD - To be determined before v1.0.0 release

---

🙏 Acknowledgments

• Cartography - Infrastructure discovery
• Neo4j - Graph database
• LangChain - LLM framework
• @edcalderon/versioning - Monorepo versioning

---

📞 Support

• 📖 Documentation: See docs/ directory
• 🐛 Issues: GitHub Issues (TBD)
• 💬 Discussions: GitHub Discussions (TBD)

---

Built with ❤️ for infrastructure engineers