Community
free- The Terraform provider
- A local server on your own hardware
- A living document for every resource
- Updated automatically on every apply
- The reason, written by a local model
Casefile
Documentation that updates itself.
A Terraform provider that keeps every resource documented, on hardware you own.
casefile/aws_security_group.web.md
# aws_security_group.web
Ingress for the public web tier.
Depends on aws_lb.public and aws_instance.web.
## Changes
### 2026-07-12
Opened 443/tcp from the ALB security group.
Why: TLS termination moved to the load balancer.
### 2026-07-09
Removed 0.0.0.0/0 on 22, scoped SSH to the bastion.
Why: closing the temporary admin rule from setup.
### 2026-07-01
Created with 80/443 ingress for the public web tier.
Why: initial launch of the marketing site.
Three lines of config, then nothing.
Casefile does its work during the apply you were running anyway.
-
Add it
Casefile goes into your Terraform config like any other provider, pointed at the server running on your own hardware.
-
Apply
On each apply the provider hands the change to the server, which records it against the resource and works out why it happened.
-
Read it
Every resource's history is Markdown in your repo. Read it there, during terraform plan, or from your own agents.
What ends up in your repo.
One file per resource, carrying its purpose, its dependencies and the reason behind every change.
A document for every resource
One living file per resource, holding what it is for, what it depends on, and every change ever made to it.
Written during the apply
The record is made by the run that made the change, so the documentation and the infrastructure cannot drift apart.
The reason, not just the diff
A model on your own hardware notes why a change happened, grounded in the commit that carried it. Missing context is flagged rather than invented.
Markdown in your repo
Plain files you can read, diff and review like any other code. There is nothing to export and nowhere else to look.
Context inside terraform plan
A resource's history appears beside its diff while you are reviewing it, so you approve with the background already there.
Terraform now, Ansible next
One local server behind both, writing into the same store, so the estate stays in one place as it grows.
Nothing leaves your network.
The server and the model both run on hardware you control. Casefile reads your state and writes to your repo, and no detail of your infrastructure is sent anywhere else.
That is also what lets it read things a hosted tool never could.
Free, with a Pro tier for teams.
The provider is free forever. Pro adds what a team needs to share the documentation and keep it current across everyone.
Pro
for teams- Shared across the team
- One store for the whole estate, in sync for everyone.
- Docs in the plan
- A resource's history surfaced inline during terraform plan.
- Your own model
- Point Casefile at a larger local or private model for richer notes.
- Control mapping
- Link resources and changes to the frameworks you report against.
Want to try Casefile?
Join the waitlist and we will email you when early access opens.
No spam. One email, when Casefile is ready for you.