[ About TFWeave ]
Built by platform engineers who got tired of being the ticket queue.
TFWeave is the golden-path platform for Terraform shops. We give infra teams a way to publish self-service templates that devs and PMs can use safely — without giving anyone production access, and without inventing a new IaC language.
Why we built this
Every platform team we've worked with has the same shape of problem: developers and PMs want to spin up infrastructure faster than the platform team can fulfill tickets. Existing options force a bad choice — either grant broad cloud access (and inherit the audit nightmare), or stay the bottleneck.
The "golden path" idea has been around for years. Spotify popularized it with Backstage. The pattern is right. But most implementations stop at a service catalog UI and leave the underlying Terraform unchanged — which means the same engineers who already wrote the modules are still the only ones who can run them.
TFWeave closes that loop. Your Terraform stays where it is, written how you write it. We add a thin layer that tags modules as self-service templates, enforces your policies on every invocation, and exposes them through interfaces non-engineers actually use — Linear tickets, Jira forms, a simple web UI, or just a PR comment.
What we believe
A few opinions that show up in how we build.
Boring is a feature
Platform engineers don't want clever. They want predictable. Every TFWeave decision optimizes for the third 3am incident, not the launch demo.
Native, not yet-another-DSL
We don't replace Terraform. We don't ask you to learn HCL-Plus-Plus. Your modules stay yours. We add a layer that publishes them safely.
Self-service or it isn't real
If devs and PMs still file tickets, you don't have a platform — you have a ticket queue. We measure success by how many requests never reach your inbox.
Guardrails over gates
Blocking everything is easy. Letting people ship safely is hard. We bias toward the latter — opinionated defaults, policy enforcement, audit by default.
Want to talk about your platform?
We're early. If you're running a platform team at a company with 50–5,000 services and you've been wrestling with the self-service problem, we want to hear from you.