boring-registry Terraform and OpenTofu Registry

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

boring-registry is a simple, open source registry for Terraform and OpenTofu modules and providers, a private and self hosted alternative to the public Terraform Registry. Point your developers and CI pipelines at a boring-registry server and they can consume your organisation's own modules and providers with the standard module and provider source syntax, while you keep full control over what is published and who can reach it. boring-registry implements the module registry protocol, the provider registry protocol and the provider network mirror protocol. This image delivers boring-registry fully installed and configured, running as a hardened systemd service behind nginx, so a working registry is answering within minutes of launch and you skip hours of manual setup, object storage wiring and access control hardening.

Self contained by design: boring-registry stores modules and providers in object storage, and this appliance bundles a lightweight S3 compatible object store on the same instance, bound to the loopback interface, so the registry works out of the box with no external cloud account or bucket to configure. boring-registry binds to loopback only and nginx is the single network facing surface, serving a public health check and the registry service discovery document, and reverse proxying the module and provider protocol to the registry. Module and provider archives are streamed back through the registry itself, so the object store never has to be reachable by your clients.

Secure by default with no shared credentials: nothing secret is baked into the image. On the first boot of every instance, boring-registry generates a unique API token that protects the registry protocol and unique credentials for the on box object store, and writes them to a root only file on the instance. Unauthenticated requests to the module and provider protocol are rejected, and publishing new modules and providers requires the per instance storage credentials. Point the terraform or tofu command at the registry with the per instance token and pull modules and providers immediately; publish your own with the bundled boring-registry command line.

Key capabilities: host your own Terraform and OpenTofu modules and providers privately; serve them over the standard registry protocols with a per instance API token; keep everything self contained on a single hardened instance with a bundled object store; publish modules and providers with the boring-registry command line; and mirror providers for reproducible, network isolated builds.

Get started: read the generated credentials, point terraform or tofu at this instance with the per instance token, and pull the bundled example module to confirm the registry end to end. Publish your own modules and providers with the boring-registry command line. cloudimg engineers can help you design registry topology, front the registry with your own TLS certificate and domain, wire it into CI and CD, and roll it out across your teams after purchase.

boring-registry is licensed under the MIT License. All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.