u/Puzzleheaded-Bowl748

Hello,
hard no-coder here. I do pretty love vibe-coding. But honestly I am not that dev-ops skillfull. Is there options for hosting next-js and payload in the managed infrastructure? I did play hard around CF workers (worked legit) but honestly I did not know what's happening behind the hood, which is only thing scarying me the most :-D (can't safely say upcoming clients for this option). On the other side, I do love the set-up of front-end etc. and running over the vibe, which giving me much more flexibility.

Hope I am not alone in that situation :-D

I have been on Webflow since 2014, mostly client work. Lately I keep messing around with vibe-coding for my own projects and it is genuinely fun, the ceiling on what you can build is way higher. But it also made me realize something about why I still reach for Webflow on paid work.

When I ship a Webflow site, my job is the build. Design to Webflow, hierarchy, SEO, analytics, tracking, the conversion layer. Uptime, security, patching, all of that just is not my problem. Webflow eats it. If someone pokes at the site at 3am, not my night.

The second I vibe-code something and put it on my own server, all of that lands back on me. Database, secrets, auth, dependencies, updates. Vercel and friends take some of the weight off but that DevOps layer never fully disappears.

So I am curious how people here think about it:

For those doing client work, is the managed infrastructure a big part of why you stay on Webflow, or is it more the design workflow? Would you ever ship a vibe-coded build to a client, or does the maintenance side kill it for you?

And honestly, do you think Webflow keeps this edge as AI builders get better, or does it close over time?

Not trying to start a Webflow vs AI flame war, just genuinely interested where everyone draws the line.