A registry for your modules and providers
Connect a repo, cut a release, and Platify packages and serves your Terraform and OpenTofu modules and providers - publicly or privately, with no BSL strings attached.
# resolve modules and providers from your private registry
module "vpc" {
source = "platify.io/acme/vpc/aws"
version = "3.2.1"
}
$ tofu init
Initializing modules...
- vpc: 3.2.1 fetched from platify.io ok
Initializing provider plugins...
- acme/aws 5.40.0 from platify.io ok
Platify resolved 2 modules, 1 provider Built to disappear into your workflow
The Registry does one job well: serve your modules and providers the moment a tag lands.
Installs as a Git app
Add Platify to GitHub or GitLab once. It listens for releases and tags. No pipelines to wire up.
Packages on release
Every tagged release is fetched, validated, and packaged into the registry protocol automatically.
Public or private
Publish a module to the world or keep it inside your org. Visibility is set per module.
OpenTofu & pre-BSL Terraform
Works with tofu and Terraform up to the last pre-BSL release. No license games, no BSL exposure.
Providers, not just modules
Host your own provider builds with signed releases and proper version constraints.
Drop-in registry protocol
Standard protocol, so source = "platify.io/..." just works in the config you already have.
How it works
Three steps from a tagged release to a resolvable registry entry.
Install the app
Add Platify to your GitHub or GitLab organization and pick the repos that hold your modules and providers.
Cut a release
Tag a release as you already do. Platify fetches it, validates it, and packages it into the registry.
Reference it
Point your config at platify.io/<org>/<name> and run tofu init. Versions resolve like any registry.
Get early access
The Registry is rolling out to early teams now, with Terrain and Kubernetes next. Leave your email and we will reach out as each opens up.
Registry questions
Which protocol does the Registry speak?
The standard module and provider registry protocol, so existing Terraform and OpenTofu configurations work without changes.
How are private modules authenticated?
Private modules are served only to authenticated members of your organization. Public modules are open to anyone.
Do you support providers as well as modules?
Yes. You can host your own provider builds with signed releases and version constraints, alongside your modules.
Is there any BSL exposure?
No. We package and serve OpenTofu and Terraform up to the last pre-BSL release only. Nothing under the BSL is involved.