Google Cloud Organization Policy vs Tirith
Google Cloud Organization Policy
cloud.google.comTirith
github.comSide by side
| Figure | Google Cloud Organization Policy | Tirith |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | — |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | Yes |
| API | Yes | — |
| Plans published | 1 | 1 |
| Spec score · Infrastructure Policy as Code Tools | 8.8 (#3) | 7.1 (#19) |
| Intended users | The documentation describes organization policy administrators as configuring organization-wide constraints and project owners and teams as benefiting from compliance guardrails. | The project names DevSecOps engineers, infrastructure architects, cloud administrators, and others who manage or enforce infrastructure guardrails. |
| Notable limitation | Most organization policy enforcement is not retroactive, so a restriction on an existing action or state does not stop that existing behavior automatically. | The maker says there is no GitLab-native action equivalent, so GitLab users invoke the CLI directly. |
| Purpose | The service gives administrators centralized and programmatic control over Google Cloud resources by configuring constraints across a resource hierarchy. | Tirith evaluates infrastructure documents against declarative JSON policies and reports which rules passed or failed, including the affected resource and value. |
Plans
Google Cloud Organization Policy
- Organization Policy Service APIFree
In their own words
Google Cloud Organization Policy
Google Cloud Organization Policy lets administrators set constraints on Google Cloud resources across organizations, folders, and projects. Descendant resources inherit policies by default, so teams can establish restrictions across a resource hierarchy. Examples include limiting resource sharing by domain, restricting IAM service account use, and limiting where new resources may be created. Organizations can define custom constraints for resource creation and updates. Policies can be managed in the Google Cloud console, CLI, or REST API; the API exposes policy and constraint resources at organization, folder, and project levels. Dry-run policies record violations in audit logs without blocking the action, while Policy Intelligence tools can test proposed changes, identify non-compliant resources, monitor workflow impact, and show policy coverage. The service is free, with the Organization Policy Service API listed at free. Policies use YAML and JSON. Changes can take up to 15 minutes to take effect, and most enforcement is not retroactive. Basic Support is included for Google Cloud customers; paid technical support tiers are also available.
Tirith
Tirith is a free, open-source Linux command-line tool that evaluates infrastructure documents against declarative JSON policies. It reports passed and failed rules together with the affected resource and value. Its pipeline gate checks Terraform plan output and can return a nonzero exit code when a policy violation appears, before infrastructure changes are applied. Documented inputs include Terraform plans and state, Kubernetes manifests, Infracost breakdowns, and other JSON documents. Policies can use providers and evaluators such as ContainedIn, Equals, and RegexMatch, while the provider architecture can be extended for other formats. Local evaluation runs on the user’s runner, and the project says policies and documents are not sent elsewhere. Optional organization mode checks plans against StackGuardian policies and uploads a masked document. Tirith documents GitHub Actions, GitLab CLI use, Bitbucket Pipelines, other CI, and local execution. OpenTofu plans work like Terraform plans for the documented gate.