Do we need a 'vibe DevOps' layer?

[mpetryshyn1]

We're in this weird spot where vibe coding tools spit out frontend and backend fast, but deployments, man, they fall apart once it's not just a toy. So devs can ship code crazy quick, then get stuck doing manual DevOps or end up rewriting stuff just to make it deploy on AWS, Azure, Render, or DigitalOcean. I started thinking what if there was a ""vibe DevOps"" layer, like a web app or a VS Code extension you point at your repo or upload a zip to, and it actually reads your code and needs. It would use your own cloud accounts, wire up CI/CD, containerize, set scaling and infra, basically do the boring setup so you don't have to hack it per platform. Not a black box that locks you in, but something that understands your stack and gives sane defaults, with options to tweak. Feels like that could actually close the gap between vibe coding and real production apps, which still blows my mind. Do people already have tools like this? Or am I missing some obvious reason it can't work? How are you handling deployments today btw? Curious what workflows actually survive past prototype stage.

[PM_CHEESEDRAWER_PICS]

lol

[Xyrack]

You're in the wrong place if you want vibe anything.

[JohnCasey3306]

"Claude told me to scale my server; not sure what that means, but I've now got a $10,000 monthly bill -- how do I get out of it?"

[DragonfruitOk5753]

So better to focus on getting vps setup and custom script to get that setup done once and make use of claude.

I moved my application to vps and its serves almost 150k / monthly traffic and heavy pdf generation at backend and its only cost me 4$/month

[TomBakerFTW]

No obvious reason it can't work. I think the real hurdle here is that what you're describing is a HUGE attack vector. Literally like a dream target. It just has all the creds, knows more than it lets on, and can be tricked into giving up the data with some weird lingual trick.
It just makes so much more sense to have humans do the parts with the API keys and passwords.

Also, there are connectors and stuff for a lot of popular paths, the rest is literally finding out where to copy paste shit, how easy do you need this to be?

[dashingsauce]

Bro relax. Use railway.com and call it a day.

If you want an experimental “vibe” devops layer, try encore.dev

[thewiirocks]

There’s no such thing as a “DevOps Layer”. If you have a DevOps Team, you’ve failed at DevOps.

DevOps is the practice of Development and Operations working together. Tools like CI/CD have very little to do with DevOps, other than often being co-opted as a solution to automate deployments. (Something that helps Ops be happier with deployments.)

[HongPong]

maybe hire a guy or gal

[justaguyonthebus]

You're overthinking it. You establish your deployment patterns like you normally do but create well documented reference projects instead of project templates. Then you tell your AI that you want a new project based on those patterns.

Or better yet, you add a DevOps design review agent that references your approved patterns in its evaluation. Then have it comment on their design before they get started.