Jamstack Frontends as Control Plane
Bucky Moore, Partner at Kleiner Perkins, on Jamstack's big upside case
This is how Jamstack tries to avoid becoming another Heroku. Instead of forcing developers onto one bundled backend, the winning front-end platforms aim to sit in the middle of an open supply chain of databases, auth tools, search, payments, and CMS products. In practice, that means a team can deploy the site on Vercel or Netlify, keep product data in Shopify, content in WordPress or Contentful, and application data in PlanetScale or CockroachDB, all without rewriting the front end when one backend piece changes.
-
The core lesson from Heroku is that developers love abstraction until it blocks a later infrastructure choice. Jamstack platforms responded by making deployment, preview links, rollbacks, and edge delivery easy defaults, while leaving the database and API layer modular.
-
That modularity only works because the backend market matured. PlanetScale sells MySQL-compatible serverless databases with branching, which gives developers isolated database copies for testing schema changes. CockroachDB sells distributed SQL for apps that need resilience and global scale. Those products can plug into a Jamstack app instead of being replaced by it.
-
The pull into the ecosystem is literal, not rhetorical. Vercel now has integrations and marketplace flows for third-party products, plus templates that package a front end together with outside services. The platform owns the developer workflow, while partners keep owning their specialized backend category.
The next phase is deeper bundling without backend lock in. Front-end clouds will keep becoming the default control plane where developers discover, connect, and manage databases and APIs. The companies that win will make partner services feel native in the workflow, while preserving the freedom to swap them out as an app grows.