Infrastructure as Code
Compare IaC tools including Terraform, Ansible, Pulumi, and CloudFormation for automated infrastructure provisioning.
9 results in Infrastructure as Code
Active Pro listings from this category appear first. Your sort applies within Pro and Free results.
Shortlists for Infrastructure as Code
Explore collections with tools relevant to this category, grouped by deployment, source model or workload.
Open-source CI/CD tools for engineering teams →
2 matching tools from this category
Self-hosted IT tools →
8 matching tools from this category
IT tools with an API →
7 matching tools from this category
How to choose infrastructure as code tools
Infrastructure as code tools describe servers, networks, clusters and cloud services in version-controlled files, then create or change the real resources to match. The category covers declarative provisioning engines, SDKs that define cloud resources in general-purpose programming languages, agentless configuration management that sets up machines after they exist, and orchestration layers that run plans from pull requests with policy checks and state management. Cloud providers supply the resources, while these tools define and reconcile them.
Who uses these tools
- Platform engineers standardising cloud environments
- Sysadmins automating server configuration
- Security teams enforcing policy on infrastructure changes
Capabilities to compare
- Provider coverage across clouds and SaaS APIs
- State storage, locking and drift detection
- Plan previews in pull requests
- Policy as code and approval gates
- Reusable modules and templates
Operating considerations
- Licence changes affecting source-available engines
- State files often contain secrets
- Learning curve of a domain-specific language
- Runner concurrency pricing in orchestration platforms
Selection checklist
- Check the provider or module coverage for every cloud and service you need to manage.
- Decide where state lives, how it is locked and who can read the secrets it contains.
- Run a plan and apply through a pull request workflow to judge the review experience.
- Review the licence terms and any community forks before committing a large codebase to one engine.
What belongs in this category: A product qualifies when it defines infrastructure or machine configuration as code and applies it automatically, or when it orchestrates, reviews and governs those code-driven infrastructure changes.
Infrastructure as Code on iThub in figures
iThub lists 9 tools in Infrastructure as Code. 5 of 9 are open source, 8 of 9 can be self-hosted, 8 of 9 have a free, freemium or open-source pricing model and 7 of 9 offer an API.
- Tools listed
- 9
- Open source
- 5
- Self-hostable
- 8
- Free to start
- 8
- With an API
- 7
- Web app
- 2
- Desktop app
- 5
Recently added: Terrateam (Stategraph Orchestration), Atlantis, MiniStack, Hetzner Cloud
Typical use cases
- Provisioning identical staging and production environments
- Configuring many servers without installing agents
- Reviewing infrastructure changes in pull requests before applying
- Detecting manual changes that drift from code
Trade-offs to model
- A declarative configuration language is easy to review, while general-purpose languages offer loops, tests and abstractions at the cost of complexity.
- Running plans from your own CI is cheap, whereas a dedicated orchestration platform adds policy, drift detection and audit trails.
Common mistakes
- Committing state files or plain secrets to the repository where anyone with read access can see them.
- Mixing manual console changes with code-managed resources, which causes surprise deletions on the next apply.
Compare Terraform and Pulumi →Cloud providers and hosting →Containers and Kubernetes →
Continue the technical evaluation
Use the resources that match your decision stage. Profile data and linked sources were refreshed through November 11, 2026.
