Repository navigation
Home
kraai is multi-provider infrastructure as code, driven by a manifest, with no state file. One manifest declares infrastructure and the code it runs, across AWS, Cloudflare and Neon today, applied with one command into your own accounts. Ephemeral per-PR and persistent environments are one abstraction over it.
Compared to Terraform: no state document — the manifest is the environment's state (see Architecture). No refresh phase — Terraform re-checks every tracked resource before every plan; kraai only looks up what the current manifest declares. One binary owns both provisioning and deploy, shipped the way Terraform itself ships.
- Architecture — what kraai is today, audited against the code.
- Decision Log — why each choice was made, and what it replaced. A history, not a description of what's currently true — read it for why, never for what is.
This wiki is reference material, not a task list. Work in progress lives in GitHub, not here:
- The project board and milestones — sequencing and status.
- The
unbuiltlabel — decided and reasoned about, not implemented. - The
dead-fieldlabel — a manifest field the schema parses that no code reads. - The
workstreamlabel — part of a sequenced, multi-issue plan.
Start with CONTRIBUTING.md
in the repo.