Working codename — rename pending (docs/03-roadmap.md).
A standalone, discovery-first control plane for bare-metal fleets: point it at your management network, and it finds, inventories, and provisions your servers — one service plus Postgres, standards on every edge, no Kubernetes required. See docs/01-product-brief.md for the full pitch.
Phase 1 of the roadmap (docs/03-roadmap.md): live BMC discovery, an inventory API + operator UI, OIDC auth with RBAC and an audit log, and a CLI — the smallest thing a design partner can run against a real management network. Not yet: deep hardware inspection at fleet scale, provisioning, or production hardening (Phases 2–4). Expect breaking changes; nothing here is released or versioned yet.
docs/quickstart.md takes you from a clone to a logged-in UI, a discovered fleet (real BMCs or a hardware-free virtual lab), and an inspected host with real CPU/memory/disk/NIC facts — every command copy-pasteable.
- docs/01-product-brief.md — what this is and why
- docs/02-architecture.md — system design, API & security, observability
- docs/03-roadmap.md — phased plan and exit criteria
- docs/04-build-vs-reuse.md — stack choices and dependency license policy
- hack/e2e/README.md — the hardware-free virtual lab used for development and e2e tests
Not yet chosen — a naming/licensing decision is a stated Phase 1 milestone (docs/03-roadmap.md). Third-party dependencies are restricted to permissive licenses (0BSD/MIT/BSD/ISC/Apache-2.0) regardless of what's picked for this project (docs/04-build-vs-reuse.md §2). Do not consume, redistribute, or build on this code until a license is in place.