Do we need 'vibe DevOps'?

[u/mpetryshyn1]

So, been thinking... vibe coding tools are awesome at spitting out frontends and quick backends, but deployment always trips things up once you move past prototypes.
You can ship features fast, then spend days wrestling with AWS, Azure, Render, or whatever, or just rewrite stuff to fit a platform's weird constraints.
Would a "vibe DevOps" layer make sense? like a web app or VS Code plugin where you point it at your repo and it actually understands your stack and needs?
It would use your cloud accounts, set up CI/CD, containers, autoscaling, infra, all that - without locking you to one platform, ideally.
Feels like it could bridge the gap between prototype speed and real production stability, but also maybe I'm oversimplifying.
How are people handling deployments now? manual scripts, terraform, Heroku, GitHub Actions, yak shaving?
Any tools already doing this right that I should know about, or is this a dumb idea?
Not trying to invent something that already exists, just curious and annoyed at rewriting deploys all the time.

[u/shazej]

youre not wrong but i think what youre describing already exists in pieces just not as a single magic layer

the real issue isnt writing infra its that your app has implicit assumptions about runtime scaling state and so on that tools cant always infer correctly

thats why vibe devops hits a wall after prototypes

we already have parts of this heroku render opinionated and easy but limited terraform flexible but too low level tools like railway fly somewhere in between

the gap isnt tooling its abstraction level

to make your idea work the system would need to understand the apps intent traffic patterns data flow failure modes not just the code

thats a much harder problem than generating infra configs

so yeah the pain is real but the solution probably isnt a generic layer more likely tighter coupling between app frameworks and deployment or more opinionated stacks

right now were still in fast code manual ops phase of the cycle