Building on Magento in 2026: three architectures for three stages of growth

Introduction

There is no single Magento architecture that fits every business. The right choice depends on what you need today and how much flexibility you will need as you grow. In 2026, the options range from a lean Magento and Hyvä setup to a headless platform or a fully managed Adobe service, each with different trade-offs in cost, control and complexity.

This guide compares three Magento-based architectures for three stages of growth: Magento with Hyvä, headless Magento, and Adobe Commerce with Edge Delivery Services. We look at what each enables, what it takes to run, and how three-year total cost of ownership shapes the decision.

Most platforms don't break on day one. They break when growth arrives: a second country, a mobile app, a B2B customer base with its own price lists. If the architecture didn't plan for that, every new step becomes a workaround, and workarounds add up. Getting the foundations right at the start is the cheapest decision you will make.

The good news: building on Magento has never offered more ways to get it right. In November 2025, Hyvä Theme became free and open source. Adobe now runs Adobe Commerce as a Cloud Service, with a storefront delivered on Edge Delivery Services. And since 2.4.9, Magento ships one major release every May, each supported for three years.

Same foundations. Every tier.

The storefront is what people see. What decides whether a platform survives production is underneath it. These principles do not change between tiers; only the tools that deliver them do.

• Back-office systems never slow the store. ERP, PIM and CRM connect through a dedicated, asynchronous integration layer. A slow or offline ERP does not stop customers from buying.
• No order gets lost. Queues, automatic retries and scheduled reconciliation catch problems before your customer service does.
• The business owns pricing and merchandising. Price lists, promotions and product ranking are managed without developer tickets, with a full audit trail.
• Many markets, one platform. Local prices, assortments and content run on shared infrastructure, with SEO kept under control.
• Everything is observable. Business and technical dashboards show stuck orders, failed syncs and slow pages. Alerts fire before the phone rings.
• Peak traffic is rehearsed, not hoped for. Integrations are tested automatically, and load tests run at several times today's traffic.

Because the foundations are shared, moving from one tier to the next does not mean rewriting your integrations. You change the layer that needs to change.

Tier 1: Magento + Hyvä

Fast to market, built to last. Best for small to mid-sized businesses with one main sales channel, one or a few markets, and a clear need for speed and a predictable budget.

The architecture

Magento Open Source or Adobe Commerce runs as a well-structured modular monolith. Hyvä Theme replaces the legacy Luma front end. Hyvä Checkout goes in from day one. Integrations with ERP and other systems run asynchronously, outside the core of the store, never as fragile scheduled scripts inside it.

What you get

• The shortest time to market of the three tiers.
• One codebase and one team to run it.
• Strong Core Web Vitals without a separate front-end application.
• A mature ecosystem of Hyvä-compatible extensions.

What to plan for

The core theme is free, but Hyvä Checkout is a commercial licence, as is Adobe Commerce if you choose it. Front end and back end are coupled, so adding a mobile app or a partner portal later is a bigger project. Advanced B2B features on Magento Open Source need extensions.

Time to move up when a second channel appears, or when the storefront starts limiting how fast the business can change.

Tier 2: Headless Magento

One engine, any front end. Best for mid-sized to large businesses selling through several channels and markets, often with complex B2B, that want to own their platform and stay free to change the front end.

The architecture

Magento stays the commerce engine and the back office, exposed through its APIs. Between Magento and the customer sits a dedicated API layer, often called a Backend for Frontend (BFF). It combines commerce data, content and search into one ready-to-use response for each channel, and decides what can be cached.

The storefront is built in any modern front-end technology, rendered on the server and cached at the edge. Marketing content lives in a headless CMS. An event-driven integration layer connects ERP, payments, e-mail and marketing tools. Infrastructure is defined as code and deployed automatically.

What you get

• New channels without re-platforming.
• Full ownership of the code and low vendor lock-in.
• Caching tuned per market and customer segment, so pages stay fast as the catalogue grows.
• Independent release cycles for marketing, commerce and front-end teams.

What to plan for

More moving parts mean a higher upfront investment and a more mature team, in-house or with a partner, including solid DevOps. In return, every next channel costs a fraction of the first.

Tier 3: Adobe Commerce + Edge Delivery Services

Enterprise as a service. Best for large organisations that prefer buying a managed service to running infrastructure, and that already use or plan to use Adobe Experience Cloud.

The architecture

Adobe Commerce as a Cloud Service runs the commerce engine, with infrastructure, scaling and updates handled by Adobe. The storefront is Adobe's Commerce Storefront on Edge Delivery Services, assembled from ready-made drop-in components, now including B2B ones such as company management and requisition lists. Business users author content in familiar documents or in a visual editor.

Customisations and integrations live outside the core, in Adobe App Builder, with API Mesh combining several APIs into one endpoint. The same integration principles apply: the ERP is connected asynchronously, through events.

What you get

• Very fast pages without building a front end from scratch.
• No upgrade projects, because the platform updates itself.
• Native integration with Adobe Experience Platform for data and personalisation.
• Content changes made by marketing, not by developers.

What to plan for

Licence cost is the highest of the three tiers, and so is dependence on a single vendor. The core cannot be modified; every customisation is an out-of-process extension. Some familiar Magento features are replaced by Adobe services in the cloud-service edition, so each one needs checking during migration.

If a fully managed SaaS is a step too far, Edge Delivery Services also works with Adobe Commerce on Cloud infrastructure, the platform-as-a-service edition.

Choosing your tier

No tier is better in general; each is cheaper for a different business. Total cost of ownership (TCO) decides more than the launch budget, so look at the full three-year picture.

The pattern is simple. Tier 1 wins while you stay on one channel. Tier 2 pays back as channels multiply. Tier 3 trades licence cost for lower operational effort and the fastest path to Adobe's personalisation tools.

Where to start

Start with the riskiest flow, not the homepage. For most businesses that is an order travelling from checkout to the ERP and back, with payment in between. Prove it works under load and under failure, and the rest of the platform has a solid core. Then ask where the business wants to go in the next few years.

Our engagements begin with a short discovery of your needs and a proof of concept of exactly that flow. It tells you a lot about the platform requirements: which tier fits, what it will cost to own, and where the risks sit, before you commit to a full build. And because the foundations are shared, starting with Tier 1 never locks you out of Tier 2 later.