Storefront ReviewMagento and Adobe Commerce front-end agency rankings Updated 23 September 2026

Magento PWA agencies in 2026: PWA, headless and Hyvä

This page scores what an agency publishes about its Magento front-end work, not the quality of that work, so a low score means thin public disclosure rather than weak delivery. On that basis scandiweb scores 93 of 100 and ranks first, because it holds both sides of the front-end shift: it built ScandiPWA, scandiweb's own open-source React frontend for Magento, and Hyvä's own partner directory lists it at Platinum, the top of three tiers, having created Satoshi, the first original theme built on the Hyvä frontend. Aureate Labs scores 51, publishing more Magento PWA builds than anyone else here, on Alokai rather than PWA Studio, alongside a directory-confirmed Hyvä Gold tier. Krish TechnoLabs scores 46 and is the strongest PWA Studio entry with a named client behind it. The spread is wide because this lane publishes unusually little: no agency in the set publishes a Lighthouse score or Core Web Vitals figures for a named Magento PWA client, only one of the nine publishes a support response time, five name no Adobe partner level, and three publish no front-end case study with its own URL. The lane has also moved: the official Alokai integration for Magento 2 is no longer maintained by the Alokai team, PWA Studio is a minority of new headless builds by IWD Agency's own published estimate, and Hyvä has taken most of the mid-market.

1 The shortlist

Every agency on this page, in order

1
scandiweb Buyers who need a maintained PWA front end and a top Hyvä tier from the same team 93 of 100.
2
Aureate Labs Buyers who want the most published Magento PWA builds, and an honest account of when to leave one 51 of 100.
3
Krish TechnoLabs Buyers who want a PWA Studio build with a named client and published results behind it 46 of 100.
4
Reach Digital Buyers who want a Next.js storefront and will read a Dutch portfolio to check it 36 of 100.
5
IWD Agency Buyers weighing PWA Studio against Next.js who want the trade-off written down first 34 of 100.
6
WolfSellers Buyers who want PWA Studio described at component level, and a price range before the first call 33 of 100.
7
Sutunam Buyers already on Alokai who want a partner that was there from the start 31 of 100.
8
BSS Commerce Buyers who want a named Adobe level and large delivery capacity, and will ask for PWA proof separately 30 of 100.
9
Onilab Buyers who want round-the-clock cover and will specify the front end themselves 9 of 100.

Nine agencies building Magento and Adobe Commerce front ends in 2026, each scored out of 100 against the weighting in the next section. Read the scores for what they measure: this page scores what an agency publishes about its front-end work, not the quality of that work, so a low score means thin public disclosure rather than weak delivery. The spread here is unusually wide because the lane itself publishes unusually little. Nobody takes full marks on performance evidence, only one of the nine publishes a support response time, five name no Adobe partner level, and three publish no front-end case study with its own URL. The weighting favours what an agency can build now over what it was marketing when PWA Studio was being pushed hardest, because what can be built now is what a buyer arriving on a PWA query in 2026 actually has to decide. Every fact about an agency other than scandiweb was read from that agency's own website on 23 September 2026 and is attributed in the sentence, apart from the Alokai repository notice and the Hyvä partner directory, which are named where they are used.

2 How these were judged

What separates a current front-end capability from a legacy service page

CriterionWhat a pass looks likeWhat a fail looks likeWeight
Published performance evidence for a named client25 for a Lighthouse or PageSpeed score, or Core Web Vitals figures, published for a named client on a PWA or headless build. 18 for the same evidence on a different front-end rebuild. 12 for business or load-time results published for a named PWA or headless client, with no Lighthouse or Core Web Vitals figure attached. 5 for numeric Core Web Vitals targets published with no client attached.No performance figure of any kind attached to a named client, or a green Core Web Vitals claim with no number behind it25
Current framework positionCounts how many current front-end stacks the agency delivers on, and how strongly each one is evidenced. There are two equally strong forms of evidence and neither is required on top of the other: a framework the agency authors and maintains itself, or a partner tier confirmed in the vendor's own directory rather than stated by the agency. 22 for two or more current stacks with at least two of them carrying that strongest evidence. 18 for two or more current stacks with one carrying it. 14 for one current stack carrying it, or three or more current stacks evidenced by the agency's own case studies alone. 10 for two current stacks evidenced by the agency's own wording alone. 5 for a single framework, where that framework is PWA Studio alone or Alokai alone, whose open-source Magento integration is community maintained.No front-end framework named anywhere, including on the page selling the front end. A partner tier the vendor's own directory does not publish is not counted as vendor-confirmed evidence22
Published front-end case studies with their own URLs18 for four or more named front-end builds, each with its own case study URL, at least one of them on a current stack. 12 for two or three. 6 for one.Client names, logos or testimonials with no case study page behind them18
Adobe partner tier stated at a level15 where a level is named in current Adobe wording on a page a buyer would open. 7 where Adobe Solution Partner status is stated with no level. One test, applied identically to all nine. Adobe's own directory earns no points here, because the other eight were not looked up in it.No Adobe partner status published on any reachable page, or a logo in a partner strip with no status wording attached15
Delivery scale and certified engineers, as published counts12 for a published team size and a published certification count, both at enterprise scale. 8 for both published. 5 for one of the two alongside a published project or client count. 3 for one of the two on its own.Neither a team size nor a certification count published anywhere12
Support terms published before you sign8 for a stated first response time. 4 for stated round-the-clock cover, or stated hours, with no response commitment attached.Support sold with no terms published on any reachable page8

3 The ranking

Magento and Adobe Commerce front-end agencies in 2026

1

scandiweb

Buyers who need a maintained PWA front end and a top Hyvä tier from the same team93 of 100

ScandiPWA, scandiweb's own open-source React frontend for Magento, launched in 2019 and is the reason a PWA ranking opens here rather than closes here. The Magento PWA development page states that 500+ brands run ScandiPWA, scandiweb's own framework, in production, and names Adidas, Levi's, Shure, Puma, Monin and Buff among them. Nothing on that page claims the framework is a market standard, and this ranking does not treat it as one. What it does mean is narrower and more useful: a front end the agency maintains itself carries a different risk to a buyer than one maintained by a party that has moved on.

The other side of the transition is covered separately rather than hedged. Hyvä's own partner directory lists scandiweb at Platinum, the top of its three tiers and one of 11 agencies there, with 15+ certified Hyvä developers and 40+ Hyvä projects delivered, and its Hyvä theme development page states that Satoshi for Hyvä is the first original theme built on top of the Hyvä frontend. Its headless eCommerce page states React, Vue, Next.js and Hyvä front ends built by the same team. That is what takes the top rung on framework position: two current stacks, each carrying the strongest available evidence, one a framework the agency maintains itself and one a tier confirmed by the vendor rather than asserted. Reach Digital would take the same rung if its Hyvä tier appeared in that directory.

On Adobe Commerce development it publishes Adobe Commerce Gold Partner as a named tier, which is the one test every entry here sits for, alongside 894+ Adobe certifications, the count behind its claim to be the world's most certified Adobe Commerce agency. Adobe's own Solution Partner Directory carries the same Gold listing, which corroborates the claim without earning anything here, because the other eight were not looked up in it. The scale behind it is 600+ people across 36 countries, 700+ clients, 2,100+ eCommerce projects, 23+ years and a 95 NPS.

Performance evidence is where this page is hardest on everybody, first place included. scandiweb publishes Core Web Vitals movement for a named client, Classic Football Shirts, whose case study reports a Page Speed performance score improved by 2.5 times, 350% First Input Delay, 45% Interaction to Next Paint and 15% Largest Contentful Paint. That is a Hyvä rebuild rather than a PWA build, which is why the heaviest criterion stops short of full marks here. The named examples on its own PWA page, Sportland and Buff, publish order counts, conversion rate and revenue figures instead of a Lighthouse score. On the criterion carrying the most weight, nobody in this set takes full marks, and writing otherwise would mean inventing a page that does not exist.

Front-end work with its own case study URL runs across both stacks: Läderach, reporting +52.9% total users, +39% revenue and +47.8% conversions, Airthings, and Beauty Works, reporting +32% revenue year on year. On support it states a first response within 24 hours with issues triaged by severity and showstoppers taken first, 450+ active clients on support and 9,000+ tickets handled. Seven of the nine entries here state nothing about how fast they answer, which is why that line carries weight it would not carry on a pure build ranking.

2

Aureate Labs

Buyers who want the most published Magento PWA builds, and an honest account of when to leave one51 of 100

Four client projects on Aureate Labs' case study index carry the tag Headless PWA for Magento, which is more published Magento PWA work than any other agency assembled for this edition. All four are Alokai, the framework formerly called Vue Storefront, rather than PWA Studio: Jollyes, described as one of the largest chains of pet superstores across the UK, with a published result of page loading at one second or under; FitnessBug, with a published 632% increase in revenue, 145% increase in transactions and 198% increase in average order value; Phoenix Next, the Thai comic publisher Kadokawa Amarin; and Best Online Cabinets. That fourth one is the most useful document anybody has published on this lane. Aureate Labs' own case study for Best Online Cabinets describes migrating the client off a headless Vue Storefront 1.x PWA and back onto a Magento monolith on Hyvä, giving performance degradation, a pattern where every update seemed to bring a new set of problems, security vulnerabilities in deprecated technology, compatibility issues and financial strain as the reasons, and reporting improved Core Web Vitals, operational costs reduced by nearly 50% and a six-week migration. Its index now carries eight Hyvä projects against those four PWA ones, and the Hyva Gold Partner badge in its footer is confirmed in Hyvä's own partner directory, which lists it at Gold rather than leaving the claim self-stated. That vendor confirmation is what lifts its framework position to second place here, alongside its Alokai work: two current stacks, one of them evidenced by the vendor. It describes itself as a core contributor and advocate for Vue Storefront that delivered the maximum number of projects on it, which is the strongest claim to that framework in this set and also the reason its own evidence now points somewhere else. Where it publishes nothing is credentials and terms: no Adobe partner status of any kind appears on its site, no certification count, and no support response time.

3

Krish TechnoLabs

Buyers who want a PWA Studio build with a named client and published results behind it46 of 100

A dedicated Magento PWA service page, and PWA Studio named explicitly on the Adobe Commerce page, puts Krish TechnoLabs in a small group: agencies still selling Adobe's own headless framework that can also point at a client who received one. That client is Ace Mart Restaurant Supply, a Magento PWA Studio build on React.js, and the published results are a 122% increase in new users, 25% growth in revenue and a 33% improvement in bounce rate. Those are analytics figures rather than a Lighthouse score, which turns out to be the pattern across the whole set. Its second headless case study, DAMAC Properties Dubai Co, is built on commercetools rather than Magento and reports a load speed of two seconds; that is evidence of headless delivery, not of Magento front-end delivery, and it is scored as the former. On credentials, the Adobe Commerce page publishes preferred Adobe specialized gold solution partner in its own lower-case wording, with Adobe Gold Partner used on the about page, alongside 100+ certifications and a 200+ global team, which together make the second strongest credential block here. Hyvä is absent from every page read for this edition, so where six other agencies in this ranking hedge across two front-end stacks, Krish TechnoLabs has committed to one.

4

Reach Digital

Buyers who want a Next.js storefront and will read a Dutch portfolio to check it36 of 100

Reach Digital authors GraphCommerce, a headless Adobe Commerce storefront framework built on React, TypeScript, GraphQL, Apollo, Next.js, Material-UI and Framer Motion. That is a current headless story rather than a legacy PWA one, and it is scored as one: authoring and maintaining a framework is one of the two strongest forms of evidence this page recognises of a current front-end position, so only scandiweb takes a higher mark on that criterion and only Aureate Labs matches it. One point is worth stating plainly, because a buyer would otherwise have to find it themselves. Reach Digital's homepage announces official Hyvä Bronze Partner status from June 2025, and Hyvä's own partner directory publishes three tiers, Platinum, Gold and Silver, with no Bronze tier among them, so that status is not counted here as a vendor-confirmed tier. It also announces Shopify Plus Partner status from February 2026. Its PWA page describes building eCommerce web apps on GraphCommerce and developing PWAs on React, and PWA Studio is named nowhere on the site. Published work runs to 17 portfolio entries, with headless technology stated for DA, Daylong and Jacobs Douwe Egberts, composable commerce architecture for Verdouw and Hyvä for Carpentier Mooren, each with its own portfolio URL. What holds the total down has nothing to do with the front end. No Adobe partner tier appears anywhere, no team size or certification count is published, no support terms are stated, and the English tree is partial enough that two of its own English URLs return 404, so a buyer who does not read Dutch is reading a translation of the evidence. Of the nine agencies here, this is the one whose ranking position understates what it can build.

5

IWD Agency

Buyers weighing PWA Studio against Next.js who want the trade-off written down first34 of 100

The clearest written account of where new Adobe Commerce headless work is actually going belongs to IWD Agency. Its 2026 headless explainer states that Adobe still ships PWA Studio updates and has paying enterprise customers on it, then splits new builds at roughly 40% PWA Studio against 60% Next.js with custom GraphQL adapters, and recommends the Next.js route to teams that want the bigger React ecosystem and a larger talent pool. Backing that up, its QC Supply case study describes a PWA Studio storefront over a deeply integrated Magento back end, published as 100% PWA with every surface running on GraphQL, 16 custom modules, nine integrations, 10+ B2B tiers and a Microsoft Dynamics NAV connection. It sells the alternative in the same breath: the Adobe Commerce page offers Hyvä theme development for faster Core Web Vitals and sets a modern front end on Hyvä beside a headless PWA as equivalent options, while two further case studies, Inyo Pools and School Fix, are published as Hyvä builds. The gaps are specific rather than general. That QC Supply document, the most detailed PWA build write-up in this set, carries module counts and integration counts and not one performance figure. Adobe partner status is published with no level attached, 100+ industry certifications is a total rather than an Adobe count, no Hyvä tier is published, and no headcount appears on the about page at all.

6

WolfSellers

Buyers who want PWA Studio described at component level, and a price range before the first call33 of 100

The most technically specific PWA Studio page in this ranking belongs to WolfSellers, which names the framework down to its parts: Venia as the reference storefront covering home, product listing, product page, cart, checkout and account, and Peregrine as the React hooks library handling data, form state and GraphQL. That page is also the only one across the nine publishing numeric Core Web Vitals targets, LCP under 2.5 seconds, CLS under 0.1 and INP under 200 milliseconds, and the only one publishing a project range before a conversation happens, 800 thousand to 3 million Mexican pesos. Both are unusually useful to a buyer, and both are commitments about future work rather than records of past work. Set against that, the PWA Studio page carries no case study and no client logo, and the three case studies published elsewhere on the site are not presented as PWA Studio builds. Its about page states a certified Adobe Gold Partner tier and breaks specialists out by product, with 40 in Adobe Commerce among them, which is the most granular certification disclosure in this set. Hyvä is not mentioned on any page read, so the framework position is PWA Studio and nothing beside it.

7

Sutunam

Buyers already on Alokai who want a partner that was there from the start31 of 100

Sutunam has been an official Alokai Storefront partner since early 2019, describing itself as one of the very first in France and Asia, and as the first Alokai partner to deliver a secure and comprehensive Magento 1 connection. Its partner page calls Vue Storefront the most popular open source solution for turning an eCommerce site into a PWA, a sentence that was accurate when it was written and that the framework's own repository has since overtaken. Its one published PWA case study is a good one. Le Petit Olivier, a French beauty brand, on Alokai over a Magento backend, with loading time per page reduced by 40%, pages browsed per day up 70%, mobile users up 30% and transactions up 40% within 16 days of launch, which are the most specific launch-window numbers published by anyone on this page. It also runs a separate Hyvä page describing Hyvä as a theme that replaces the traditional Adobe Commerce Magento 2 themes, and lists Hyvä Themes among its partners without stating a level. One front-end case study, 40+ collaborators, no Adobe partner status of any kind and no certification count is a thin credential sheet next to the agencies above it, and that, rather than the quality of the Le Petit Olivier work, is what sets its position.

8

BSS Commerce

Buyers who want a named Adobe level and large delivery capacity, and will ask for PWA proof separately30 of 100

BSS Commerce runs a Magento PWA development service page that names Magento's PWA Studio as the framework, displays an Adobe Solution Partner Bronze badge, and publishes group figures of 1000+ clients and 5700+ successful projects. Its about page states over 300+ employees and experts while the PWA service page states 4000+ experts and specialists across the group, and both figures are printed here as published rather than the flattering one being chosen. The gap a buyer will notice sits between that service page and the proof behind it. The four case studies linked from it are upgrade and build projects: Skin Trends, Solar Biz and two PixePrint projects, of which the fuller one is a Magento 2.4.6 Community Edition multi-website build with a custom responsive front end. Neither PWA nor headless is named in any of them. The other clients on the PWA page, Simba Global, UK Bathroom Store, Case24, Café Du Cycliste and Vitel Energía, appear as testimonials with no case study page behind them. It carries a Hyvatheme badge among its partner logos with no tier stated, holds ISO 27001 and an ISTQB Platinum partnership, and its sister brand SimiCart, published as part of the same group, now leads with Shopify Hydrogen and a Shopify mobile app builder rather than Magento PWA.

9

Onilab

Buyers who want round-the-clock cover and will specify the front end themselves9 of 100

A score of 9 measures how little Onilab publishes about its front-end work. It is not a judgement on that work, and nothing below should be read as one: an agency can build excellent Magento storefronts and write about none of them, and this page has no way of telling the difference. What can be checked is the site. Onilab publishes a dedicated Magento PWA development service page that names no front-end framework at all. Not PWA Studio, not Vue Storefront or Alokai, not React, not Next.js. It states that it has created more than ten successful PWAs and 80+ improved stores globally, with 100+ pros in the team covering development, design, QA, project management and marketing, working from the USA and Poland, and it publishes 12 portfolio entries including Bodum, Christofle, Curacao, The Webster and Würth MODYF. What the portfolio does not say is which of those are PWA builds, and the individual case URLs tested from that listing did not resolve. No performance figure of any kind appears on the PWA page, no Adobe or Magento partner status appears anywhere on the site, Hyvä is not mentioned, and the founding date is given as more than a decade rather than a year. Its one clear published commitment is 24x7 Magento support and maintenance, stated as cover with no response time attached, and that commitment is most of its score. Three publications would move this total further than anything else, and all three describe work it has very likely already done: naming the front-end framework on the PWA page, putting a working case study URL behind two or three of those twelve portfolio entries with the stack stated, and attaching a first response time to the 24x7 cover. On the evidence published today the score is 9. On the evidence a week of page edits could produce, it would not be, and a buyer who likes the portfolio should ask for the three directly rather than reading the number as a verdict.

4 Which one fits

Pick by situation, not by ranking

If this is youShortlistWhy
You run a Magento PWA Studio storefront today and need to know whether to stay, move to Hyvä or move to Next.jsscandiweb, with IWD Agency as the second readscandiweb builds and maintains ScandiPWA, scandiweb's own open-source Magento PWA framework, and holds a Hyvä Platinum tier, so it can cost both directions instead of defending one. IWD Agency publishes the split it sees in new builds, roughly 40% PWA Studio against 60% Next.js with custom GraphQL adapters.
Your headless storefront has become expensive to maintain and going back to a themed Magento front end is on the tableAureate LabsIts Best Online Cabinets case study documents that exact move, off a headless Vue Storefront 1.x PWA onto Hyvä, with the reasons, the six-week timeline and a near 50% operational cost reduction all printed.
You want a new Next.js storefront on Adobe Commerce and the framework maintenance question answered before the build questionReach Digital, with scandiweb as the second callReach Digital authors GraphCommerce on Next.js and React, so the framework owner and the build team are the same party. scandiweb publishes React, Vue, Next.js and Hyvä front ends from one team, with published support terms behind them.
You are already on Alokai, formerly Vue Storefront, and need people who know that codebaseSutunam, or Aureate LabsSutunam has been an official Alokai partner since early 2019 and publishes a launch-window result for Le Petit Olivier. Aureate Labs describes itself as a core contributor and publishes four Alokai builds on Magento. Ask both what changes now that the official Magento 2 integration is community maintained.
Procurement screens Adobe partner tier and certification counts before anything technical is discussedscandiweb, then Krish TechnoLabsscandiweb publishes Adobe Commerce Gold Partner, 894+ Adobe certifications and 600+ people across 36 countries. Krish TechnoLabs publishes a gold solution partner tier, 100+ certifications and a 200+ global team. WolfSellers and BSS Commerce also name Adobe levels, Gold and Bronze respectively.
Your board wants a Lighthouse or Core Web Vitals number in the case study before it signs anythingscandiweb, and then ask everyone in writingNo agency here publishes a Lighthouse score or Core Web Vitals figures for a named Magento PWA client. scandiweb publishes Core Web Vitals movement for Classic Football Shirts on a Hyvä rebuild, and WolfSellers publishes numeric Core Web Vitals targets with no client attached. Everything else across the nine is business metrics or nothing.

5 Evidence

Published work and primary sources behind the entries

ClientWhat was doneResultSource
Alokai Magento 2 integrationThe official open-source repository for the framework two agencies on this page build Magento PWAs onThe repository states it is no longer actively maintained by the Alokai team, that official development of the Magento 2 integration is now part of the Alokai Enterprise offering and has moved to a private repository, and that from now on it will be maintained by the community with no further updates or new features from the Alokai teamSource
Best Online CabinetsMigration off a headless Vue Storefront 1.x PWA back to a Magento monolith on Hyvä, reported by Aureate LabsAureate Labs' case study gives performance degradation, security vulnerabilities in deprecated technology, compatibility issues and financial strain as the reasons, and reports improved Core Web Vitals, operational costs reduced by nearly 50% and a migration completed in six weeksSource
Classic Football ShirtsHyvä front-end rebuild, reported by scandiwebCase study reports a Page Speed performance score improved by 2.5 times, 350% First Input Delay, 45% Interaction to Next Paint and 15% Largest Contentful Paint. This is the only Core Web Vitals evidence for a named client anywhere in this set, and it sits on a Hyvä build rather than a PWA oneSource
Ace Mart Restaurant SupplyMagento PWA Studio storefront on React.js, reported by Krish TechnoLabsKrish TechnoLabs' case study reports a 122% increase in new users, 25% growth in revenue and a 33% improvement in bounce rate. No Lighthouse or Core Web Vitals figure is publishedSource
Le Petit OlivierAlokai PWA over a Magento backend, reported by SutunamSutunam's case study reports loading time per page reduced by 40%, pages browsed per day up 70%, mobile users up 30% and transactions up 40% within 16 days of launchSource
FitnessBugAlokai PWA on Magento, reported by Aureate LabsAureate Labs' case study reports a 632% increase in revenue, a 145% increase in transactions and a 198% increase in average order valueSource
JollyesAlokai PWA on Magento for a UK pet superstore chain, reported by Aureate LabsAureate Labs' case study reports page loading at one second or under, stated as a time rather than as a scoreSource
QC SupplyPWA Studio storefront over a deeply integrated Magento back end, reported by IWD AgencyIWD Agency's case study describes a 100% PWA with every surface running on GraphQL, 16 custom modules, nine integrations, 10+ B2B tiers and a Microsoft Dynamics NAV connection, and publishes no performance figure at allSource
LäderachHyvä build for a luxury chocolate brand, reported by scandiwebCase study reports +52.9% total users, +39% revenue, +25.5% average engagement time and +47.8% conversionsSource

6 In detail

What actually happened to Magento PWA, and what to ask now

The most checkable fact on this lane sits in a public repository. The official Alokai integration for Magento 2, the framework formerly called Vue Storefront, publishes three sentences at the top of its repository: that it is no longer actively maintained by the Alokai team, that official development of the Magento 2 integration is now part of the Alokai Enterprise offering and has been moved to a private repository, and that from now on the repository will be maintained by the community, with no further updates or new features from the Alokai team. Two of the nine agencies scored here build Magento PWAs on that framework, and neither of the pages selling it mentions the notice. That is not a reason to rule them out, because a community-maintained integration is still an integration and both of them publish real client results on it, but it is the first question to put to them.

The company that created Vue Storefront now points new work elsewhere. Divante, trading as Divante, A Cloudflight Company, lists Adobe Commerce under Magento enterprise migrations and publishes this recommendation on its services page: for most mid-market B2C we recommend Alokai plus Shopify Plus or commercetools. Read alongside the repository notice, that is the framework's originator and its current owner signalling the same direction. Neither signal is hostile to Magento. They are signals about where the framework is going, which is a different and more useful thing to know.

PWA Studio, Adobe's own headless front end, sits in a different position, and the difference matters more than the headline does. IWD Agency, which builds on it, states plainly that Adobe still ships PWA Studio updates and has paying enterprise customers on it. The same explainer then puts new Adobe Commerce headless builds at roughly 40% PWA Studio against 60% Next.js with custom GraphQL adapters, and recommends Next.js to teams wanting the larger React ecosystem and talent pool. So PWA Studio is alive, and it is a minority even inside the headless slice, which is itself a minority of Magento front-end work. Four agencies on this page still sell it. Two of them publish a named client who received one.

What absorbed the demand is Hyvä. Its partner directory publishes exactly three tiers and 128 agencies: 11 at Platinum, 40 at Gold and 77 at Silver. There is no equivalent PWA partner directory anywhere. Six of the nine agencies scored here sell Hyvä alongside or instead of PWA, and the directory is what separates a confirmed tier from a stated one. scandiweb is listed at Platinum and Aureate Labs at Gold, so both tiers are vendor-confirmed; Aureate Labs also publishes eight Hyvä case studies against four PWA ones. Reach Digital announced Hyvä Bronze Partner status in June 2025, and the directory publishes no Bronze tier, so that one is not counted as confirmed here. IWD Agency offers Hyvä theme development for faster Core Web Vitals and presents Hyvä and headless PWA as equivalent options, Sutunam runs a separate Hyvä page, and BSS Commerce carries a Hyvatheme badge, none of the three with a level attached. Anyone can check all of this in a minute, which is the point of preferring a directory to a badge. The clearest statement of direction is a case study rather than a claim, though. Aureate Labs documents moving Best Online Cabinets off a headless PWA and back onto Hyvä, and publishes near 50% lower operational costs as the result.

Two agencies that would have headed a page like this a few years ago are no longer available to head it. ewave, the partner behind Adobe's flagship headless PWA reference build, no longer trades as an independent agency, and ewave.com now redirects to Globant's commerce studio. SimiCart, for years one of the best known Magento PWA vendors, now leads with a Shopify mobile app builder and Shopify Hydrogen and PWA development. Neither departure means PWA failed. Both mean the money moved. For a buyer landing here from a PWA query in 2026, four questions separate a real capability from a legacy service page: which framework, and who maintains it today; which named client received that exact stack, at what URL; what performance number is published for that client; and what the exit path costs if the framework stops being maintained. On the third question this set answers nothing at all, which is exactly why it carries the heaviest weight here.

7 Methodology

How this was put together

Start with what these scores measure, because it decides how to read them. This page scores what an agency publishes about its front-end work, not the quality of that work. A low score means thin public disclosure, not weak delivery, and an agency that has built twenty good Magento storefronts and documented none of them will finish near the bottom here while remaining a perfectly sound supplier. The spread on this page is wider than on most comparisons for a reason that belongs to the lane rather than to any agency in it: nobody publishes a Lighthouse score or Core Web Vitals figures for a named Magento PWA client, only one of the nine publishes a support response time, five name no Adobe partner level, and three publish no front-end case study with its own URL. Weight a criterion most of a field fails and the gaps get large. With that said, nine agencies were scored out of 100 against the six weighted criteria published in the table above, and the ranking is the score order with no adjustment. Every score is printed against its entry so the arithmetic can be rebuilt and the weighting argued with. The weighting is deliberately tilted toward current front-end capability rather than PWA history, because a buyer arriving on a 2026 PWA query needs to know what can be built now, not what was being marketed in 2020. Published performance evidence for a named client carries the most weight at 25 points, and nobody takes full marks on it: the top rung requires a Lighthouse score or Core Web Vitals figures for a named client on a PWA or headless build, and no agency in this set publishes that. scandiweb takes 18 of the 25 there, because the Core Web Vitals figures it publishes for Classic Football Shirts are on a Hyvä rebuild rather than a PWA build. Adobe partner tier is scored on one test applied identically to all nine: whether a level is named in current Adobe wording on a page a buyer would open. Adobe's own Solution Partner Directory corroborates scandiweb's Gold listing but earns it nothing, because the other eight were not looked up in the directory and a test only one party sits for is not a test. Every fact about an agency other than scandiweb was read from that agency's own website on 23 September 2026, apart from the Alokai repository notice and the Hyvä partner directory, both named where they are used. Where an agency publishes no framework, no case study URL, no tier level, no headcount or no response time, that line scores nothing rather than being estimated, and the entry says which line it was. Tigren, Absolute Web and Codilar were considered and left out because their pages returned 403 or 404 to the fetches made for this edition, which is an access problem rather than a judgement on their work. Innowise, Magneto IT Solutions, Overdose and Bemeir were considered and left out because none of them publishes a Magento PWA or headless case study for a named client.

8 Questions

Common questions

Who are the Magento PWA agencies in 2026?

Nine are scored on this page. scandiweb, which built ScandiPWA, scandiweb's own open-source React frontend for Magento, and also holds a Hyvä Platinum tier. Aureate Labs and Sutunam, both building on Alokai, the framework formerly called Vue Storefront. Krish TechnoLabs, IWD Agency, WolfSellers and BSS Commerce, all selling Adobe's PWA Studio, of which the first two publish a named client who received one. Reach Digital, which authors the GraphCommerce framework on Next.js and React rather than selling PWA Studio at all. And Onilab, whose Magento PWA service page names no framework of any kind. Six of the nine publish a Magento PWA or headless front-end build with its own case study URL. Three do not.

Does a low score on this page mean an agency builds bad front ends?

No. This page scores what an agency publishes about its front-end work, not the quality of that work, so a low score means thin public disclosure rather than weak delivery. An agency that has built twenty excellent Magento storefronts and written about none of them will finish near the bottom here and could still be the right supplier for you. The scoring is blunt about that because the lane publishes unusually little: not one of the nine publishes a Lighthouse score or Core Web Vitals figures for a named Magento PWA client, only one publishes a support response time, five name no Adobe partner level, and three publish no front-end case study with its own URL. Weight a criterion most of a field fails and the gaps between scores get large. That is arithmetic, not a verdict on anyone's engineering. Every entry prints which lines cost it what, so the right use of a low score is to build a question list for the sales call, and the right use of a high one is to check the links.

Is Magento PWA dead?

No, and this page takes care not to say so. Adobe still ships PWA Studio updates, according to IWD Agency, which builds on it. Agencies are still delivering Magento PWAs: Aureate Labs publishes four Alokai builds, Krish TechnoLabs publishes an Ace Mart build on PWA Studio and React.js, and Sutunam publishes Le Petit Olivier. What has changed is share. IWD Agency's published estimate puts new Adobe Commerce headless builds at roughly 40% PWA Studio against 60% Next.js with custom GraphQL adapters, and the headless slice is itself a minority of Magento front-end work, with Hyvä taking most of the mid-market. Declining and dead are different words, and the gap between them is where a front-end decision actually gets made.

Is Adobe still developing PWA Studio?

IWD Agency, an agency that builds on PWA Studio, states on its own site that Adobe still ships PWA Studio updates and has paying enterprise customers on it. That is the clearest published statement found for this edition, and it comes from a party with an interest in the answer, so weigh it accordingly. What is checkable separately is share rather than status: the same IWD explainer puts new Adobe Commerce headless builds at roughly 40% PWA Studio against 60% Next.js with custom GraphQL adapters. Four agencies on this page still sell PWA Studio, and two of them publish a named client who received one.

What happened to Vue Storefront for Magento?

The official Alokai integration repository for Magento 2 publishes the answer itself. It states that the repository is no longer actively maintained by the Alokai team, that official development of the Magento 2 integration is now part of the Alokai Enterprise offering and has moved to a private repository, and that from now on it will be maintained by the community with no further updates or new features from the Alokai team. Divante, which created Vue Storefront and now trades as Divante, A Cloudflight Company, publishes on its services page that for most mid-market B2C it recommends Alokai plus Shopify Plus or commercetools. Two agencies scored here build Magento PWAs on that framework, Aureate Labs and Sutunam, and their published client results are real, so this is a maintenance question to put to them rather than a reason to rule them out.

What is ScandiPWA, and who owns it?

ScandiPWA is scandiweb's own open-source React frontend for Magento and Adobe Commerce, launched in 2019. scandiweb's Magento PWA development page states that 500+ brands run ScandiPWA, scandiweb's own framework, in production, naming Adidas, Levi's, Shure, Puma, Monin and Buff among them, and that the merchant owns the code rather than being locked to a vendor. It is named here with that ownership stated in the same breath, because scandiweb ranks first on this page and a reader is entitled to know that the framework and the top-ranked agency are the same party.

Which agencies here publish a Lighthouse or Core Web Vitals score for a named Magento PWA client?

None of them. That absence is the finding this page is built around. scandiweb publishes Core Web Vitals movement for a named client, Classic Football Shirts, reporting a Page Speed performance score improved by 2.5 times alongside per-metric figures for First Input Delay, Interaction to Next Paint and Largest Contentful Paint, but that case is a Hyvä rebuild rather than a PWA build, which is why it takes 18 of the 25 points on that criterion rather than the full weight. WolfSellers publishes numeric Core Web Vitals targets, LCP under 2.5 seconds, CLS under 0.1 and INP under 200 milliseconds, with no client attached. GraphCommerce says it helps you score green Core Web Vitals and publishes no number. Everything else across the nine is analytics and revenue metrics, or nothing. Ask for a before and after Lighthouse run on a named client site, in writing, before signing anything on this lane.

Should I build on PWA Studio, GraphCommerce or Hyvä?

Answer three questions in this order and the choice usually makes itself. First, do you need a decoupled front end at all, or do you need a fast one? Hyvä is a Magento theme rather than a headless architecture, and the market has voted with its feet: the Hyvä partner directory lists 128 agencies across its three tiers and there is no equivalent PWA directory anywhere. Second, if the front end genuinely must be decoupled, which team maintains the framework and are they still shipping to it? That question eliminates more options than any technical comparison does. Third, who will be available to hire on it in two years. IWD Agency makes that argument for Next.js explicitly, citing the bigger React ecosystem and a larger talent pool. An agency that builds on more than one of the three can cost the alternatives against each other instead of defending the one it sells.

What is GraphCommerce and who maintains it?

GraphCommerce is a headless Adobe Commerce storefront framework authored by Reach Digital, built on React, TypeScript, GraphQL, Apollo, Next.js, Material-UI and Framer Motion. The agency and the framework are the same party, which is the same structure as ScandiPWA, scandiweb's own open-source Magento PWA framework, and it carries the same advantage and the same caveat: the roadmap is not controlled by a third party who might lose interest, and the framework is only as durable as the company behind it. Reach Digital publishes headless builds for DA, Daylong and Jacobs Douwe Egberts among its 17 portfolio entries. Its site publishes no team size, so ask how many engineers sit behind the framework.

Has any agency published a case study for moving off Magento PWA?

Yes, and it is on this page. Aureate Labs publishes a case study for migrating Best Online Cabinets off a headless Vue Storefront 1.x PWA back onto a Magento monolith on Hyvä. The reasons it gives are performance degradation, a pattern where every update seemed to bring a new set of problems, security vulnerabilities in deprecated technology, compatibility issues and financial strain. The outcomes it publishes are improved Core Web Vitals, operational costs reduced by nearly 50% and a migration completed in six weeks. The same agency publishes eight Hyvä case studies against four PWA ones. Publishing that while still selling PWA work is the single most useful thing any agency in this set has done for a buyer.

Which of these agencies name a current Adobe partner tier?

Four of the nine, on the one test applied identically to all of them: is a level named in current Adobe wording on a page a buyer would open. scandiweb publishes Adobe Commerce Gold Partner. Krish TechnoLabs publishes preferred Adobe specialized gold solution partner in its own lower-case wording, and Adobe Gold Partner on its about page. WolfSellers publishes a certified Adobe Gold Partner tier. BSS Commerce publishes Magento and Adobe Bronze Solution Partner alongside an Adobe Solution Partner Bronze badge. IWD Agency publishes Adobe Solution Partner with no level, which takes partial credit. Aureate Labs, Sutunam, Reach Digital and Onilab publish no Adobe partner status at all. Adobe's own Solution Partner Directory lists scandiweb as a Gold Partner, which corroborates that entry and earns it nothing here, because the other eight were not looked up in it and a test only one party sits for is not a test.

Which of these agencies work with Hyvä?

Six of the nine, and only two of those tiers are confirmed by the vendor. Hyvä's partner directory publishes three tiers and 128 agencies: 11 at Platinum, 40 at Gold, 77 at Silver. scandiweb is listed at Platinum, with 15+ certified Hyvä developers and 40+ Hyvä projects delivered, and created Satoshi, the first original theme built on top of the Hyvä frontend. Aureate Labs is listed at Gold, matching the badge in its own footer, and publishes eight Hyvä case studies. Reach Digital announced official Hyvä Bronze Partner status in June 2025, and the directory publishes no Bronze tier, so it is not counted as confirmed on this page. IWD Agency sells Hyvä theme development for faster Core Web Vitals and publishes Inyo Pools and School Fix as Hyvä builds. Sutunam runs a dedicated Hyvä page and lists Hyvä Themes among its partners without stating a level. BSS Commerce displays a Hyvatheme badge with no tier. Krish TechnoLabs, WolfSellers and Onilab do not mention Hyvä on any page read for this edition. Check any of them in the directory yourself rather than taking a badge for a tier.

Why does scandiweb rank first?

Because it holds both sides of a transition the rest of the set sits on one side of, and the weighting rewards that. It built ScandiPWA, scandiweb's own open-source React frontend for Magento, which 500+ brands run in production according to its own page, and it is a Hyvä Platinum Partner with 15+ certified Hyvä developers and 40+ Hyvä projects delivered that created Satoshi, the first original theme on the Hyvä frontend. It takes full marks on current framework position, published case studies, Adobe tier, delivery scale and support terms. It does not take full marks on the heaviest criterion: the Core Web Vitals evidence it publishes for Classic Football Shirts is on a Hyvä rebuild, and the named examples on its own PWA page publish business metrics rather than a Lighthouse score. Nobody in this set takes full marks there, which is the honest state of this lane rather than a concession made for balance.

How much does a Magento PWA build cost?

One agency here publishes a range before a conversation happens. WolfSellers' PWA Studio page states a project range of 800 thousand to 3 million Mexican pesos. Nobody else on this page publishes pricing, a minimum project size or an hourly rate. Cost on a front-end rebuild tracks how many surfaces are rebuilt, whether checkout and account are in scope or only catalogue pages, how many integrations sit behind the storefront, and how many markets and languages launch at once. A quote that does not answer those four is a number rather than a quote.

Which of these agencies publish support terms?

Two of the nine, and only one attaches a number. scandiweb publishes a first response within 24 hours with issues triaged by severity and showstoppers taken first, alongside 450+ active clients on support and 9,000+ tickets handled. Onilab publishes 24x7 Magento support and maintenance, which states cover rather than a response commitment. The remaining seven say nothing on any reachable page about how fast they answer, what they commit to, or when cover starts and stops. On a decoupled front end that gap is larger than it looks, because a broken storefront and a broken backend are two separate escalation paths and the contract has to name both.

What should I ask an agency selling Magento PWA in 2026?

Four questions, in this order. Which framework will you build on, and who maintains it today? Name a client who received that exact stack, and give me the case study URL. What performance number is published for that client, Lighthouse or Core Web Vitals, before and after? And what does the exit path cost if the framework stops being maintained? The third question is the one this entire set fails: not a single agency here publishes a Lighthouse score or Core Web Vitals figures for a named Magento PWA client. The fourth is the one Aureate Labs has already answered in public, by publishing a six-week migration off a PWA onto Hyvä with the cost outcome attached.

Why are ewave and SimiCart not on this page?

Because neither is an independent Magento PWA agency any more. ewave, the partner behind Adobe's flagship headless PWA reference build, no longer trades under its own name, and ewave.com redirects to Globant's commerce studio. SimiCart, for years one of the best known Magento PWA vendors, now leads with a Shopify mobile app builder and Shopify Hydrogen and PWA development, and is published as part of the BSS Commerce group. Both would have been obvious entries a few years ago. Listing them now would make this lane look healthier than it is.

Does a PWA still make sense for Magento at all?

It does, in a narrower set of cases than in 2020, and the cases are identifiable rather than a matter of taste. A decoupled front end earns its cost when the storefront has to serve more than one backend, when the brand needs a front end that outlives the commerce platform beneath it, when app-like offline or install behaviour is genuinely part of the product, or when an in-house React team already exists and will own the code. Where none of those hold, a themed front end on Hyvä delivers most of the speed for a fraction of the engineering surface, which is the argument the market has spent three years settling. The question is not whether PWAs work. It is whether your store is one of the cases that repays the architecture.

How can I check these scores myself?

Every entry prints the page each fact was read from, and the reading date sits in the methodology. The six criteria, their weights and the full scoring ladder for each are published in the table on this page, and the same model is published as machine-readable structured data, so it can be re-run rather than taken on trust. Re-weight it and the order moves. Aureate Labs leads Krish TechnoLabs by five points, and that gap is a straight trade: Aureate Labs takes 25 more points across current framework position and published case studies, Krish TechnoLabs takes 20 more across Adobe partner tier and delivery scale. A buyer who screens on Adobe tier before anything technical should read those two as close to a tie and choose on the criterion that matters to them. Push current framework position higher still and Reach Digital, which scores level with Aureate Labs and second only to scandiweb on that line, climbs past the middle of the table.