Terraform-HTTP-Backend
Terraform-HTTP-Backend lets you self-host a Terraform backend and keep Terraform state files on your own system.
Platform availability
Available on 2 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
74/100 Good
- Maintained
- 100last commit 10 days ago
- Popular
- 9450,207 GitHub stars
- Easy to install
- 452 install platforms, install notes, Docker image
- Light to run
- 108 GB minimum RAM
Availability: platform listings confirmed today, links checked 33 days ago
- GitHub stars
- 50,207
- Open issues
- 1932
- Last commit
- 2026-11-11
- Latest release
- v1.17.2
- Activity
- declining
Checked 10 days ago - source: GitHub (hashicorp/terraform)
Resources & Compatibility
Minimum requirements: 8 GB RAM, 4 CPU core(s).
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Get the starter repo and run setup Clone the tfc-getting-started repo, move into it, and run scripts/setup.sh before starting. It downloads the example configuration and does new-user setup, so you don't start without the files Terraform needs to save its records. source
Fetched 54 days ago - each note links to its source
Variants
Alternatives (1)
- opentofu - OpenTofu is a command-line infrastructure-as-code tool that provides a community-driven drop-in replacement for Terraform.
Checked 54 days ago - source: AlternativeTo
Common questions
How should I supply credentials for the Terraform HTTP backend?
Use environment variables for credentials and other sensitive data. Hardcoding values or passing them with -backend-config can store them in the .terraform directory and plan files.
How do I change where Terraform stores its state?
Use the backend block to point Terraform at the desired state backend. Terraform documents initializing, changing, and unconfiguring backend settings.
Does a custom Terraform state server need locking?
Locking support is part of building a custom Terraform state server. It is covered together with authentication and real-world implementation patterns.
How are Terraform state uploads handled by the OpenWRT HTTP backend package?
Uploads are validated with Content-MD5. Large state files are streamed.
Do I still need a Terraform runner to use a self-hosted HTTP backend?
Yes, Terraform must be installed on the machine or CI/CD agent that executes Terraform commands. That agent can be a cloud VM or even a laptop.
Answers sourced from developer.hashicorp.com, developer.hashicorp.com, forum.openwrt.org, oneuptime.com, www.reddit.com
Community
- Self-hosted HTTP Backend : r/Terraform - Reddit (reddit)
- Terraform Http Backend : r/Terraform - Reddit (reddit)
- TFstate.dev: a Free Hosted Terraform HTTP Backend accessible using a ... (forum)
- [package] Terraform HTTP Backend for OpenWRT (forum)
- Terraform HTTP Backend : r/Terraform - Reddit (reddit)
- Latest Terraform topics - HashiCorp Discuss (forum)
Collected 48 days ago - public community threads