You've built a strong Magento. Give it a front-end that keeps up.
Headless commerce development for Magento 2
A fast storefront on its own server, connected to your Magento. Black Friday, bots and ad campaigns hit the storefront, not your Magento. Your catalogue, integrations and customer prices keep working as they are.
- Works with any Magento 2.x
- Open-source stack
- Switch back to Magento in minutes
What you get
- A calmer Black Friday: sale and ad peaks land on the storefront, not on Magento
- Bots crawl without slowing down checkout
- Design and content changes without touching Magento
- Any Magento 2.x, no upgrade first
Why Magento slows down
One queue for everyone
In Magento, everything shares one server and one database: shoppers browsing the catalogue, search bots crawling it, traffic from your ads, site search and product reindexing. When they hit at once, they all wait in the same queue, and the shopper about to pay waits with them. There's no way to send them to separate places, because Magento works as one system.
What headless changes
Browsing, filters and search move to a separate storefront on its own server. Bots and ad traffic land there. Magento handles only the cart, checkout and admin, so the shopper's order no longer waits behind a crawler.
If Magento slows down or goes offline for a while, shoppers can still browse. The cart and checkout need Magento back.
Sounds familiar?
- The store slows down when search engines crawl it, at least once a month
- Ad campaigns bring traffic, and the store gets slower right when it matters
- Product imports and reindexing slow down the storefront
- A hiccup at the host or in the search engine slows the whole store
- With several stores on one Magento, one store's peak slows the others
- Shoppers
- Search bots
- Ad traffic
- Site search
- Reindexing
one queue
- Shoppers
- Search bots
- Ad traffic

Storefront server
catalogue · filters · search
- sync, usually 2–5 min · add to cart, checkout
cart · checkout · admin
Before you decide
What changes, and what doesn't
Changes
- Catalogue, filters and search run on their own server, not on Magento
- Bots and ad traffic land on the storefront, not on Magento
- One store's peak no longer slows down the others
- Images are optimised automatically
- reCAPTCHA loads only on forms (reviews, newsletter, account), not on every page
- Content and design changes don't touch Magento
- The blog moves to a headless CMS, managed via API
Stays the same
- Checkout and admin, on Magento
- Prices and stock, always from Magento
- Customer group prices: each logged-in group sees its own price
- Back-end integrations: ERP, email, payments
- Your Magento version, no upgrade first
- Every URL, including custom navigation modules
- SEO data: texts, structured data and meta
What we rebuild on the new storefront
Anything your modules show on the page: reviews, banners, labels, related products, chat and email widgets, tracking pixels. We go through it with a checklist, so nothing goes missing.
What headless doesn't fix
Third-party scripts such as chat widgets and email pop-ups weigh the same on any front-end. We review them with you, and some can go before headless.
What gets added to your stack
It looks like a lot, but it isn't rocket science. Every part is a well-known open-source tool, and we set it up, monitor it and keep it running as part of your support retainer. You don't have to manage any of it.
- Nuxt
- OpenSearch
- Meilisearch
- Redis
- RabbitMQ
- Strapi
- Sync module
- Cloudflare
What each part does, for your developers
| Added | What it does |
|---|---|
| Storefront (Nuxt, Node.js) | Renders your pages |
| OpenSearch | Catalogue and filters |
| Meilisearch | Site search. If it's down, search falls back to OpenSearch |
| RabbitMQ | Passes every change from Magento to the storefront |
| Redis | Caches content and queues image optimisation |
| Strapi | Blog and content pages |
| Sync module in Magento | Picks up changes from the admin, imports or your own sync. Usually live in 2–5 minutes |
| Cloudflare | Caching, protection and switching back to Magento |
Example setup
4 stores, about 38,000 products. One dedicated server: 8 cores, 64 GB RAM, NVMe. About $115/month, plus Cloudflare Pro from $20/month. Your setup depends on your catalogue and traffic, and we size it before we start.
Live demo
See it working on Magento
A headless storefront connected to a real Magento 2 catalogue. Open a category, try the filters, search for a product, and see how fast the page responds.
Catalogue
- Simple and configurable products, with swatches
- Filters and sorting
- Site search
- Auto categories by rules
- Related products and menu
Merchandising
- Product labels by rules
- Custom stock statuses: only X left, pre-order
- Notify me when back in stock
- Banners, CMS pages and product widgets such as Best Sellers
Customers
- Customer account, with the same basics as in Magento
- Customer group pricing for B2B
- Reviews
- Newsletter signup
- reCAPTCHA Enterprise
Tier prices, quick order and quote requests aren't part of the storefront yet.
Before you decide
Questions to ask before going headless
Will we get 100 in PageSpeed?
We don't promise a score. Third-party scripts such as chat and email pop-ups still count against it. What we do: measure the same pages before and after, on mobile and desktop, so you see the difference on your own store.
Do we have to upgrade Magento first?
No. The storefront works with any Magento 2.x through the API. Magento 1 isn't supported yet. If you're on Magento 1, start with an upgrade to Magento 2.
What if a product sells out before the storefront updates?
It can't be ordered. Adding to the cart goes through Magento, so an out-of-stock product can't be added, and the price always comes from Magento. Your current front-end caches prices the same way. The difference: no more manual cache flushes to see your changes.
Will we lose our search rankings?
Every URL stays the same, including the ones from custom navigation modules. Texts, structured data and meta move with them.
What if it doesn't work for us?
We start with one store. If something goes wrong, we switch it back to Magento in Cloudflare within minutes, with no downtime. Shoppers browsing at that moment usually don't notice: the next page simply opens from Magento, and their cart is still there.
How will we know it worked?
Before we start, we agree on the pages and metrics. After launch, we measure the same pages the same way. The decision on the rest of your stores comes after that.
Is headless right for every Magento store?
No. If your store is stable and only the theme feels heavy, optimisation or Hyvä may be enough. Compare the options
Your options
Headless or fix what you have?
Headless isn't the only way to a faster store. Here's how the three options compare.
| Criterion | Optimise your theme | Hyvä theme | Headless storefront |
|---|---|---|---|
| Fixes | Quick wins: caching, images, scripts | Page speed | Page speed, plus slowdowns from bots, ads and reindexing |
| Front-end still runs on Magento | Yes | Yes | No. Catalogue, filters and search run separately |
| Your Magento version | Any | Current releases need 2.4.4-p9+ and PHP 8.1+. Older stores upgrade first, or use an older Hyvä release, where compatible modules may be missing | Any Magento 2.x, via API |
| Modules that show something on the page | Stay as they are | Need Hyvä-compatible versions | Rebuilt on the storefront, once |
| Magento upgrades | Theme checked every time | Theme and compatibility modules checked | Back end and our sync module only |
| Extra server | No | No | Yes. See the example setup above |
| Fits when | The store is mostly fine | The front-end is slow, but load isn't the problem | The store slows down or goes down under traffic |
Every option comes with trade-offs, and some only show up once the work starts. The audit is there to find as many as possible before you choose.
Not sure which one you need?
A performance audit shows what slows your store down and what it takes to fix it. Up to 3 days, $560.
An honest comparison
Or move to Shopify?
| Criterion | ||
|---|---|---|
| Several stores | Several brands on one Magento: one catalogue, one admin, shared customers | Each store is separate. Plus includes up to 9 expansion stores |
| Complex catalogue and B2B | Customer group prices and your custom logic stay | B2B on every plan, with more on Plus. Custom logic through apps |
| Speed | You control every script on the storefront | Fast platform, but each app can add its own scripts to your pages |
| Checkout | Yours. Change any step | Customised through Shopify's checkout extensions, more on Plus |
| What you pay every month | Magento hosting, plus about $115 for the storefront server and Cloudflare Pro from $20 | Plan from $29 to $2,300+. Apps, each billed separately. An extra 0.2–2% fee if you pay through a provider other than Shopify Payments |
| Who you depend on | Your own code and server. You need a team that knows Magento | Shopify's rules, and every app vendor: their prices, updates and shutdowns |
| Servers | We run them for you | None. Shopify hosts everything |
| Fits when | Your catalogue is complex, you run several stores, and you've invested in custom logic | Your catalogue is simpler and you want no servers at all |
Shopify is a strong platform, and we build on it too. If it fits you better, we'll say so and help you move.
How it works
From your store to a faster storefront
01 Brief
Tell us about your store
Before we start
Magento version, how many stores, which modules show something on the page, and what slows down.
02 Demo
See it on a real catalogue
Before we start
We show you the live demo and walk you through it. Want to see your own products? We can load your catalogue too. Ask us about the terms.
03 Plan
Checklist and estimate
Before we start
What we rebuild, how URLs and SEO move, which pages and metrics we measure. A fixed estimate before any work starts.
04 Build
One store first
Usually 3–4 months
We build the storefront and switch one store over in Cloudflare. If anything goes wrong, it goes back to Magento in minutes.
05 Measure
Same pages, before and after
After launch
We compare the pages we agreed on. The rest of your stores follow when you're happy with the result.
06 Support
We keep it running
From $800/month
Monitoring, fixes and small changes, as part of your support retainer.
FAQ
Questions about headless for Magento
How is a headless project priced?
Every project is estimated individually. You get a plan, a timeline and a fixed estimate before any work starts. Paid in three steps: 20% to start, 30% at the midpoint, 50% when it works.
How long does it take?
Usually 3–4 months, depending on how complex your store is.
Can our team still manage banners and pages?
Yes. Banners, CMS pages and product widgets such as Best Sellers are managed in a content admin, without a developer. Products, prices and orders stay in Magento, as they are now.
Who owns the code?
You do. Everything runs on your server, and the licence is included in the project price. It covers your whole Magento installation, with all its stores. You can change the code however you like. The only thing you can't do is resell it.
Can agencies offer this to their clients?
Yes. We work under your brand: your email, your project tools. The server and the domain belong to you or your client.
Is headless right for your store? Let's discuss.
Tell us your Magento version, how many stores you run and what slows down. We'll walk you through the live demo and tell you honestly whether headless is worth it for you.
- Reply within one business day
- Live demo walkthrough
- No commitment
