Headless Magento keeps Magento as the engine and replaces the storefront with a separate frontend, built and maintained by our headless Magento development team.
Adobe Commerce gold partner
#1 Adobe Commerce partner worldwide
Hyvä Platinum Partner
40+ projects delivered
ISO certification
9001 & 27001
Most certified Hyvä agency worldwide
200+ Adobe Commerce Certifications
Award-winning agency
3× eCommerce excellence award
Going headless isn't a new platform. Magento keeps doing almost everything it does today, and only the part the shopper sees is rebuilt.
Products, pricing, promotions and customer-group rules
Orders, fulfilment and the admin your team already uses
Extension logic and every ERP or PIM integration
Checkout rules, taxes, shipping methods and payment providers
Extensions built on the theme get their frontend rebuilt
Page Builder content moves to the storefront or a CMS
Two systems to deploy, host and upgrade instead of one
The storefront becomes its own application, talking to Magento through its APIs
We build and run both halves, the storefront and Magento, as one project with one team.
Kristaps Rjabovs, Managing Director
A headless Magento store has layers, and most of the engineering decisions sit in how they're joined.
Catalog, cart, checkout and customers exposed through GraphQL and REST. GraphQL does most of the work.
Joins Magento with search, a CMS, reviews or an ERP, so the storefront makes one call instead of five.
Usually React or Vue, with the first page rendered on the server so shoppers and crawlers get full HTML.
Pages, assets and read-only responses cached on a CDN, where much of a headless store's speed comes from.
How we choose for a new build: the systems the storefront draws on, who maintains it, budget and your Magento edition.
Your own storefront in React or Vue on Magento's GraphQL API, with an API layer wherever other systems join in.
Adobe's decoupled storefront on Edge Delivery Services, with shopping components maintained by Adobe.
Not headless. A fast Magento theme that keeps the storefront inside Magento.
New decoupled builds no longer start on PWA Studio, but we keep maintaining and extending the PWA Studio stores already running.
Magento PWA developmentThe stores that get the most from a decoupled storefront usually share one of these needs.
A website, an app, kiosks or marketplaces, all fed by one catalog through the same APIs.
Magento, search, a CMS and an ERP combined, so every page reads live data.
Layouts and interactions designed freely, not limited by what a theme allows.
The storefront ships on its own schedule, without waiting for Magento releases.
Or you'd like us to run both halves for you, under one support agreement.
One Magento catalog serving your website, app, kiosks and marketplaces, without each channel keeping its own copy.
Rendered on the server and cached at the edge.
The same products, prices and accounts via one API.
Endless-aisle browsing and ordering from the full catalog.
Tills that read Magento's catalog and write sales back.
Product and stock published out, orders coming back in.
Adobe's SaaS edition was decoupled from the start, and Adobe Commerce Optimizer puts the same storefront layer in front of an existing backend.
Adobe's ready-made storefront components for cart, checkout and account.
Fast catalog reads served separately from the application.
Several data sources combined behind one endpoint.
Custom logic running outside the application.
We recommend the one that suits your licence.
What a decoupled storefront gives a store that a theme can't.
Any layout or interaction, not limited by a theme.
Server-rendered pages cached at the edge, close to every shopper.
Website, app, kiosk and marketplaces from the same data.
Search, a CMS or reviews plugged in at the API layer.
New channels and AI agents connect through the same APIs.
The storefront ships without waiting for Magento upgrades.
We estimate the running cost with the build, so you know what the store costs every year.
Codebases
Two, often changed together
One
Deployment pipelines
Two, each with its own releases
One
Hosting bills
Magento plus server-side rendering
Magento only
Magento upgrades
Tested against the storefront too
Tested in one system
Frontend framework upgrades
React or Vue kept current
Handled by the theme
New extensions with a frontend
Storefront side built as well
Work in the theme
Monitoring
Both systems and the API between
One system
All of it can run under one Magebit support agreement.
Decoupled storefronts running on one Magento backend.
Bob Toeppner
E-commerce Manager
There is no challenge for which they can't find a solution.
Will Aubuchon
CEO
Magebit feels like an extension of our own team. Whatever we need across the store, they handle it quickly and well, and the site keeps getting better.
Jad Haidamous
CEO
Within just two to three months, they resolved issues that previously seemed unresolvable.
Tim Johnson
CTO
Magebit brings Magento expertise to businesses in every country. From Perth, Melbourne and Sydney to London, Dubai, New York, Los Angeles, Charlotte and Florida, we’re ready to help wherever you are.
The top-ranked Adobe Commerce agency on the planet by Adobe themselves.
The most certified Hyvä agency in the world. Confirmed by Hyvä themselves, twice.
Explore Hyvä development
Innovator, World Traveler, and eCommerce Excellence awards across Meet Magento NYC and HIVE London, and more.
The most-certified Hyvä agency worldwide and the first Hyvä Platinum Partner in the USA. 55+ Hyvä certifications and 40+ projects delivered.
ISO 9001 & 27001 for quality and security.
Truly agile team that moves and adapts faster than your typical agency.
UX grounded in large-scale ecommerce research.
A headless store gives you one catalog for every channel and full control of the frontend. Tell me where you sell and who will run the store, and I'll show you the architecture we'd build and what it costs to build and run.
Reviewed by Kristaps Rjabovs
Co-founder of Magebit, Forbes 30 Under 30
If you can't find the answer you're looking for, feel free to reach out to us. We're here to help.
A Magento store whose storefront is a separate application, talking to Magento through its GraphQL and REST APIs. Magento still runs the catalog, checkout, orders and admin; only the shopper-facing layer is rebuilt.
When one catalog has to serve several channels, or the storefront combines Magento with other services, it pays off quickly. If the only goal is a faster web store, we'll also price a Hyvä option alongside it.
Yes, with a custom storefront on Magento's GraphQL API. Adobe Commerce Storefront is the exception: it needs Adobe Commerce and doesn't run on Open Source.
Their back-end logic keeps working inside Magento. Anything that adds to the storefront, such as widgets, product-page features or checkout steps, needs its frontend rebuilt against the API. We list those before quoting.
It can, as long as pages are produced server-side, so crawlers read finished HTML rather than waiting for JavaScript. A storefront that only builds pages in the browser can cost rankings, which is why every build we do renders on the server.
Not necessarily. Headless is the way the store is structured, and a PWA is one type of storefront that structure can support.
Yes. We audit the storefront, the API layer and Magento together, since problems often sit between them, then stabilise it or continue the roadmap.
Explore the Magento services Magebit has to offer.
Tell us where you sell and what the storefront has to do. You'll get a plan for your headless build, and what it costs to build and to run.
Where you sell today, and where you want to.
Headless, Adobe Commerce Storefront or Hyvä, free of charge.
A proposal with the build cost and the running cost.
We use cookies to understand visits, show relevant ads and play videos. You choose what to allow.
ProductDetails.jsx
PageSpeed Insights
2.4.8-p3 unchanged
