A web dashboard to visualize and query Terraform states from multiple backend providers.
Terraboard is a web dashboard for inspecting and visualizing Terraform state files. It connects to remote state backends like AWS S3, Google Cloud Storage, and Terraform Cloud to provide an overview of infrastructure state, search capabilities, and version comparison. It solves the problem of lacking visibility into Terraform-managed resources across teams and environments.
Infrastructure engineers, DevOps teams, and platform operators who use Terraform for infrastructure-as-code and need to monitor, audit, or troubleshoot state changes.
Developers choose Terraboard because it offers a free, self-hosted alternative to proprietary Terraform state visualization tools, supports multiple state backends simultaneously, and provides detailed diffing and search without requiring changes to existing Terraform workflows.
:earth_africa: :clipboard: A web dashboard to inspect Terraform States
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports AWS S3, Google Cloud Storage, Terraform Cloud, GitLab, and S3-compatible backends like MinIO, enabling centralized monitoring across diverse cloud and on-premises environments.
Allows querying resources by type, name, or attributes across all state files, with a dedicated search interface shown in screenshots, making it easy to debug or audit infrastructure.
Provides diff views between state versions to track infrastructure changes, as highlighted in the compare feature and screenshot, essential for change management and rollbacks.
Can configure and monitor states from multiple buckets or providers simultaneously via YAML configuration, ideal for large-scale operations with dispersed Terraform projects.
Requires external authentication proxies like oauth2_proxy, as admitted in the README, adding setup complexity and security management overhead for teams.
Needs a separate PostgreSQL instance for internal data storage, per the requirements section, increasing deployment footprint and maintenance effort.
Advanced configurations for multiple buckets or providers force use of YAML files instead of simpler environment variables, creating a steeper learning curve for initial setup.
Compatibility matrix shows limited support for newer Terraform versions, potentially causing issues with state files from latest Terraform releases without updates.