Tools we built for our own work, free to run on yours.
Each one answers a question an engineer has to answer anyway, from the files you already have. They run where you are, read rather than write, send nothing to us, and name the rule behind every finding.
Start with the one that matches your question.
EdgePQ Check
Post-quantum readiness for the AWS endpoints and keys in your Terraform.
- Runs
- In your browser. Nothing you paste leaves it.
- Needs
- Terraform, or the JSON from
terraform show -json
tfimpact
Which change in a Terraform plan destroys data, widens access or interrupts service.
- Runs
- On your CI runner or laptop. Nothing is sent to us.
- Needs
- The plan JSON from terraform show -json
Four promises, the same for every tool.
An engineer deciding whether to run something from a consultancy asks the same questions each time. The answers do not change from tool to tool.
Runs where you are
In your browser, on your laptop or on your CI runner. No InfraEdge server sees what you paste or scan.
Reads, never writes
Terraform, a plan, or read-only API calls. No tool here applies a change. What it proposes, a person reviews.
Sends nothing to us
No upload, no telemetry, no account. What you paste or scan stays with you.
Shows its working
Every finding names the resource it read and the rule it matched, so you can take the claim to the console or the documentation and check it before you act on it.
Each tool is the engine behind part of the paid work, published so the method can be checked before anyone is hired. If a tool shows work worth doing, an engineer can do it with you; if it shows nothing, you have your answer at no cost.
Built by the same engineer, with a site of its own.
A website rather than something you run, so the four promises above describe the tools, not this. It is here because the question it answers comes up in the same work.
A tool found something worth fixing?
Each tool is one piece of the paid work. An engineer runs it across your estate or your pipeline, reviews what it finds with you, and delivers the fixes as pull requests in your repository. Twenty minutes on a call tells you whether that is worth doing.