Frntkey vs Alokai: which fits the project?

What Alokai is

Alokai, formerly Vue Storefront, is an open-source headless commerce frontend framework built on Vue and Nuxt. It provides a starter storefront, a middleware layer, and integration adapters for several commerce platforms including commercetools, SAP Commerce Cloud, BigCommerce, Magento, Shopify, and others. Customers license the framework and platform tools, then build their storefront on top of it with their own team or a delivery partner.

Alokai is a real and capable framework. Companies running production storefronts on Alokai include household consumer brands across Europe and the US. The team behind it has been building headless commerce tooling longer than almost anyone else in the Vue ecosystem.

Frntkey vs Alokai: the core difference

The core difference is not technology. Both products are built on Vue and Nuxt. Both run on edge hosting. Both connect to commerce backends through API adapters. Both render server-side and target Core Web Vitals as a baseline.

The difference is delivery model.

Alokai is a framework. The merchant or their delivery partner builds the storefront on top of it. The framework is more open and more flexible than a productized FaaS. It also requires more implementation work, more in-house or partner engineering, and more ongoing maintenance after launch.

Frntkey is a frontend-as-a-service. The storefront is already built. The merchant licenses it, customizes the design and content, and connects it to their commerce backend. The setup project is scoped and fixed. The codebase is maintained by Frntkey. The integration set is pre-wired.

Both models work. They suit different teams, different budgets, and different project scopes.

Side-by-side comparison

When Alokai is the right choice

Alokai is the right choice when:

• The commerce backend is commercetools, SAP Commerce Cloud, or another platform Frntkey does not currently support. Alokai's adapter coverage is broader than Frntkey's.
• The storefront experience is so distinctive that a productized FaaS would have to be rebuilt anyway. A fully custom build on a framework gives more architectural freedom than a productized product.
• The merchant has in-house frontend engineering capacity, or works with a delivery partner that has deep Alokai experience, and wants the framework openness that comes with that.
• The project budget and timeline genuinely fit a 4-to-9-month custom build. For some merchants, that timeline is correct. For most mid-market merchants on Norce or Shopware, it is not.

When Frntkey is the right choice

Frntkey is the right choice when:

• The commerce backend is Norce or Shopware. The native integrations and the Norce Jetshop migration program make Frntkey the structured path for these backends.
• Time to market matters. 6 to 12 weeks for a production launch is meaningfully faster than the typical Alokai project timeline.
• The Nordic integration set (Klarna, Walley, Voyado, Hello Retail, Lipscore) is part of the requirements. Frntkey ships with these pre-wired.
• The team prefers a productized model over a framework. SaaS pricing, a maintained codebase, and a fixed-scope setup project remove the ongoing engineering overhead of a fully custom storefront.

The honest summary

Alokai is a strong open framework. Frntkey is a productized SaaS frontend. Neither is universally better. For merchants on commercetools or other Alokai-supported backends who have the engineering capacity for a custom build, Alokai is often the natural choice. For mid-market merchants on Norce or Shopware who want a fast launch with the Nordic integration set already in place, Frntkey is built for that exact case.

The decision should rest on the commerce backend, the team's engineering capacity, and the project timeline. Both products run on the same underlying technology.