Hi Product Hunt, I built CostPilot to answer a narrow question: is infrastructure cost feedback more useful before merge than after deploy? CostPilot is a local CLI that estimates cost deltas from Terraform plans. It works by consuming terraform show -json output and evaluating changes entirely offline using embedded pricing data. There are no cloud API calls, no IAM roles, and no network access at runtime, which keeps the output deterministic and cheap enough to run in CI. The motivation came from a specific frustration. Cost feedback usually arrives after deploy, when the change is already merged and normalized. Terraform plans already describe irreversible infrastructure decisions, so estimating cost there makes it part of code review instead of a billing post-mortem. Design constraints I cared about: deterministic execution (same input, same output) fully offline execution intended to run before merge, not after deploy directional accuracy rather than billing-exact precision Real trade-offs: it cannot model runtime behavior like autoscaling or traffic it is weak at usage-driven costs such as egress it will not match provider bills to the cent This started as a small experiment extracted from real CI workflows. I am mostly interested in whether this timing and constraint set makes sense, not in building a general FinOps platform. Happy to answer technical questions or hear where this approach breaks down.

CostPilot

Terraform cost diffs at PR time. No IAM, no APIs.

Terraform cost diffs at PR time. No IAM, no APIs.