Glossary
Frontend-as-a-service (FaaS)
Frontend-as-a-service is a productized delivery model for headless commerce storefronts. The merchant licenses a pre-built storefront instead of building one from scratch.
Frontend-as-a-service productizes the storefront layer of a headless commerce project. The merchant gets a pre-built, maintained storefront on subscription. The provider handles the underlying codebase. Most FaaS projects launch in 6 to 12 weeks rather than the 4 to 9 months a custom headless build typically takes.
Frontend-as-a-service (FaaS) is a productized delivery model for the storefront layer of a headless commerce project. Instead of building a custom storefront from scratch, the merchant licenses a pre-built, production-ready frontend and customizes it for their brand. The provider maintains the underlying codebase as a product.
A FaaS product ships the pages every ecommerce site needs — home, category, product detail, cart, checkout, search, account — along with a CMS, pre-wired integrations for payment, shipping, search, and CRM, and the server-side rendering and structured data needed for SEO. The merchant pays a subscription for the license and runs a fixed-scope setup project to connect the backend, apply branding, and go live.
## How FaaS differs from other delivery models
FaaS sits between a platform theme and a fully custom headless build. A theme is constrained by what the commerce platform's frontend engine allows. A fully custom build gives complete freedom but requires a team to build and maintain the storefront from scratch. FaaS reduces build time and shifts long-term maintenance to the provider, at the cost of working within a productized frontend's constraints.
A typical fully custom headless build takes 4 to 9 months. A FaaS project typically launches in 6 to 12 weeks because the storefront, backend-for-frontend (BFF) layer, and most integrations are already in place.
## What FaaS is not
FaaS is not a website builder. The storefront is a production-grade software application built in a JavaScript framework like Nuxt or Next.js. Developers configure and extend it. Editors manage content through the CMS.
FaaS is not a commerce platform. It does not own products, pricing, inventory, or orders. Those stay in the commerce backend — Norce, Shopware, Shopify, Magento, or another API-first engine. FaaS is the frontend that connects to the backend.
## How Frntkey relates
Frntkey is a frontend-as-a-service for Norce Commerce and Shopware. The storefront is built on Nuxt.js, Vue.js, and Tailwind CSS. Storyblok ships bundled as the CMS. Hosting runs on Vercel. The full integration set — Klarna, Walley, Voyado, Hello Retail, Lipscore, Ingrid — is pre-wired and ready to activate per project.
For the long-form explanation of the FaaS model, see the frontend-as-a-service pillar post.
## Related terms
Headless architecture · Headless commerce · Composable commerce · Ecommerce frontend
Frequently asked questions
Ready to talk?
See how Frntkey fits your stack. Book a 30-minute demo.
Book a demo