Workflow Is the Product
Vercel, Netlify, and the consumerization of developer tools
The real product is not hosting, it is the removal of infrastructure work from the front end team’s day to day job. Vercel and Netlify take jobs that normally mean wiring up S3, CloudFront, DNS, serverless functions, rollbacks, preview environments, and deploy scripts, then turn them into a Git based flow where a commit creates a live preview and production deploy with sensible defaults. That lets a small React team ship like it has a platform team, and charge a markup for convenience on top of commodity cloud services.
-
What developers are buying is a workflow. Push code to GitHub, get a preview URL in the pull request, merge, and the site goes live. That is the same basic value Heroku created earlier for app servers, but adapted to CDNs, static builds, and serverless functions for modern web teams.
-
The bundle matters because most teams do not want to configure each piece separately. In practice this means preconfigured storage, CDN delivery, routing, lambdas, rollback, and edge behavior. Building the same stack directly on AWS is possible, but it shifts time from product work into infrastructure setup and cloud bill management.
-
This model works best at startup and prototype scale, where speed beats unit economics. As traffic and customization needs rise, larger companies often keep the workflow for new projects but move heavy workloads onto their own cloud stack, because the markup becomes harder to justify at enterprise volume.
The next step is deeper verticalization of the same wrapper. Vercel already pulled the framework closer with Next.js, and both companies have pushed further into edge functions and richer app behavior. The winning platforms will keep absorbing more of the stack, while preserving the feeling that shipping a web app is as simple as pushing code.