boring-registry
An open-source Terraform and OpenTofu provider and module registry for self-hosting, supporting multiple storage backends.
What is boring-registry?
Boring-registry is an open-source registry for Terraform and OpenTofu modules and providers. It allows organizations to host and distribute their infrastructure-as-code components privately, serving as a self-hosted alternative to HashiCorp's public Terraform Registry. It implements Terraform's official registry protocols, ensuring seamless compatibility with existing workflows.
DevOps engineers, platform teams, and organizations managing private Terraform or OpenTofu modules and providers who need a self-hosted, reliable registry solution.
It provides a simple, protocol-compliant, and storage-agnostic registry that can be self-hosted on-premises or in the cloud, offering full control over module and provider distribution without relying on external services.
Overview
A Simple Terraform Provider and Module Registry
Use Cases
Best For
- Hosting private Terraform modules within an organization
- Self-hosting a Terraform provider registry for custom providers
- Creating a network mirror to cache and reduce dependency on external provider sources
- Using S3-compatible storage (like MinIO) for registry backend
- Implementing OIDC-based authentication for registry access
- Running a registry on Kubernetes via Helm deployment
Not Ideal For
- Organizations seeking a fully managed, SaaS-based registry with no self-hosting responsibilities
- Teams requiring advanced features like graphical user interfaces, automated compliance checks, or integrated CI/CD pipelines
- Small projects or individual developers who can rely entirely on the public Terraform Registry without private distribution needs
Pros & Cons
Pros
Implements official Terraform registry protocols, ensuring native compatibility with Terraform and OpenTofu without additional configuration, as stated in the overview.
Supports multiple object storage backends including S3, GCS, Azure Blob, and S3-compatible systems, allowing deployment in diverse environments as highlighted in the features.
Enables organizations to host and distribute their own modules and providers privately, offering full control over infrastructure components without relying on external services.
Includes pull-through mirroring to cache providers from upstream registries, reducing external dependencies and improving reliability, as noted in the features.
Cons
Requires manual setup and maintenance, including storage configuration and authentication, which adds operational complexity compared to managed services like Terraform Cloud.
Focuses on core registry functions; lacks built-in GUI, advanced analytics, or enterprise-grade management tools that some organizations may need for comprehensive IaC governance.
As a niche open-source project, documentation might be minimal for complex deployments, and community support could be limited compared to commercial alternatives with larger ecosystems.
Open Source Alternative To
boring-registry is an open-source alternative to the following products:
Frequently Asked Questions
Related Projects
terralistTerraform Private Registry for modules and providers manageable from a REST API
TerraregOpen source Terraform module registry with UI, optional Git integration and deep analysis. Demo: https://terrareg-main.gitlab-pr.dockstudios.co.uk
terraregOpen source Terraform module registry with UI, optional Git integration and deep analysis. Demo: https://terrareg-main.gitlab-pr.dockstudios.co.uk
tapirA Private Terraform Registry
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.