The Terraform Cost Estimator gives you a rough monthly cost estimate from your Terraform configuration without leaving the browser. It counts resources by type from the .tf you paste, multiplies each type by a fixed placeholder monthly rate, and produces a Markdown table plus a summed total. The goal is a privacy-first, order-of-magnitude sense of spend before you run a real plan, so you can catch obviously expensive shapes early.
Everything is computed locally. The estimator parses your HCL with a bundled parser, tallies resource blocks, and never contacts a cloud account or a pricing API, so secrets, instance sizes and topology stay on your machine. It is a deliberately simple approximation, not a billing system.
Because the rates are illustrative placeholders, treat the number as a conversation starter rather than an invoice. Pair it with a proper tool such as Infracost when you need accurate, usage-aware pricing. The estimator still earns its place for quick comparisons, teaching, and sanity checks during design reviews. For a production-grade number, export the JSON and feed it into a dedicated pricing pipeline, but the in-browser estimate is enough to flag a forgotten large instance before it is applied.
The estimator is also a good teaching tool. New engineers can paste a module and immediately see which resource types dominate the bill, reinforcing the habit of checking cost during design rather than after deployment. Because it runs offline, it works in locked-down environments where external pricing services are blocked, and it can be demonstrated in a workshop without network access.
Keep in mind the model is intentionally flat: it does not account for instance families, regions, reserved capacity, data transfer or storage growth. A fixed instance rate stands in for a small box and should not be read as a bill. The value is in relative comparison and early warning, not precision.