Terrateam

The plan output belongs in the pull request.

What it is sold for

Running infrastructure changes through git review.

Named alongside

These entries mention each other by name. It is a weak relationship and it is the only one the catalogue can show without inventing something.

Names:

• Terraform
  The declarative infrastructure tool that made state files and plan output an industry convention.
• Pulumi
  Infrastructure as code in general-purpose languages, so loops, types and tests come from the language rather than from a DSL.

Same shelf

The rest of ci, cd and infrastructure, alphabetically. Sharing a category is a filing decision, not a relationship.

• Abstra
  Automation for finance operations, built as workflows rather than as spreadsheets.
• Ansible
  Agentless configuration management over SSH, with playbooks in YAML and no daemon on the target.
• AWS Step Functions
  Orchestrates AWS services as a state machine, so retries and failure branches are configuration rather than code.
• Buildstash
  Artifact and release management for teams shipping binaries: mobile, desktop, games, XR and embedded.
• Camunda
  Process orchestration for long-running work that spans people, systems and now agents, with the model as the executable.
• CircleCI
  A hosted CI platform, one of the older ones, now marketing itself around validating machine-written changes.
• Datadog
  Metrics, logs, traces and a great deal more in one platform. The default answer for large-scale monitoring, and priced like it.
• DeployHQ
  Deploys from a git host to servers with build steps, zero-downtime releases and one-click rollback.

All 34 in ci, cd and infrastructure