Headless APIs Replace Backend Labor
Lenny Bogdonoff, co-founder and CTO of Milk Video, on the past, present and future of Javascript
The real money sits in turning messy back end work into one clean API that front end teams can buy with a credit card. A headless CMS or frontend cloud is not just storing content or hosting files. It is replacing pieces of a database, app server, cache, image pipeline, deploy system, and admin panel, then wrapping them in docs, SDKs, previews, and permissions so a small team can ship without hiring backend specialists.
-
The product is expensive because it replaces labor, not because raw infrastructure is expensive. In Jamstack, teams stopped bundling a database with the web server, so tools like Contentful and Sanity became the place where editors update content and developers fetch it by API, which is a job old CMSs handled inside the monolith.
-
These businesses often resell commodity cloud at a large markup by bundling workflow on top. Vercel and Netlify package CDN, compute, routing, storage, and deploys into one push button service, and earlier research found Netlify and Vercel priced bandwidth well above AWS CloudFront. That is the same basic pattern Lenny is pointing to in CMS and Jamstack APIs.
-
Pricing works because the buyer compares it to headcount and launch speed, not to servers. Current list prices make that visible, with Contentful at $300 per month for Lite, Sanity at $15 per seat per month for Growth, and Vercel Pro at $20 per month plus usage. Those numbers are easy to justify if they save even a few hours of engineering time each month.
The direction of travel is toward more backend categories being sliced into premium APIs. CMS was an early wedge. Search, auth, media processing, databases, and edge compute follow the same playbook. The winners will keep charging infrastructure like software by owning the developer workflow, the editor experience, and the default path from code commit to production.