Formae now supports Kubernetes, Helm, .tfvars and a public plugin hub
Details
- External ID
- 48210240
- Source
- HN
- Company
- —
- Product
- Formae now supports Kubernetes, Helm, .tfvars and a public plugin hub
- Website domain
- github.com
- Launched
- May 20, 2026
- Cohort
- —
- Upvotes
- 9
- Upvotes percentile
- 0.5516962843295639
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:26 p.m.
- Updated at
- Sept. 7, 2026, 9:26 p.m.
Description
Hi HN! I’m Zach, co-founder / CTO of Platform Engineering Labs.We’re building formae, an open-source IaC system that stays in sync with real infrastructure instead of relying on manually maintained state and drift detection. We’ve just shipped Kubernetes, Helm, and Terraform .tfvars support.The goal with this release was simple: make it easy to start using formae with infrastructure people already have. formae can now discover existing k8s workloads automatically and the ability to utilize existing Helm charts.Coming from Terraform / OpenTofu and already have variable definitions everywhere? formae now supports consuming values from existing .tfvars files. You can manage whole k8s clusters - from VMs to workloads - in the same consistent model. Changes made through Terraform, Pulumi, kubectl, or cloud consoles are automatically discovered and synced back into formae.This release also includes the new public plugin hub, which is now home to our official plugins and, hopefully over time, community-built ones too.Links:https://github.com/platform-engineering-labs/formaehttps://platform.engineering/https://blog.platform.engineering/formae-now-comes-with-k8s-...We’d love feedback from anyone working in platform engineering, DevOps, or SRE.
Enrichment
- Theme
- Vertical
- Horizontal
- Function
- Dev tools
- Audience
- Developer
- AI stance
- Not AI
- Project type
- Commercial product
- Normalized one-liner
- infrastructure configuration management
- Manually corrected
- False
Could you build this?
No Building a continuous state-reconciling Infrastructure-as-Code engine across Kubernetes, Helm, and Terraform requires deep systems engineering, distributed state consensus, and cloud API edge-case handling.
What it would actually take: Formae requires building a state reconciliation daemon that interfaces with cloud control planes (AWS/GCP/Azure) and the Kubernetes API via custom controllers and CRDs. It needs a resilient DAG engine to evaluate dependency trees, handle partial failures, and perform non-destructive updates without conventional state locking. This demands high-level expertise in distributed systems, declarative convergence algorithms, and cloud provider schema internals.
Discussion
No comments on this launch.
Competitors
Other products that read as similar to this one — 52 launches clear the similarity bar, closest 8 shown.
Attention rank: #30 of 53 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 202 days after the earliest competitor.
- GitHub · ph · 2026-09-11 · 2 upvotes · similarity 0.43
- Chart Preview · hn · 2025-12-20 · 22 upvotes · similarity 0.43
- Building a Cloud Native Kubernetes Java Client · hn · 2025-10-30 · 6 upvotes · similarity 0.38
- Renovate · hn · 2026-02-11 · 43 upvotes · similarity 0.37
- Stateboard · ph · 2026-09-09 · 1 upvotes · similarity 0.37
- unclick · github · 2026-09-23 · 7 upvotes · similarity 0.37
- Titan · hn · 2025-12-11 · 49 upvotes · similarity 0.37
- Compose-to-Cloud Pulumi Providers for AWS, GCP, and Azure · hn · 2026-05-22 · 5 upvotes · similarity 0.36
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a dev tools tool for Sales yet.