Infrastructure as Code

OpenTofu28.6k★

OpenTofu is the community fork of Terraform that stays truly open source. It's a drop-in replacement for Terraform, maintained by the Linux Foundation. MPL-2.0 licensed. You take your existing Terraform configs (.tf files), point them at OpenTofu instead, and everything works. Same HCL language, same provider ecosystem, same state management. The migration is almost trivial for most setups. Fully free. No paid tier from the project itself. Companies like Spacelift, env0, and Scalr offer managed OpenTofu platforms, but the CLI tool is free forever. The catch: OpenTofu tracks behind Terraform on new features: HashiCorp has more engineers. Some newer Terraform features (like the testing framework improvements) take time to land in OpenTofu. The provider ecosystem is shared, but if HashiCorp ever changes how providers work in an incompatible way, OpenTofu has to adapt. For most teams, this doesn't matter; infrastructure code doesn't need cutting-edge features. But if you're on the Terraform bleeding edge, check feature parity before switching.

Pulumi25.2k★

Pulumi lets you define infrastructure using real programming languages: TypeScript, Python, Go, C#, Java. Same concept as Terraform, but instead of learning a DSL, you use the language you already know with loops, conditionals, functions, and your IDE's autocomplete. Go, Apache 2.0. Supports AWS, Azure, GCP, Kubernetes, and 150+ providers. The state management works like Terraform: tracks what's deployed and diffs against your code. Pulumi AI can generate infrastructure code from natural language prompts. The CLI and engine are free and open source. You can self-manage state in an S3 bucket or local file, truly $0. Pulumi Cloud (managed state + team features) has a free tier for individual use: 1 user, unlimited stacks, 200 resources. Pulumi Cloud Team: $50/user/month: adds RBAC, audit logs, CI/CD integrations. Enterprise: custom pricing for SAML SSO, self-hosted options, and policy-as-code. Solo developers: free, self-manage state or use the free Pulumi Cloud tier. Either way, $0. Small teams: self-managed state works fine until you need collaboration features. $50/user/month for Cloud Team is steep if you're just managing a few stacks. Medium to large: Pulumi Cloud starts making sense for RBAC and audit trails. The catch: the ecosystem is smaller than Terraform's. Fewer blog posts, fewer Stack Overflow answers, fewer example configs. And using a real programming language is a double-edged sword: you CAN write bad abstractions and over-engineer your infrastructure code. Terraform's simplicity is a constraint that prevents some of that.

Packer15.7k★

Packer builds identical machine images for AWS, Azure, GCP, and VMware from the same configuration, defined in code. Packer does that. Instead of manually configuring a server and hoping you remember every step, you write a template that says "start with Ubuntu, install these packages, configure these settings" and Packer builds the image automatically. The entire tool is free under the BSL license (business source license, free for most use cases, restricted for competing managed services). No paid features, no cloud tier from HashiCorp specifically for Packer. You download the binary and run it. There's nothing to host; it's a CLI tool that runs on your machine and talks to cloud APIs. Install it, write a template in HCL or JSON, run `packer build`. It creates the image in your cloud provider and exits. Ops burden is trivial. Solo developers: useful if you're automating infrastructure. Otherwise, a manual AMI snapshot works fine. Small teams: Packer templates in version control mean everyone builds the same image. Growing teams: this is where it shines: golden images across multiple clouds, baked into your CI/CD. The catch: Packer solves one problem well but it's only the image layer. You still need Terraform or similar to deploy those images. And the BSL license change in 2023 upset the open source community; if you're philosophically opposed, look at alternatives.

Semaphore13.6k★

Semaphore gives you a web UI to manage and trigger your Ansible playbooks and shell scripts. It's a control panel for your DevOps automation. The open source version is useful: you get task scheduling, inventory management, team access controls, and a clean dashboard to see what ran and what failed. For a solo dev or small team managing a handful of servers, this is more than enough. Self-hosting is straightforward: single Go binary, throw it behind a reverse proxy, point it at a Postgres or MySQL database. Semaphore Pro adds LDAP/AD integration, audit logs, and priority support starting at $99/mo. Worth it if you're a growing team that needs enterprise auth. For everyone else, the free version handles the core workflow. Solo devs: use the free version. Small teams (2-10): free version covers you. Growing teams needing LDAP: evaluate Pro. Large orgs: you probably already have AWX or Terraform Cloud. The catch: it's not a CI/CD platform. If you need build pipelines and artifact management, look at Woodpecker CI or Jenkins. Semaphore is specifically for running automation tools through a UI instead of SSH sessions.

Crossplane11.7k★

You define an S3 bucket or RDS instance the same way you define a Kubernetes deployment, with a manifest. Completely free and open source under Apache 2.0. A CNCF incubating project, so it has serious backing. You get providers for all major clouds, the ability to compose custom APIs (called Compositions) that abstract infrastructure for your team, and drift detection built in. If someone changes something in the console, Crossplane reverts it. The catch: the learning curve is steep. You need to understand Kubernetes well before Crossplane makes sense. The abstraction layers (Providers, Managed Resources, Compositions, Claims) are powerful but feel over-engineered for simple infrastructure. If you just need to spin up a few AWS resources, Terraform is simpler. Crossplane shines when you want to offer self-service infrastructure to developers through a Kubernetes-native API. Solo: use Terraform instead. Crossplane is overkill. Small teams: still probably Terraform. Platform teams at growing companies: this is where Crossplane starts to make sense. Large orgs building internal platforms: Crossplane's sweet spot.

lift946★

Lift provides pre-built constructs that plug into your serverless.yml. It's essentially higher-level building blocks for AWS infrastructure alongside your Lambda functions. MIT license, TypeScript. Lift adds constructs like 'website' (S3 + CloudFront), 'queue' (SQS), 'storage' (S3), 'database' (DynamoDB), and 'webhook' with sensible defaults. Instead of 50 lines of CloudFormation, you write 3 lines of YAML. Fully free and open source. No paid tier. However, the Serverless Framework itself has gone through licensing changes; Serverless Framework v4 requires a paid subscription for organizations above a certain size. Lift is an MIT plugin, but it only works with the Serverless Framework. Solo developers on Serverless Framework: useful time-saver. Everyone else: look at SST or AWS CDK instead. The catch: Lift's value is tied entirely to the Serverless Framework ecosystem. If you're not using Serverless Framework, this does nothing for you. And with the Serverless Framework's licensing changes pushing larger teams toward alternatives like SST, CDK, or Terraform, Lift's future relevance is uncertain. The project appears to be in maintenance mode.