Every replacement we build uses software you can read, run and keep without us. Here is each tool in one sentence, its licence, who maintains it, and where we use it.
Open-source infrastructure-as-code tool, a community fork of Terraform.
Linter that catches mistakes and bad practice in Terraform and OpenTofu code.
Checks infrastructure code for security misconfigurations before it is applied.
Official site ↗General-purpose policy engine; rules are written in the Rego language.
Runs OPA policies against configuration files and infrastructure plans in CI.
Wrapper around OpenTofu and Terraform for keeping many environments and accounts DRY. The core is free and open source (MIT); Gruntwork sells optional paid add-ons (Terragrunt Scale: pipelines, drift detection, support).
Self-hosted pull-request automation that runs plan and apply from code reviews.
Open-source secrets manager, a community fork of HashiCorp Vault.
Registry for container images and Helm charts, with scanning, replication and proxy caching.
Distributed object and file storage with an S3-compatible API.
Lightweight S3-compatible object storage for small and geo-distributed clusters.
Distributed storage for block, file and S3-compatible object storage (RGW).
In-memory data store, the open-source continuation of Redis 7.2.
Scanner for vulnerabilities and misconfigurations in images, dependencies and IaC.
Official site ↗Checks dependencies against the open OSV vulnerability database.
Static code analysis with readable, customisable rules.
Community fork of the Semgrep open-source engine.
Finds passwords, keys and tokens committed to Git.
Detects malicious open-source packages from code and metadata heuristics.
Generates a software bill of materials (SBOM) from images and file systems.
Standard format for software bills of materials, published as ECMA-424.
Keeps the SBOM of every release and alerts when a new vulnerability affects it.
Signs container images and other artefacts and verifies the signatures.
Collects findings from all scanners in one place, with owners, deadlines and accepted risks.
Short version: all of these tools can be run inside your company to build and operate your own systems. Most obligations only start when you distribute the software — or, for AGPL, when you offer a modified version to users over a network.
| Licence | What it allows | What it asks of you | Tools here |
|---|---|---|---|
| Apache-2.0 Permissive | Use, change and redistribute, also in commercial and closed products. Includes an explicit patent licence from contributors. | When you redistribute: include the licence, keep the notices and the NOTICE file, mark files you changed. | Checkov, Open Policy Agent (OPA), Conftest, Atlantis, Harbor, SeaweedFS, Trivy, OSV-Scanner, GuardDog, Syft, CycloneDX, Dependency-Track, cosign |
| MIT Permissive | Use, change and redistribute for any purpose. | Keep the copyright and licence notice in copies or substantial portions. | Terragrunt, Gitleaks |
| BSD-3-Clause Permissive | Use, change and redistribute in source or binary form. | Keep the copyright notice and conditions; don't use the authors' names to promote your product without permission. | Valkey, DefectDojo |
| MPL-2.0 Weak copyleft (per file) | Use and change freely; combine with your own code in a larger work under your own terms. | Only if you distribute outside your organisation: changed MPL files stay under MPL and their source must be available. Internal use creates no obligations (Mozilla MPL FAQ). | OpenTofu, TFLint, OpenBao |
| LGPL-2.1 / LGPL-3.0 Weak copyleft (library) | Use as is and combine with your own software under your own terms. | Only if you distribute: your changes to the LGPL code itself stay under LGPL; software that merely uses it may stay under your terms if it allows modification and reverse engineering for debugging (LGPL-2.1, sections 2 and 6). | Ceph, Semgrep Community Edition, Opengrep |
| AGPL-3.0 Strong copyleft, including network use | Use, change and distribute; run as a network service. | If you modify it and people use your modified version over a network, offer them its source code at no charge (section 13). Running it unmodified does not trigger this. | Garage |
Summaries of the licence texts and official FAQs listed below, for orientation only — not legal advice. If you ship products that include these tools or offer them as a service to others, have your counsel review the licences.
Tell us what you run today. A 30-minute call is enough to point you to the right replacement.