Turn your IaC state into an interactive constellation.
Resources become planets, modules become galaxies, and dependencies form orbital links.
| Terraform Concept | TerraScope Metaphor | Example Visualization |
|---|---|---|
| Provider | Star type | Color or spectrum per provider |
| Module | Galaxy | Grouped cluster with faint halo |
| Resource | Planet | Size by importance or cost hint |
| Data source | Moon | Smaller orbiting body |
| Dependency edge | Orbit/Link | Line with arrow and weight |
| Drift or taint | Storm cloud | Particle effect or outline |
- Constellation view: force-directed graph of resources and modules
- Orbit view: module-centric “solar system” where resources orbit modules
- Timeline: play changes across commits or releases
- Policy lens: highlight resources violating tagging or compliance rules
- Click to open a resource panel: type, provider, attributes (sanitized), lifecycle, dependencies
- Filter by provider, module, tag, environment
- Search bar with fuzzy search on addresses (
module.app.aws_s3_bucket.assets) - Snapshot compare: diff two states and highlight adds/changes/destroys
- Conventional commits:
feat:,fix:,refactor:,docs:,ci:,build:,test: - Keep the service stateless; use object storage for optional snapshots
- Use IaC for deployment (Terraform, Pulumi, or Helm)
- Implement CI/CD with automated tests and image builds
- Enforce least privilege for any backend reads
- Provide clear docs for local dev, cloud deploy, and supported backends
- Add redaction options to mask sensitive attributes before rendering
Terraform State (local upload or remote backend)
=> Parser / Normalizer (API)
=> Graph Builder (nodes, edges, metadata)
=> REST / WebSocket
=> Frontend (React + Three.js)
=> Interactive Constellation UI
terraform.tfstateJSON (local or remote backend)- Optional:
terraform plan -jsonfor planned changes - Optional:
terraform graph -jsonfor explicit dependency graph