Kief Morris at infrastructure-as-code.com nails it: having agents write reusable infrastructure code is far safer than letting them drive Terraform directly. But the ecosystem of composable components he envisions already exists—it’s called BigConfig.
In this reply, we explore how BigConfig’s package manager model gives agents exactly the high-level abstraction layer they need to go from “messy tourist” to reliable infrastructure composer.
Postgres is trusted because it is hardened by decades of production use. Most Terraform code is not. Here is why BigConfig packages aim for “Postgres-level” reliability — and a real incident that shows why it matters.
Can you build a professional-grade cloud platform without writing a single line of code? By leveraging BigConfig and AI, I created the blueprint of a full-stack infrastructure—complete with DNS, SMTP, and TLS—in just three minutes using nothing but Markdown and declarative data.
By treating infrastructure as “pure data” rather than complex scripts, BigConfig acts as the “React of DevOps,” encapsulating messy Terraform and Ansible logic into clean, reusable components. This post explores a hands-off workflow where a simple Markdown plan is transformed into a working blueprint, proving that with the right abstractions, non-technical users can manage non-trivial infrastructure as easily as filling in a configuration manifest.
Stop asking AI to write “assembly code” for your deployment. Writing 500-line Terraform files is brittle, verbose, and a recipe for hallucination. In this article, we explore a paradigm shift: Component-Based DevOps.
By using BigConfig and the “once” package, you can move away from manual scripting and toward a “React-style” architecture for infrastructure. Learn how to combine Claude Code with high-level abstractions to build your own personal PaaS on providers like Hetzner and OCI—achieving deterministic, zero-touch deployments without the DSL headache. It’s time to stop writing infrastructure and start composing it.
Drawing a parallel to the React revolution in frontend development, this article explores how shifting from Separation by Technology to Separation by Concerns can solve the modern infrastructure bottleneck. Learn how BigConfig uses a component-based approach to unify Kubernetes, Terraform, and Ansible, enabling modularity, interchangeability, and a “clean interface” for your entire stack.
Vibe coding has revolutionized how we build apps, but deployment is still stuck in the manual ages. Discover how BigConfig’s once bridges the gap, automating compute, DNS, and SMTP into a seamless pipeline that brings us one step closer to Natural Language Infrastructure.
BigConfig started as a modest script to simplify complex Terraform projects, but it has grown into something far more ambitious. By moving beyond the “library” mindset and embracing the role of a package manager for infrastructure, BigConfig overcomes the traditional barriers of language adoption. This article explores how a unified Clojure-based workflow—spanning the REPL, the Shell, and the Library—offers a total solution for developers tired of juggling fragmented YAML templates and rigid deployment schemas.
