Generated from your infrastructure code, your templates and the live estate, and regenerated as the estate changes.
It describes what was true when someone last had time to write it down, and nobody trusts it enough to act on it.
The IT Operations Engine generates documentation from the infrastructure code, the templates and the live estate, and regenerates it as the estate changes.
What documentation has to be to be worth having
Documentation is produced from the sources of truth rather than written alongside them, so it stays current as a consequence of operating rather than as a separate task. Where a repository is built from a blueprint, the README explains how to run it, what it costs and how to tear it down.
Want to see the first generated set?
Read-only access to the accounts and repositories in scope is enough. It is usually available within days.
Nothing in the estate or the repositories is changed to produce it.
Access to the accounts and repositories in scope. The engine reads the infrastructure code, the templates and the running estate.
Architecture, inventory and security posture, plus the reasoning behind each change made and the evidence that it worked.
Every run produces its own evidence as a by-product. Onboarding artefacts are versioned and regenerated as the estate changes.
The engine produces it for the audiences you name, from security to finance.
You gain:
FAQ
Yes. The same discovery output can be curated for different readers.