Technology

Frontend

Nuxt.js with Vue 3 and Tailwind CSS. Server-rendered for SEO and initial load, hydrated for interactivity. The component library is shared across every Frntkey deployment, with backend-specific adapters layered on top.

Backends

Frntkey currently runs on Norce and Shopware. Each backend is its own Frntkey version. The frontend core is shared. The integration layer is tailored to the backend you run. Frntkey is not a one-size-fits-all storefront, it is a maintained set of versions, one per supported backend.

More backends are on the roadmap. Exact list and timing are not committed yet.

Content

Storyblok ships bundled. Marketing pages, navigation, footer, and SEO metadata live in Storyblok. The Frntkey component library is registered as Storyblok bloks so editors author with the same primitives the storefront renders.

Hosting and delivery

Frntkey is deployed on Vercel. Server-side rendering and ISR run on Vercel’s edge. Storyblok CDN serves images via the a.storyblok.com image-transform pipeline. Norce media is served from the Norce CDN.

Analytics and consent

Google Analytics 4 with Google Tag Manager is pre-installed. Cookiebot handles consent. Meta Pixel is pre-installed. Server-side GTM is available as an add-on.

Search

Frntkey AI Search is available as an add-on. Hello Retail or another external search provider can be plugged in when the customer already runs one.

Performance

Core Web Vitals are part of the contract. Frntkey storefronts are expected to ship with green LCP, INP, and CLS at launch. Performance is a property of the architecture, not a tuning pass at the end of the project.