Skip to content

vibe operations

4 posts with the tag “vibe operations”

Why Agents Need an Infrastructure Package Manager

BigConfig as an infrastructure package manager for Agentic DevOps

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.

DevOps Without the Code: Infrastructure as Markdown

Once

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.

BigConfig: The "React" for Agentic DevOps

Once

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.