head to head · open source
OpenTofu vs iam-policy-json-to-terraform
OpenTofu has 30,703 GitHub stars, 1,414 forks, 320 open issues and last shipped yesterday. iam-policy-json-to-terraform has 816 stars, 58 forks, 19 open issues and last shipped 5 days ago. OpenTofu leads on adoption by 3,663% (30,703 vs 816 stars). OpenTofu is written in Go under MPL-2.0; iam-policy-json-to-terraform is written in JavaScript under Apache-2.0. OpenTofu has attracted 5% as many forks as stars, iam-policy-json-to-terraform 7%. OpenTofu was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| OpenTofu | iam-policy-json-to-terraform | |
|---|---|---|
| GitHub stars | ★ 31K | ★ 816 |
| License | MPL-2.0 | Apache-2.0 |
| Written in | Go | JavaScript |
| Last push | 2026-11-02 | 2026-10-29 |
| Forks | ⑂ 1.4K | ⑂ 58 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick OpenTofu if
- You weight community size — 31K stars and counting
- You want the MPL-2.0 license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
pick iam-policy-json-to-terraform if
- You want the iam-policy-json-to-terraform feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches JavaScript
- You evaluated both and iam-policy-json-to-terraform fits your workflow better
About OpenTofu
Homepage Slack Get Started OpenTofu is an OSS tool for building, changing, and versioning infrastructure safely and efficiently. OpenTofu can manage existing and popular service providers as well as custom in house solutions. Getting help and contributing Have a question? Post it in GitHub Discussions Open a GitHub issue Join us in the opentofu channel on the CNCF Slack! Want to contribute? Please read the Contribution Guide. Recurring Events Community Meetings on Wednesdays at 12:30 UTC (calendar) Technical Steering Committee Meetings every other Tuesday at 4pm UTC (calendar) [!TIP] For more OpenTofu events…
read the full OpenTofu overview →
About iam-policy-json-to-terraform
iam policy json to terraform Small tool to convert an IAM Policy in JSON format into a Terraform aws iam policy document Web Version Check out a web version of the tool here. For command line usage and automation, check out the instructions below. Installation OSX asdf Other Download the latest binary from the releases page and put it into your PATH under the name iam policy json to terraform Developer If you're a go developer and have your GOPATH defined and have added your $GOPATH/bin directory to your path, you can simply run this command. Usage From raw JSON From a JSON policy file If a video demo is more…
read the full iam-policy-json-to-terraform overview →
More in Infrastructure & Operations
Related comparisons
More Cloud Infrastructure Management projects
Compare either of these against the rest of the Cloud Infrastructure Management field.
Frequently asked questions
Is OpenTofu or iam-policy-json-to-terraform more popular?
OpenTofu has 30,703 GitHub stars and iam-policy-json-to-terraform has 816. OpenTofu has the larger community by that measure.
Are OpenTofu and iam-policy-json-to-terraform free?
Both are open source. OpenTofu is licensed under MPL-2.0 and iam-policy-json-to-terraform under Apache-2.0. Neither carries a licence fee.
What is the difference between OpenTofu and iam-policy-json-to-terraform?
OpenTofu is written in Go and iam-policy-json-to-terraform in JavaScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, OpenTofu or iam-policy-json-to-terraform?
Choose OpenTofu if you want the larger community (30,703 stars) or its MPL-2.0 licence terms. Choose iam-policy-json-to-terraform if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.