AI is eating your moat(josepvidal.dev)

5 pointsby jvidalv2 hours ago3 comments

rowbinan hour ago
I think this conflates setup cost with operating cost. The painful part of self-hosting was always to get it working: writing configs, reading docs, SSH ceremony. That's exactly the part that agents can help with a lot, so the perceived gap to Vercel shrinks a lot. But the problems that come later are still there, you just discover it later. DDoS absorption, zero-downtime rollbacks, cert rotations failing at 3am, someone else getting paged when they do. An agent can write my firewall rules, but it doesn't carry a pager.
So I'd reframe the thesis a bit: AI didn't destroy the moat, it moved it. Saving the customer setup time is no longer worth paying for, taking operational liability for the customer still is. SaaS that only offer the former are indeed in trouble, and honestly founders should verify that their product doesn't have this issue.
- jvidalvan hour ago
  Fair reframe, and I agree more than I disagree.
  It's actually why I stopped at Railway level instead of going full VPS.
sinoue2 hours ago
Reducing friction and commoditizing make this an economic argument.
- jvidalvan hour ago
  Exactly, it always was one. The UX premium was a price on friction, and agents are pushing the price of friction to zero.
newaccountman22 hours ago
> I would have never switched before agents, barring some extreme necessity, but now an agent writes for us the Dockerfile, the build config, the deploy file, all of it, from one prompt.
Really? That's too hard for the author without an LLM agent?
- jvidalvan hour ago
  It's not about hard, it's about priorities.
  I wouldn't switch from Vercel just to save X% per month, because the real cost was all the extra time to build and maintain the infrastructure myself. The savings never justified the hours.
  With agents that math changes. The build and maintenance work moves onto the agent, so the savings threshold where switching makes sense drops a lot.
  On top of that there are other goodies. Vercel is serverless, so you can't co-locate the API with the DB, which means extra latency and yet another bill (Supabase?). That's one more thing you can now own for basically no effort.