Scayle vs Alokai vs Frntkey

Why this comparison exists

Scayle, Alokai, and Frntkey show up on the same shortlists when a European or Nordic merchant evaluates a modern storefront. They appear side by side in RFPs, on evaluation matrices, and in analyst notes. The names are treated as roughly interchangeable options in the headless commerce space.

In practice they answer three different questions and belong in three different product categories. Comparing them like-for-like without noticing that is how bad platform decisions get made. This piece sorts out what each product actually is, what each is good at, and which shortlist question each one is designed to answer.

They are not the same category

The first honest observation is that these three are not competitors in the strict sense.

Scayle is a commerce platform. It ships a Vue-based storefront on top of its own commerce engine. Adopting Scayle means replatforming the backend as well as the frontend.

Alokai is a headless frontend framework. It is the rebranded product formerly known as Vue Storefront. Alokai does not ship a commerce engine. It sits in front of one the merchant already has (commercetools, SAP Commerce Cloud, BigCommerce, Shopify, others) and provides the frontend and an orchestration layer.

Frntkey is a productized headless frontend. Like Alokai, it does not ship a commerce engine. It sits in front of Norce, Shopware, Shopify, or Magento, and delivers a working storefront with Nordic integrations pre-built.

This distinction runs through every dimension of the evaluation. It is worth naming clearly before going further.

Scayle: full-stack commerce platform

Scayle originated inside About You, the Hamburg-based fashion retailer, and now sells as a standalone commerce platform. It ships a Vue-based frontend on top of its own commerce engine. Buyers get both layers from one vendor. The two are tightly integrated because they were built together.

The honest strengths of Scayle:

• Mature at brand and enterprise scale. About You itself runs on Scayle. The platform has been through real load and real complexity.
• Consistent DACH presence. Scayle is headquartered in Hamburg and is well known in the German-speaking fashion and lifestyle space.
• Unified frontend and backend experience. Because one vendor owns both layers, the seams between them are less visible than in a mixed stack.
• Strong content authority in German. Scayle runs one of the more capable glossary engines in the DE headless space.

The honest tradeoffs:

• Adopting Scayle means committing to Scayle's commerce engine, not just Scayle's frontend. Merchants with significant investment in another commerce platform are looking at a full replatforming, not a frontend swap.
• Third-party integrations bound to the current commerce engine need to be re-implemented against Scayle's backend. The scope is usually larger than the frontend evaluation suggests.
• Scayle is heavier for merchants outside the DACH consumer brand profile. It is a strong product; it is not the right product for a Norce-anchored Nordic merchant who wants only a new frontend.

Alokai: headless frontend framework

Alokai is the rebranded product formerly known as Vue Storefront. The rebrand landed in 2024. The product has continuous history back to the open-source Vue Storefront project from around 2017. Alokai is a frontend framework, not a commerce platform. It supports multiple commerce backends through an orchestration layer they call Middleware.

The honest strengths:

• Multi-backend flexibility. Alokai works with commercetools, SAP Commerce Cloud, BigCommerce, Shopify, and others. Merchants running enterprise backends have real optionality.
• Large ecosystem. The open-source heritage means an active community, extensive documentation, and a substantial pool of developers who know the framework.
• Enterprise deployments. Alokai has real production customers at the Fortune 500 scale. SAP CX integration is a specific focus area.
• Global reach. The team is Poland-based with a global customer base. Not narrowly regional.

The honest tradeoffs:

• Alokai is more framework than product. You build your storefront using their libraries, boilerplates, and Middleware. You do not adopt a working storefront out of the box.
• Implementation timelines are closer to a custom build than to a packaged product. This is fine for enterprises with a dedicated frontend team. It is a poor fit for merchants who want a fast launch.
• The Nordic integration set (Klarna, Kustom, Svea, Walley, Voyado, Lipscore) is not pre-built. Everything gets integrated as part of the project.
• Norce is not on Alokai's list of supported backends. Merchants anchored to Norce would need custom integration work.

Frntkey: productized headless frontend

Frntkey is built by Nordic Web Team. It is a Nuxt.js frontend product that connects to Norce (native), Shopware (via Store API), Shopify (via Storefront API), and Magento (via GraphQL). It is a working storefront out of the box, licensed as a monthly SaaS subscription, with pre-built integrations for the Nordic commerce stack.

The honest strengths:

• Norce official partnership. Norce recommends Frntkey as the frontend for its Jetshop migration program. For merchants on Norce (or moving to Norce from Jetshop), this is a paved path.
• Pre-built Nordic integrations. Klarna, Kustom, Svea, Walley, Voyado, Lipscore, and Hello Retail all ship with the product. Nothing to re-implement.
• Packaged product model. Frntkey is a working storefront on day one. Design customization and integration wiring happen on top of a live baseline rather than starting from a blank framework.
• Faster launches. Most Frntkey storefronts go live in 6 to 12 weeks. A custom headless build typically takes 4 to 9 months for the same scope.
• Storyblok bundled as the CMS. The content layer is not a separate integration; it ships with the product.

The honest tradeoffs:

• Smaller ecosystem than Alokai. Fewer community contributions, fewer independent developers who have worked with Frntkey specifically.
• Tighter geographic and backend focus. Nordic and DACH markets, Norce and Shopware primarily, with Shopify and Magento supported. Not a fit for merchants who need SAP CX or a highly enterprise-specific stack.
• Less battle-tested at Fortune 500 scale. Frntkey serves mid-market and enterprise-adjacent merchants in the Nordics. The Alokai team has more references at the very top of the market.
• Packaged means opinionated. Merchants who want to build the storefront substantially custom get less value from the packaging than merchants who want to launch a working storefront quickly.

Side-by-side dimensions

When to pick Scayle

Scayle is the right call when:

• You are replatforming end to end and want one vendor accountable for both frontend and backend.
• You are a DACH consumer brand, particularly in fashion or lifestyle, where Scayle's positioning aligns with your buyer.
• You value having the vendor own the full commerce experience, not just one layer.
• You do not have significant sunk cost in another commerce engine that you want to preserve.

Scayle is a poor fit when the backend commitment is unwelcome, when your integration set is bound to a different commerce engine, or when your market is outside the DACH consumer brand corridor.

When to pick Alokai

Alokai is the right call when:

• You are an enterprise with an in-house frontend team and engineering capacity to sustain a framework-based build.
• Your commerce backend is SAP Commerce Cloud, commercetools, or another platform on Alokai's supported list.
• The storefront is a strategic competitive differentiator worth building substantially custom.
• You benefit from Alokai's community, ecosystem, and open-source heritage.

Alokai is a poor fit when time-to-launch is the dominant constraint, when the team is not prepared to operate a custom frontend at framework scale, or when the commerce backend is Norce.

When to pick Frntkey

Frntkey is the right call when:

• Your commerce backend is Norce or Shopware, or you are moving to one of them.
• You want a working storefront in weeks, not quarters.
• Your customer base is in the Nordic market and the pre-built integrations (Klarna, Kustom, Svea, Walley, Voyado, Lipscore) map to your existing stack.
• You value packaging and time-to-launch over deep frontend customization.
• You want Storyblok as the CMS without a separate integration project.

Frntkey is a poor fit when the storefront needs to be built substantially custom, when the commerce backend is enterprise-specific (SAP CX, complex commercetools), or when the geographic focus is outside the Nordic and DACH markets.

The honest summary

Three products, three different questions. If you are picking between Scayle, Alokai, and Frntkey, the first useful thing to figure out is which question you are actually answering.

Are you replatforming end to end and looking for one vendor to own the whole stack? That is a Scayle question. Are you building a custom frontend as strategic investment on an enterprise commerce backend you are keeping? That is an Alokai question. Are you launching a fast headless storefront on Norce or Shopware, with Nordic integrations you need working on day one? That is a Frntkey question.

The three products do not compete for the same buyer. They compete for buyers who have not yet sorted their own decision into one of those three shapes. Once the shape is clear, the choice usually is too.

For the head-to-head deep dives, see Frntkey vs Scayle and Frntkey vs Alokai. Or read the frontend-as-a-service pillar to understand the packaged category that Frntkey belongs to.