Developer Tooling Sells Labor Savings
Lenny Bogdonoff, co-founder and CTO of Milk Video, on the past, present and future of Javascript
The core economic insight is that these tools sell labor savings at a markup, not raw infrastructure at the lowest price. A team pays Algolia, Heroku, or PlanetScale more than the underlying compute would cost because the product removes work like configuring clusters, tuning search, handling failover, and rolling back databases. That trade works best for small teams moving fast, and it breaks once usage or seat counts get large enough that in house ops becomes cheaper.
-
In practice, the buyer is replacing a specialist headcount with software. Heroku made deployment push button simple, and Milk Video used it despite paying a couple thousand dollars a month because database rollback, scaling, and backend maintenance no longer needed a dedicated engineer.
-
This pricing pattern shows up across the Jamstack stack. Vercel and Netlify package CDN, compute, routing, storage, and build workflows into one smooth developer flow, but their resale model creates price breakpoints where larger customers eventually move closer to AWS to cut cloud spend.
-
PlanetScale is the database version of the same bargain. It offers a managed MySQL compatible system built for scale, and companies accept higher bills because avoiding performance firefighting and database operations is worth more than bare metal savings during early growth.
The next wave of backend tools will keep winning first on convenience, then face pressure to justify premium pricing as customers mature. The durable vendors will be the ones that keep pushing the abstraction higher, adding workflows like branching, previews, and automated scaling that are annoying to rebuild internally, even after basic hosting and search become commodities.