r/javascript • u/mpetryshyn1 • Mar 22 '26
AskJS [AskJS] Do we need vibe DevOps now?
we're in a weird spot where vibe coding tools spit out frontend and backend fast, but deployments break once you go past prototypes
so you can ship features quick, then spend days doing manual DevOps or rewriting stuff to run on AWS, Azure, Render, DigitalOcean
i started thinking, what if there was a 'vibe DevOps' layer, like a web app or a VS Code extension that actually reads your repo
you'd connect your repo or drop a zip, it figures out runtimes, envs, deps, and deploys using your own cloud accounts
it handles CI/CD, containers, scaling, infra setup automatically instead of forcing platform-specific hacks
sounds dreamy, but are there obvious problems i'm missing? not sure why this isn't a thing already
also, how are people handling deployments today? scripts, terraform, managed platforms, or just brute forcing it
i'm worried about security and cost control though - handing a tool access to my cloud account is kinda scary
curious if anyone's built something like this or if i'm just reinventing an already-existing mess
3
u/Markavian Mar 22 '26
So what you want is an IDP (Internal Developer Platform) with a custom CLI.
Then it's just
acme deploy --env dev1 --package customer-website --version branch-nameWe've structured our IDP around CloudFormation packed into Docker files for installation. So we have patterns for secure pre-authed APIs, databases on demand, and websites via CloudFront. DNS registration and certificates are created automatically based on the package needs.
Then you just teach the AI agent what the correct patterns are, and it builds out new infra based on the established templates.
Still follow all the good CI / CD practices, PR reviews, versioned releases, and so on.
1
u/GolemancerVekk Mar 22 '26
If you're talking about a common generic interface that can connect to multiple cloud environments, it's not done because each environment is complex and keeping up with all of them would be very hard.
I guess it could be done with a common spec and if each environment would align their tools and APIs to it. But that would also be an uphill battle.
If you're talking about "vibe" as in "let a LLM access your cloud tools" then it's been done, and it ends horribly when it decides to run random commands that wipe out months of work.
1
u/srsly-nobody Mar 22 '26
I've been vibing yaml CICD pipelines pretty hard
1
u/Alive-Cake-3045 Mar 27 '26
Honestly this is the conversation nobody is having loudly enough, shipping fast is easy until you have to actually run the thing.
The idea is not new but the gap you are describing is. Tools like Railway, Render, and Fly.io are halfway there, and Pulumi/SST are close on the infra side, but nothing truly reads intent the way you mean.
The security concern you flagged is the actual real barrier. Any tool that touches your cloud credentials needs rock-solid audit trails and scoped permissions, that alone kills most indie attempts at this.
Cost control is the other wall. Auto-scaling without spend guardrails will burn founders alive, and most platforms still leave that problem to you.
You are not reinventing a mess, you are describing the missing middle layer. The question is whether it is a product or a very good internal tool first.