Infracost's JetBrains plugin shows you cost estimates for Terraform right in your editor! It also surfaces FinOps policies and tagging issues so you can catch problems before they reach production.
See cost estimates as code vision hints directly above Terraform resource definitions. Costs update as you edit.
Click a code vision hint to open the resource details panel, showing a full cost component breakdown, FinOps policy violations, and tagging issues.
The plugin highlights FinOps policy violations (with risk, effort, and potential savings) and tag policy issues directly in the sidebar. Blocking violations are clearly marked.
In addition to Terraform (.tf) files, the plugin supports CloudFormation templates in YAML and JSON.
Open the IDE and go to Settings -> Plugins -> Marketplace, search for Infracost, and click Install. Restart the IDE.
Using a different IDE? See the official installation docs for instructions on other supported editors.
Open the Infracost tool window and click Login to Infracost. This will open a browser window to authenticate your editor with your Infracost account.
Open a project containing Terraform files. The plugin will start the language server and begin scanning your project. Cost estimates will appear as code vision hints above resource blocks.
Use our CI/CD integrations to add cost estimates to pull requests, giving your team visibility into cloud costs as part of your workflow.
- A JetBrains IDE (IntelliJ IDEA, GoLand, PyCharm, WebStorm, etc.)
- An Infracost account
Go to Settings -> Tools -> Infracost to configure:
- Server path — path to the
infracost-lsbinary. Leave empty to use the bundled binary or find it on your PATH. - Cache TTL — how long (in seconds) to cache run parameters between API calls. Defaults to 300.
This plugin is a lightweight LSP client that connects to the infracost-ls language server. The server handles all Terraform/CloudFormation parsing, cost estimation, and caching. The plugin surfaces cost data via JetBrains Code Vision and a detail panel in the tool window.
We welcome contributions! Please start by opening a thread in GitHub Discussions to discuss your idea before submitting a PR.
If you run into any issues or have feedback, please open a thread in GitHub Discussions. We'd love to hear from you!