Vercel and Netlify as operating layer

Support is part of the product in cloud hosting, not an extra. Vercel and Netlify sell a layer on top of AWS that removes day to day DevOps work, gives frontend teams a cleaner path from Git push to production, and helps them avoid the moment where a developer suddenly has to understand buckets, CDNs, functions, billing, and edge config just to ship a site.

• The practical difference is who owns the messy parts. On Vercel or Netlify, a team connects a repo and gets previews, rollbacks, deploys, and framework specific defaults. On raw AWS, many of those same pieces exist, but the team often has to assemble and operate them itself, or pay internal DevOps talent to do it.
  1 sacra 2 sacra 4 sacra
• AWS products like Amplify narrow that gap, but the common pattern is a good on ramp followed by a handoff into the full AWS maze once the app goes off the happy path. That is where smaller platforms can win on support, because their value is staying opinionated instead of exposing every underlying service.
  2 sacra 3 sacra 4 sacra
• This also explains why startups often begin on Vercel or Netlify, then selectively move pieces to AWS later. The trade is paying markup for speed and hand holding early, then taking on more infrastructure work once scale, custom needs, or seat based pricing make owning more of the stack worthwhile.
  1 sacra 3 sacra 5 sacra

Over time, big clouds keep copying the best features of these abstractions, while the abstraction vendors keep moving up the stack on workflow and support. That pushes the market toward a split, AWS as the default infrastructure layer for very large or highly custom setups, and Vercel or Netlify as the default operating layer for teams that want to ship fast with fewer infrastructure specialists.