Monolith vs headless

A monolith is a commerce platform where the storefront and the backend live in the same codebase, ship in the same release, and run on the same servers. Shopify Liquid themes are monoliths. Magento with a default frontend is a monolith. Jetshop is a monolith. The frontend is the platform's frontend, customised to the merchant's brand. A headless setup separates the two. The commerce backend exposes APIs. A separate frontend application consumes them and renders the storefront. The frontend can run on different infrastructure, in a different language, on a different release cycle than the backend. Norce sells the backend only. Shopware can run headless. Frntkey is the headless frontend layer. The trade-offs are real in both directions. ## Where monoliths win Monoliths win on time-to-launch for simple stores. The theme is already there. Pick one, swap the brand, hit publish. For a small D2C merchant with standard requirements, a monolithic platform is faster to ship and cheaper to operate than any headless setup. Monoliths lose on customisation depth. The frontend can only change as far as the theme system allows. New page types, custom checkout flows, unusual product configurators all hit the theme's ceiling sooner or later. The escape hatch is forking the theme or paying the platform vendor to extend it. Both are expensive. ## Where headless wins Headless wins on flexibility and speed of change. The frontend team ships independently of the backend team. New page types are a frontend code change, not a platform configuration. Performance optimisation is a frontend concern, not a platform constraint. Multi-market rollout is a frontend pattern, not a platform fork. Headless loses on initial complexity. More moving parts. More integrations. More monitoring. The team needs to be comfortable with frontend engineering as a discipline, not as a theming exercise. The hosting bill, the build pipeline, and the deployment process all become things to maintain. ## The middle ground The middle ground is a productised headless frontend. Frntkey, Alokai, Vue Storefront. The frontend is decoupled from the backend (headless benefits) but comes with the storefront, components, and integrations already built (monolith-style time-to-launch). The trade-off shifts: instead of monolith-vs-headless, the question becomes packaged-vs-custom. ## A real decision framework If your storefront does standard ecommerce on a single market, with brand-level customisation but no fundamentally unusual product or checkout requirements, a monolith is usually the cheapest answer. If your storefront does B2B, multi-market, complex catalogues, or needs to ship features faster than your monolith's release cycle allows, headless wins. If you want headless benefits without paying for a full custom frontend build, a packaged headless frontend like Frntkey targets that exact gap. Norce's CPO has said publicly that Frntkey has become a popular choice for merchants who prioritise fast time to market and low total cost of ownership. That phrasing tracks the packaged-headless positioning: closer to monolith on launch speed, closer to custom-headless on flexibility, between them on cost.