Open-Source DevOps · camptocamp

terraboard

Terraboard is a web dashboard for visualizing and inspecting Terraform state files stored in S3, GCS, Terraform Cloud, or GitLab. It provides search, comparison, and version tracking capabilities to help teams audit infrastructure state and track changes over time.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/camptocamp/terraboard

GitHub stars

167

Forks

Primary language

Apache-2.0

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	camptocamp/terraboard
Owner	camptocamp
Primary language	Go
License	Apache-2.0 — OSI-approved
Stars	2k
Forks	167
Open issues	26
Latest release	v2.4.0 (2024-07-24)
Last updated	2026-06-15
Source	https://github.com/camptocamp/terraboard

What terraboard is

Go-based server application with a web UI that reads Terraform state files from multiple remote backends (AWS S3, GCS, Terraform Cloud, GitLab, S3-compatible stores), indexes them into a PostgreSQL database, and exposes search/diff functionality through a REST API and web interface.

Quickstart

Get the terraboard source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/camptocamp/terraboard.git2cd terraboard3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Multi-team Terraform state auditing

Centralized visibility into Terraform state changes across multiple teams and AWS accounts; enables resource discovery and state version history tracking without direct Terraform CLI access.

State migration and bulk operations

Compare state versions before and after migrations; identify resource discrepancies and validate Terraform plan impacts across multiple state files in a single dashboard.

Compliance and change tracking

Maintain an audit trail of infrastructure changes with timestamped state diffs; support compliance workflows by documenting who modified what resources and when.

Implementation considerations

PostgreSQL database is mandatory for storing indexed state data; plan for backup, recovery, and scaling as state file count grows.
AWS IAM/GCP service account credentials must grant s3:GetObject, s3:ListBucket, s3:ListBucketVersions, s3:GetObjectVersion permissions; tightly scope to least privilege.
State file versioning must be enabled on S3 buckets; disable via YAML config only for non-versioning backends (MinIO, etc.) to avoid data loss.
Multi-provider configuration requires YAML config file; environment variables/CLI flags only support single provider, limiting flexibility.
Authentication and TLS termination (if exposed over HTTPS) must be handled externally or via reverse proxy; Terraboard itself provides no built-in auth mechanisms.

When to avoid it — and what to weigh

Real-time state mutation monitoring required — Terraboard reads state files at configured intervals; it is not a live event stream. For immediate state change notifications, consider Terraform Cloud's run notifications or custom webhooks.
Single-user, ad-hoc Terraform usage — Overhead of running a separate PostgreSQL database and dashboard is not justified for small teams doing infrequent Terraform operations; `terraform state` CLI commands may suffice.
Sensitive state data with no encryption at rest — State files contain secrets (database passwords, API keys). Ensure PostgreSQL backend is encrypted and access-controlled; Terraboard does not encrypt the internal database by default.
Air-gapped environments without S3/GCS/Terraform Cloud access — Requires connectivity to remote state backends; not suitable for fully offline infrastructure.

License & commercial use

Licensed under Apache License 2.0 (Apache-2.0), a permissive OSI-approved open-source license. Permits commercial use, modification, and distribution with proper attribution and no warranty.

Apache-2.0 permits unrestricted commercial use, modification, and private deployment. No proprietary license required. However, verify that dependencies (PostgreSQL, frontend libraries, etc.) comply with your commercial policies. No warranty or commercial support terms are implied by the license alone; engage maintainers separately if SLA/support needed.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Adequate
License clarity	Clear
Deployment complexity	Moderate
DEV.co fit	Good
Assessment confidence	High

Security considerations

State files contain plaintext secrets (database passwords, keys, tokens). Terraboard reads and indexes these into PostgreSQL. Recommended mitigations: (1) Encrypt PostgreSQL at rest and in transit. (2) Restrict network access to dashboard via reverse proxy, VPN, or IAM. (3) Audit PostgreSQL user permissions and enable query logging. (4) Use S3 bucket policies to restrict who can list/read state files. (5) Rotate AWS/GCP credentials regularly. (6) No built-in authentication; delegate to external reverse proxy (nginx, Cloudflare, etc.) or SSO provider.

Alternatives to consider

Terraform Cloud/Enterprise

Official Terraform state management with built-in audit logs, cost estimation, and policy enforcement (Sentinel). Higher cost, closed-source, but eliminates need for separate dashboard and database.

Atlantis

Pull-request-driven Terraform workflow automation with integrated state visibility and plan review. Better for CI/CD-first teams; less suitable if you need historical state comparison without plan context.

Spacelift

Commercial SaaS platform for Terraform management with state visualization, policy engine, and teams. Proprietary, higher cost, but full-stack solution with support.

Software development agency

Build on terraboard with DEV.co software developers

Start with Terraboard's open-source dashboard to gain visibility into state changes, compare versions, and maintain compliance across your infrastructure-as-code deployments.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

terratest terragrunt terraform-kubestack

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source DevOps DevOps Cloud Deployment API Development Talk to DEV.co

terraboard FAQ

Does Terraboard modify state files?

No. Terraboard is read-only. It fetches state files, indexes them in PostgreSQL, and serves visualizations. It does not write back to state backends unless explicitly configured to push plans (optional feature).

Can I use Terraboard without Terraform Cloud?

Yes. Terraboard supports S3 + DynamoDB, GCS, GitLab, and S3-compatible backends (MinIO). Terraform Cloud is one of several supported options, not required.

How do I secure Terraboard in production?

Use a reverse proxy (nginx, Cloudflare) with authentication (OIDC, mTLS, IP allowlisting); encrypt PostgreSQL; restrict IAM credentials to least-privilege; enable S3 bucket versioning and access logging; rotate secrets regularly.

What happens if PostgreSQL goes down?

Terraboard cannot serve the dashboard, but state files remain untouched in remote backends. Rebuild the PostgreSQL database by refreshing state ingestion; data is not lost, only the index.

Work with a software development agency

Adopting terraboard is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source devops software in production.

Audit your Terraform state infrastructure today

Start with Terraboard's open-source dashboard to gain visibility into state changes, compare versions, and maintain compliance across your infrastructure-as-code deployments.

Talk to DEV.co Schedule a Consultation