Frontend as a Service: The Missing Piece of the Composable Web

By Philipp Marxen | August 23, 2025

For the last decade, we have been obsessed with the "Headless" revolution. We decapitated the monoliths. We moved our content to Strapi and Sanity. We moved our commerce to Shopify and BigCommerce.

But we left one question unanswered: Where does the head actually go?

Enter Frontend as a Service (FaaS).

Strictly speaking, FaaS is a cloud-based solution that provides the infrastructure, workflows, and often the visual interface to build and deploy the "head" of your website. It is the orchestration layer that glues your APIs together and serves them to the user.

It is no longer just "hosting." It is an entire ecosystem of Image Optimization, Edge Middleware, and Visual Building.

The 2025 FaaS Leaderboard

The market has matured. We have seen giants rise and early pioneers fall. Here is the snapshot of the landscape in late 2025.

1. Webstudio (The Visual FaaS)

• Projects: 150k+

• Growth: >1000% (2024), >300% (2025)

• The Pitch: "Webflow for the open stack."

• Why it's winning: Webstudio is unique because it bridges the gap. It is a visual builder (like Webflow) but it deploys standard React/Remix code to the edge. It is the only FaaS that doesn't require you to be a hardcore React developer to use effectively.

2. Vercel (The Developer Standard)

• Projects: >4m websites

• Growth: Strong, steady enterprise adoption.

• The Pitch: "Develop. Preview. Ship."

• Why it's winning: Vercel owns the standard (Next.js). If you are coding by hand, you are likely deploying here. Their "v0" AI tools have kept them competitive, but they remain a code-first platform.

3. Netlify (The Composable Hub)

• Projects: >700k active sites

• Traffic: 700m unique visitors/month.

• The Pitch: "Connect everything."

• Why it's winning: Netlify has pivoted to become the integration glue. Their "Netlify Connect" data layer unifies content from different sources, making them the Switzerland of the FaaS war.

4. The Niche & The Fallen

• Instant Commerce: Growing rapidly in the Shopify ecosystem by offering a "Headless PWA in a box" for e-commerce brands.

• Shogun Frontend: Deceased. Shogun bet early on a dedicated headless frontend product but shut it down to focus on their core Page Builder.

  • The Lesson: Shogun Frontend failed because it was too expensive (~$2k/mo start) and too closed. The market wanted Open Source and Flexible Pricing—the exact gap Webstudio filled.

The Architecture of FaaS

To understand the value, you have to look at the architecture.

1. The Backend (BaaS): This is your source of truth. It holds the data. (e.g., Baserow for data, Shopify for products, Strapi for blog posts).

2. The API Layer: The "glue" that fetches data.

3. The Frontend (FaaS): This is where Webstudio or Vercel lives. It takes the raw JSON data and renders it into HTML/CSS/JS.

Why Move to FaaS? (The Advantages)

1. Decoupling Teams

In a monolithic setup (like WordPress), if the backend developer updates the database, the frontend might break. In a FaaS setup, the two are separated by an API contract.

• Marketing Team: Can iterate on the design in Webstudio daily.

• Dev Team: Can refactor the database without ever touching the visual layer.

2. Performance by Default

FaaS providers compete on speed. Features that used to require a DevOps engineer are now standard:

• Edge Caching: Your site is replicated on servers globally (London, Tokyo, New York).

• Image Optimization: Upload a 5MB PNG, and the FaaS automatically serves a 30KB AVIF file to the user.

3. Component-Driven Design

FaaS tools force you to think in Components, not pages. You build a "Product Card" once. You connect it to your database. Then you reuse that card on the Homepage, the Category Page, and the Search Results. If you change the design of the card, it updates everywhere instantly.

The Collateral Damage: Is Figma Dead?

This shift has a massive side effect: The irrelevance of static design tools.

In 2023, the workflow was: Figma (Design) -> Developer (Translate to Code) -> FaaS (Deploy)

In 2025, with tools like Webstudio, the workflow is: Webstudio (Design & Build) -> FaaS (Publish)

Why would you spend 100 hours drawing a "Fake" interface in Figma when you can spend those same 100 hours building the real interface in Webstudio?

• Figma is retreating to become a prototyping and ideation tool.

• The "Hand-off" is disappearing.

Conclusion

Frontend as a Service is not just a hosting upgrade. It is a workflow revolution.

It allows us to build websites that are Dynamic (connected to real databases), Performant (running on the edge), and Maintainable (component-based).

For the Webstudiosi community, we are sitting in the driver's seat. We have the only tool that combines the visual ease of the old world with the FaaS power of the new world.