Paying to Avoid DevOps Work

The real product is not raw hosting, it is a managed deployment workflow that replaces an internal platform team for many web projects. Vercel and Netlify sit on top of AWS and similar clouds, so their markup pays for setup, rollbacks, support, and sane defaults. That trade works especially well for front end teams shipping marketing sites and new apps fast, where avoiding one DevOps hire matters more than squeezing infra cost to the minimum.

• In practice, the customer is buying pre wired CDN, file storage, routing, builds, and serverless functions in one place. A developer connects a repo, pushes code, and gets a live site without piecing together S3, CloudFront, CI/CD, and monitoring by hand.
  2 sacra
• This follows the old Heroku pattern. Heroku also charged a premium over raw cloud because teams were paying to avoid operating infrastructure themselves. The same logic shows up here, just aimed at modern JavaScript and Jamstack workflows instead of Ruby apps.
  4 sacra 5 sacra
• The breakpoint comes when usage or team size gets large enough that the platform fee exceeds the cost of hiring internal expertise. That is why startups and one off enterprise projects often start on Vercel or Netlify, while bigger companies may keep core systems on AWS and use these tools for speed sensitive launches.
  1 sacra 2 sacra

Going forward, this premium should hold as long as these platforms keep expanding what gets abstracted away, especially edge functions, previews, and integrated tooling around Next.js style workflows. The more of the app lifecycle they remove from manual cloud setup, the more they can charge for convenience instead of competing with AWS on raw compute price.