Where it fits
Teams wanting an open CLI with reviewed configuration, state and provider ownership.
Trade-offs and limitations
It does not automatically replace HCP Terraform workflows or make cloud resources portable. Check exact migration and provider versions.
Deployment and technology
Go command-line application, provider plugins and a chosen state backend. Self-hosting requires a supported deployment, capacity planning and a named maintainer. Consult the official installation guide for the current version.
Portability and integration
| API | CLI, machine-readable output and provider-specific APIs |
|---|---|
| Authentication | Backend and provider credentials; separate execution from approval rights |
| Data export | Configuration and state backups; state may contain secrets |
Migration considerations
Back up state, pin versions and compare a non-production plan before applying changes. Never run concurrent writers against shared state.
Security and ongoing costs
Budget for infrastructure, implementation, monitoring, patching, backups, restore tests and user support. Check the supported release and current advisories with the project. An open licence is not a security guarantee.
Freedom score and exit difficulty
A complete, evidence-backed assessment of all 15 criteria is required before publishing a score. Exit difficulty depends on your customisations, data model, integrations and operating documentation. This profile does not claim a hands-on benchmark or a complete security assessment.
Primary sources
Profile reviewed 2026-09-13. Verify the exact release, edition and extensions before implementation.