Hyva agencies in 2026, ranked on Hyva's licensed product line

First place is decided on the heaviest line and it is the one no agency can write about itself. Hyva's full agency register, read on 5 October 2026, carries five scandiweb listings and every one of them is Platinum, across five countries, out of 18 Platinum listings in a register of 460. Among the agencies ranked here, two hold more than one listing at Platinum: scandiweb with five and ZERO-1 with two. What that tier costs to hold is published by Hyva rather than inferred: at least 45% of a partner's points must come from licence sales of Hyva Commerce, Enterprise, Checkout and UI, and Platinum requires a minimum of five developer certifications and at least 70% of live Hyva projects passing Google Core Web Vitals. Hyva's own curated partner page, read the same day, puts the certification count at 30 or more certified Hyva developers and 50 or more Hyva projects delivered, in Hyva's voice rather than scandiweb's. The tier itself was announced in becoming a Hyva Platinum Partner, which does not explain what the tier counts, and that gap is what this page exists to close.

On the breadth of the licensed line this entry takes the top mark, and so do five agencies below it: Foundation Commerce, Fluid Commerce, Dev Team, Vendic and Cream. The criterion caps at three products carrying a published scope of work, and this entry carries four of the six. Hyva theme development carries a Hyva POS section that states plainly what the work is, that it integrates Hyva POS into an existing setup, configures how the stores operate and tests real checkout flows before go live, and what Hyva POS means for omnichannel retailers backs it with a seven minute account of the product, including that a free tier covers a single register while the Pro version adds offline mode, a customer display and advanced staff management. A first look at Hyva Commerce is a code level review written from early access, and it is where Hyva UI is named. The ATX Fitness launch on Hyva Commerce carries Hyva Commerce, Hyva Checkout and Hyva CMS together on one build. Hyva Enterprise is named, in how to work with Hyva on Magento 2, but only inside a licence sentence and never with a scope of work attached, so two of the six, Hyva Enterprise and Hyva UI, are named without scope.

On named clients this entry loses to five agencies below it, and they are Foundation Commerce, Vendic, elgentos, Aureate Labs and JaJuMa. The reason is precise. The ATX Fitness case names the client, names three licensed products, Hyva Commerce, Hyva Checkout and Hyva CMS, and describes the scope in detail, a United States store launched in 2.5 months with the homepage, listing and product pages, cart, Hyva checkout, account, blog and CMS pages built out, 15 or more extra features before launch and a quote from the client's chief executive. What it does not publish is a commercial figure. Its results read as all green Core Web Vitals, stated in words with no number, and 93 to 100% PageSpeed scores for accessibility across key pages. A second scandiweb page describes the same range as PageSpeed scores of 93 to 100 without scoping it to accessibility, so a reader cannot tell from the two pages which score the range belongs to. That is a question rather than a contradiction, and it caps this line at 14 of 18 while elgentos, Vendic and Foundation Commerce take 18.

On the Adobe side it takes 13 of 16, level with Fluid Commerce and Dev Team, and the shortfall is the same shape. Adobe Commerce development names Adobe Commerce Gold Solution Partner in body copy, Adobe's own Solution Partner Directory carries the same Gold listing, and the Adobe certification set publishes 894 or more Adobe certifications behind a practice of 23 or more years, 700 or more clients and 2,100 or more eCommerce projects, with a 95 NPS. Six of the ten agencies here publish no Adobe partner status at all on the pages read, namely Vendic, ZERO-1, elgentos, Aureate Labs, Cream and JaJuMa, which matters because Hyva publishes that an Adobe Commerce store needs Hyva Enterprise rather than Hyva Commerce. The full mark needs Hyva Enterprise described as delivered work as well, and that is the one thing missing.

The clearest loss on this page is the licence line, where this entry takes 4 of 10, behind Aureate Labs on 8 and Fluid Commerce on 6. The correct account exists and it is the most precise in this comparison: how to work with Hyva publishes that the Hyva Theme became free and open source on 10 November 2025, relicensed under OSL3 and AFL3, and that Hyva Checkout, Enterprise and Commerce remain proprietary and paid. Both halves of the split, with the exact date. Against that, reasons to use the Hyva theme is undated and still live, and it describes Hyva Checkout as React based and completely headless due to GraphQL, calls it available for free and open source, advises against using it, and prices the Hyva theme at 1,000 euro as a one time payment. Hyva's own Checkout page, which that sentence links, says Hyva Checkout is a commercial product based on Magewire, a PHP based technology, and 1,000 euro is now the price of the Checkout rather than of the theme. No scandiweb page read names Magewire, and no current price for any licensed Hyva product appears on the pages read, which is why the top rung is out of reach whatever happens to the contradicting page.

What holds the entry at the top is the boundary work, which takes the full mark. The first look at Hyva Commerce publishes that content created with the current Hyva library will not carry over automatically and that a transition plan is essential. The reasons page publishes that one of Hyva's drawbacks is that it does not work with extensions out of the box. The ATX case records that the build introduced technical risk because scandiweb was among the earliest adopters, and that accessibility scores were to be optimised further following the next Hyva update, both of which work against its own sales case. One more concession belongs here. The fuller credential account states 22 or more years where the canonical figure is 23 or more, and gives the Adobe Commerce start year as 2009 where scandiweb's own solutions page gives 2008, so two of the figures a buyer would screen on disagree across the site. And a separate guide to the best point of sale systems for Magento compares seven options and does not name Hyva POS, so a buyer who lands there would not learn that the product exists.

Second place is decided by the one thing this lane is thinnest on, and Foundation Commerce is the only agency here that has it twice. Two named clients carry commercial figures attributed to Hyva Checkout specifically rather than to a Hyva build in general. Citizen Watch states that it supercharged the checkout page performance by rolling out Hyva's checkout solution, and publishes a 141% increase in online revenue described as more than doubling turnover, a 43% increase in conversion rate and a 67% boost in page speed performance, alongside a Best Conversion Improvement award at the Hive Awards 2025. Again Faster publishes a 54% increase in conversion rate, a 64% increase in page speed and a 63% increase in checkout completion, with that last figure attributed in the sentence to increasing page speed using Hyva Checkout and simplifying data entry, delivered in 8 weeks.

On product coverage it takes the top mark with three carrying its own scope: Hyva Commerce, Hyva Checkout and Hyva CMS. Its Hyva Commerce page states that it builds high performance Hyva Commerce websites, its accelerator page states that a Hyva Commerce migration starts with a full audit of third party modules, its Hyva Checkout page sells tailoring every step of the checkout journey, and on Hyva CMS it goes further than description by stating it can quickly customise the platform to a merchant's requirements. It also publishes a Hyva POS explainer and a claim to work across the full Hyva product suite, with no POS client or delivery scope behind it. Hyva UI was not found on the pages read, which is the one product gap.

Its register listing is Platinum, in the United Kingdom, read on 5 October 2026. Where it falls away is the Adobe line, and the shortfall is specific rather than general. Its homepage badge row and every page title read Adobe Solution Partner and Adobe Commerce Solution Partners, with no level attached, and no Adobe or Magento certification count was found on the pages read. Hyva Enterprise is explained accurately, that it gives everything in Hyva Commerce plus compatibility with Adobe Commerce features, and never claimed as delivered work. That combination takes 4 of 16 against 13 for the agency in first place and for two others, which is most of the 9 point gap.

The licence line costs it too, and for a reason worth checking before a call. One post publishes the change correctly and to the day, that from 10 November 2025 the licence fee barrier is gone, and another publishes the current split as plainly as anyone: on Magento Open Source you need Hyva Commerce, on Adobe Commerce you need Hyva Enterprise. Against that, a 2022 frequently asked questions post is still live and still prices a Hyva Themes licence at 1,000 euro, and the same page publishes a recommended checkout list that labels the commercial Hyva Checkout product URL as React Checkout while listing Magewire Checkout separately as something coming soon. No euro figure for Commerce, Enterprise, Checkout or UI appears anywhere on the pages read. On published limits it takes the full mark, naming licence gating, Luma JavaScript dependency and the need for a complete front end rebuild, and going against its own sales case by telling merchants to own their own licences in case they change agency, and by recommending two rival checkouts.

Third place publishes more of the licensed line as its own work than anyone here, all four separately licensed products, and it is the only agency on this page whose Hyva Enterprise claim has a named client behind it. Its Hyva service page states that it has experience developing stores with Hyva Commerce but that it is not necessary for all business to business companies, so it runs a discovery session to establish which version of Hyva fits, that its Hyva development team is able to add Hyva checkout for business to business and direct to consumer companies, and that it is experienced in using Hyva UI, which it also built its own business to business accelerator on. On Enterprise, a July 2026 post states that it recently implemented Hyva Enterprise for its client Cablecraft.

That client is also where the entry gives ground. The Cablecraft result is explicitly withheld, with the page saying the project, the implementation and the results will follow in a forthcoming case study. A second Enterprise client, Pearson Hydraulics, is published as using Hyva Enterprise and the majority of its features, with the build detail attached to a generic Hyva front end and an enterprise resource planning integration rather than to the licensed product. A third, Stoves Are Us, is published as using Hyva Checkout while the conversion and search result is attributed to the theme. So the scope is described and no metric value is attached to a licensed product, which takes 14 of 18 rather than 18.

On the Adobe line it takes 13 of 16, level with the agency in first place, by a different route: Hyva Enterprise named as delivered work plus a Silver Adobe Solution Partner status stated with the level in current Adobe wording, and no certification count published. It is also the only agency here that publishes Hyva's current Enterprise pricing, a fixed 7,500 euro for the first year and 5,000 euro a year on renewal rather than varying by gross merchandise value, traffic or storefront count, and dates that change to July 2026.

Its register listing is Gold, in the United Kingdom, read on 5 October 2026, and that single line is what keeps it off the top: 14 against 26 for the two agencies holding Platinum in more than one country, scandiweb and ZERO-1. On the licence line it publishes the clearest statement of the split found anywhere, that in November 2025 Hyva announced its core theme was open source and free to use while Hyva Commerce, Hyva Checkout and Hyva UI remain on a paid subscription model, and then loses 2 points because older posts on the same site still price Enterprise and Commerce at 2,500 euro a year and still describe Hyva UI as free with the theme. On published limits it takes the full mark for the sharpest section on this page, headed that Hyva Enterprise does not make business to business complexity disappear, naming accumulated bespoke customisation, front end extensions and integration dependencies as the mechanisms, and concluding that it would not recommend treating a migration as a simple theme replacement.

Nobody here publishes the product line as a list better than this. Its Hyva page enumerates the ecosystem as Hyva Theme for the front end, Hyva Checkout for a conversion focused checkout, Hyva UI as a reusable component library, Hyva Enterprise as scalable tools for enterprise merchants and Hyva POS as unified in store and online commerce, and it is the only agency on this page that both names Hyva POS and explains Hyva Enterprise properly. On Enterprise it writes the clearest account in this comparison, that it brings Hyva Theme, Hyva Checkout, modern content management tools and enterprise capabilities into a unified platform built specifically for Adobe Commerce, and then claims the work as its own, helping merchants unlock Adobe Commerce with Hyva Enterprise whether they are migrating from Luma or Magento's progressive web app, launching new or modernising. On Checkout it publishes a service list covering new implementations, migrations from the default or a third party checkout, fully customised journeys, integrations to enterprise resource planning, order management and payment gateways, and business to business fulfilment workflows, and calls it its preferred checkout framework for all new builds.

The gap between that list and the evidence behind it is the whole entry. Flooring Superstore is a named client on Hyva Checkout with a genuine two phase scope published, the storefront modernised on Hyva Theme and then the checkout rebuilt, integrated with payment gateways, enterprise resource planning and order processing. It publishes no results at all: the results panel carries the labels checkout completion rate, conversion rate, checkout abandonment and mobile checkout performance with no values, and the page states that as the checkout has only recently launched the focus is on measuring over time. Its headline Hyva Checkout reference, which it calls one of the most sophisticated such projects, is for a European football club it does not name. So 14 of 18, and the page prints the empty panel rather than quoting the unattributed 40% conversion figure from its own Hyva page headline.

On the Adobe line it takes 13 of 16, by a third distinct route: Hyva Enterprise named as its own service line plus a published count of 24 Adobe Certifications on its homepage and its Magento development page, alongside 50 or more development professionals. What it does not publish is an Adobe partner level in current wording; what it publishes instead is Magento Solution Partner status, which is the pre Adobe phrasing. Its register listing is Gold, twice, for the United Kingdom and the Philippines, read on 5 October 2026, which takes 17 on the heaviest line. Its own news post announces Hyva Silver Partner status and describes itself as one of the few Silver Partners in the Asia Pacific region, so it publishes a tier one rung below the one the register gives it, which is an under claim rather than an over claim.

The licence line is where it scores lowest of any agency in the top five. Its Hyva page defines Hyva as a performance first ecosystem and lists five products, and on the pages read it never states that any of them is paid, licensed or priced, and never states that the theme is free. Hyva Commerce, the product a Magento Open Source merchant needs, is also missing from a list that includes Enterprise and POS. That is 2 of 10. Against that it takes the full mark on published limits, with the sharpest single sentence in the set, that Hyva alone is not a silver bullet and that images, fonts, JavaScript, caching, hosting and third party integrations all have to be optimised for the out of the box gains to be retained, and with a named client whose Hyva build was underperforming a year after implementation, published as a case study.

This is the only agency here with a page whose whole job is to explain the Hyva suite commercially, and it takes the top mark on product coverage because three products carry its own advisory scope: Hyva Commerce, Hyva Checkout and Hyva CMS. Its Hyva Commerce page states that the suite bundles Theme, Checkout, CMS and admin tools and that it helps a merchant decide what belongs in their store, and in Dutch it is more concrete still, that with Hyva Commerce the question becomes which module to deploy when and which to leave alone, and that it advises per shop. On Checkout it publishes that Hyva Checkout replaces the Luma checkout and that payment methods, shipping logic and business to business flows are tested step by step. On Hyva CMS it publishes the live view editor in feature detail. Hyva Enterprise is named once, correctly, as what Hyva Commerce needs to support Adobe Commerce, and Hyva UI once inside a bundle description, both without scope.

On named clients it takes the full mark, and the evidence is unusually careful. Huissteden was rebuilt on Hyva Theme and Hyva Checkout together, with third party scripts removed or loaded on demand, the cookie bar rendered server side, images served automatically as right sized WebP and Magewire adding products to the cart without a page refresh. It publishes Google Lighthouse mobile across five named templates with the heaviest product page going from 37 to 97 and the five averaging a 74.6% improvement, plus RUMvision real visitor scores of 100, 100, 99, 100 and 95, and then qualifies its own award by stating the result was not achieved on an empty store. Paco Verpakkingen is published on Theme and Checkout with 45 or more custom modules and six custom checkout modules for guest registration, payment method filtering and value added tax validation. TopaShop is labelled a takeover plus Hyva Commerce, with 60% reduced technical debt on modules and a 99 of 100 RUMvision score.

Its register listing is Platinum, in the Netherlands, read on 5 October 2026, and its own Hyva page goes further, calling itself the first Hyva Platinum Partner in the world. What costs it third place is the Adobe line, where it takes 2 of 16. Adobe is not published as a partner status anywhere on the pages read, no Adobe or Magento certification count appears, and Adobe is named only as a platform a client migrated away from and as the vendor focused on enterprise shops. Since Hyva publishes that an Adobe Commerce store needs Hyva Enterprise, that is a real gap for half this lane's buyers rather than a scoring artefact.

The licence line costs it as much again, and it is the one place a page positioned as pricing does not deliver. It carries a section headed what Hyva costs, states that licences run through Hyva and apply per store, that Hyva Checkout is licensed separately next to the theme, and that Hyva Commerce puts Theme, Checkout, CMS, admin theme and image editor under one licence. It then publishes no euro figure for any of them, deferring everything to the intake, and in answering whether Hyva is free it says Magento Open Source is free while the Hyva products carry a per store licence, which reads as though the theme is still paid. That is 2 of 10. It does take the full mark on published limits, stating flatly that Hyva only replaces the front end and that the catalogue, orders and integrations stay as they are, that every third party module with front end output needs a Hyva compatible version which it inventories up front, and offering, on every Hyva page, an introductory conversation that includes the answer that you should not start this. Its own rate card is published at 130 euro an hour for custom work.

This entry shares the top mark on the heaviest line and then publishes less of the product line than any agency above it, and the distance between those two facts is the whole entry. Its register listing is Platinum under both the United Kingdom and the United States, read on 5 October 2026, which is 26 of 26, the same as the agency in first place. It also publishes a certified Hyva developer count, three, naming them as among the very first Hyva Certified Associate Developers, which is one of only three counts published anywhere in this research, the others being the 30 or more that Hyva itself publishes for scandiweb and the two that Synolia publishes, which is not ranked here. That announcement is dated June 2025 and the number it gives, three, is below the five certifications Hyva publishes as the Platinum minimum, so either the published count is behind the bench or the register reading and the agency's own page are measuring different moments. A reader cannot settle that from what is published, and it is worth a question on a call rather than a conclusion here.

On the one licensed product it does publish, it goes deeper into the code than anyone. It states that it developed the Instore Collect and multi source inventory functionality for Hyva Checkout, delivered the first implementation of ShipperHQ support for Hyva Checkout, contributed to Hyva and Hyva Checkout, and maintains a large in house automated test suite built for Hyva Theme and Checkout. One post walks through a checkout build as a sequence of steps that begins with purchasing the Hyva Checkout licence, installing its own standardised Hyva Checkout base theme and running a pre prepared library of Hyva Checkout Selenium tests, which is the plainest third party confirmation on this page that the product is a bought licence. Hyva Commerce is named once as a market signal and Hyva UI once descriptively, both without scope, and Enterprise, CMS and POS were not found on the pages read. Note that its own open source point of sale product, built on Hyva, is not Hyva POS.

Its named client sits one rung below the top for a precise reason. Barr Display is named on Hyva Checkout with ShipperHQ and the scope is specific, gathering extra customer information where large orders ship by less than truckload and may need liftgate or delivery location detail. The figure it publishes for that client, Core Web Vitals good URLs lifting from 19% to 85% in a little over two weeks, is attributed to switching to Hyva rather than to the checkout, so it is not counted as a metric on a licensed product. On the Adobe line it takes 2 of 16: no Adobe partner status and no certification count were found on the pages read, and Adobe appears only as a platform name beside Magento Open Source.

What it does better than anyone is publish against itself, and it takes the full mark for it. It devotes an article to whether Hyva guarantees Core Web Vitals and answers no, naming three mechanisms: an agency adding JavaScript libraries, a second CSS library and bad practices to the theme files, a merchant loading a content block with a video and thirty half megabyte images, and third party JavaScript dumped onto the page. It calls its own fastest checkout build potentially reckless. It published an article about losing a fifty thousand pound build because the work came in inside existing retainer hours, and in it names a large development team as a possible red flag. It publishes its own Hyva search research with the Luma comparison number intact, 94% of Hyva sites improving against 47% of Luma sites across 37 sites, which deflates its own headline. One thing to update rather than to hold against it: its Platinum announcement, dated October 2024, describes the agency as one of just seven companies worldwide at that tier, and the register read on 5 October 2026 carries 18 Platinum listings.

On the named client line this is one of five agencies taking the full mark, alongside Foundation Commerce, Vendic, Aureate Labs and JaJuMa, and the case behind it is the best documented business to business checkout in this comparison. EFKA, an aluminium frame manufacturer, had its checkout rebuilt around its exceptions, differing delivery dates, shipping methods per product group and customer specific rules, and the page explains the engineering reason it worked: because Hyva Checkout has far fewer moving parts than the Luma checkout, the logic could be built inside the checkout instead of around it. The published result is 34% fewer abandoned carts, 22% fewer customer service requests and 15% more orders, after roughly three months for the Hyva work and a further month for the checkout. Seven more named clients are tagged on Hyva Checkout in its case fact boxes, with scope described on several and no figures.

Its Hyva Checkout practice is published as hours and as code. It states it has implemented over 20 Hyva themes and over 5 Hyva Checkout implementations, that those implementations typically range between 50 and 200 hours, and that where Hyva's own integrations stopped it built its own: PostNL and ShipperHQ support Hyva Checkout already, and it implemented support for Paazl itself, and where Postcode.nl supports the checkout it implemented Loqate itself. Hyva UI carries its own scope as a design route with hour bands, a rebuild on Hyva UI components at 300 to 500 hours against a fully custom design at 400 to 700, and it states that using Hyva UI as a foundation reduces cost. Hyva Commerce and Hyva CMS are named only as a planned next step for one client, so two products carry scope rather than three.

Its register listing is Platinum, in the Netherlands, read on 5 October 2026, and it publishes that accurately as the first Hyva partner in the Netherlands and now a Platinum Partner. The Adobe line is the only zero on this page: Adobe is not published as a partner status anywhere on the pages read, no certification count appears, Hyva Enterprise was not found, and Adobe is named once only as the vendor whose default progressive web app solution it says scores lower than a standard Hyva installation. For a buyer on Magento Open Source that costs nothing; for a buyer on Adobe Commerce it is the whole conversation.

The licence line takes 2 of 10 and the reason is an out of date sentence on its main Hyva page: that Hyva offers two products, the Hyva Theme and Hyva Checkout. Its own case page already names Hyva Commerce and Hyva CMS, and nothing on the pages read states that the theme is now free or that any product carries a subscription. Its blog gets the technology right where almost nobody does, that Hyva Checkout is built on top of Magewire, a system that lets its backend developers write checkout logic in PHP and XML, while one case page calls the product based on Laravel Livewire, which is the framework Magewire ports rather than the thing itself. It also uses Hyva React Checkout as its own label for bespoke React and GraphQL checkouts it builds, which a reader could easily mistake for a Hyva product. On published limits it takes the full mark: it published a build where it deliberately left the checkout on the old theme because that part of the shop was the most entangled, stated the downside itself, that one part of the shop still carries the old JavaScript, published the limits of its own React checkout including that it needs React knowledge to maintain, and then recommended the competing route as more robust and less maintenance heavy.

This is the agency to read if you want to know what Hyva costs, and it takes the highest mark on this page for it, 8 of 10. It publishes the theme as free because it has become open source, previously priced at 1,000 euro, Hyva Checkout at a one time fee of 1,000 euro, Hyva UI as a separate one time purchase at 250 euro where it used to be bundled with a paid theme licence, and Hyva Commerce at 3,000 euro a year with the upgrade credits itemised, up to 1,000 euro each for an existing Theme and Checkout licence plus 250 euro per unused prepaid support month. It is also the only agency on this page that answers the checkout question correctly, naming Hyva React Checkout as an open source community maintained initiative built on React against the commercial product's dedicated development and regular updates. Two points come off for Hyva Enterprise being published at 2,500 euro a year, where Hyva publishes 7,500 euro the first year and 5,000 euro on renewal, and for its own template product pages still telling a buyer that a Hyva theme licence must be purchased separately.

On named clients it takes the full mark. Regton is titled as a Magento, Hyva and Hyva Checkout transformation, the scope is described as installing and customising the Hyva checkout to the client's needs and adding Omnifinance compatibility for Hyva Checkout, which it states was a market first, and the published figure is a page speed score moving from 14 to 84 on mobile with reduced cart abandonment stated in words. One caution for anyone reproducing that: a second Aureate Labs page publishes the same project as a page speed score improving from 14 to 92, so a reader cannot reconcile the two figures from what is published. The Regton page also concedes the starting condition, a store the client describes as overwhelming at over 100 extensions.

Product coverage sits at 18 because two products carry its own scope rather than three. Hyva Checkout does, through Regton. Hyva UI does, and unusually it is sold rather than described: Hyva UI components at 250 dollars as an add on to its own template product, with a Figma design file at 220 dollars, an installation service and a separately priced Figma file, and it publishes a Hyva UI guide of its own. Hyva Commerce, Hyva Enterprise and Hyva CMS are explained editorially rather than claimed as delivered work, and Hyva POS was not found on the pages read.

Its register listing is Gold, in India, read on 5 October 2026, and it publishes that accurately, having announced the move up from Silver. That single line is most of the distance to the top: 14 against 26. On the Adobe side it takes 2 of 16, with no Adobe partner status published and the nearest claim worded as official Magento partner. On published limits it takes the full mark, telling merchants that even with the theme open source they still need to budget for design, development, compatibility work and optional add ons such as Hyva Checkout, naming the child theme dependency its own product has on the Hyva licence, and going furthest of anyone against its own revenue by stating that any certified Magento or Hyva developer can do the installation work and that a buyer is free to explore another partner.

This entry is the clearest evidence that this page asks a different question from the comparable one about theme engineering, where the same agency scores 27 of 100. Here it takes the top mark on product coverage, because it is the only agency on this page with a dedicated landing page for each licensed product: one for Hyva Commerce, one for Hyva Checkout, one for Hyva POS and the Hyva Theme alongside. Hyva Commerce is published as a complete suite that goes further than the Magento front end, with Hyva CMS and live view, an image editor, media optimisation and an admin dashboard named as its components. On Hyva Checkout it states its own scope plainly, that its team, selected as a Hyva Platinum Partner, handles a smooth implementation and configuration fully tailored to the shop and provides ongoing support, and it adds a technically useful detail almost nobody else publishes, that in some situations it implements Hyva Checkout alongside the standard Luma theme for a shop that has not fully moved to Hyva yet. On Hyva CMS it publishes release level detail, including that the visual editor's coverage extended from pages and blocks to category and product detail pages in version 1.3.0.

Its register listing is Platinum, in the Netherlands, read on 5 October 2026, and it publishes that accurately and goes further than most by telling a reader where the tier sits, describing Platinum as the highest partner level within Hyva. Its named client is Meerdanlicht, published in June 2025, where it advised renewing the Magento shop completely and implementing both the Hyva Theme and Hyva Commerce, used the Hyva Commerce content management system with live preview to make campaign pages faster to build, and built a rail configurator on top. No numeric figure is published against it, only that the result leads directly to more sales and less pressure on customer service, which takes 14 of 18.

Two lines cost it the rest. On the Adobe side it takes nothing: Adobe is not published as a partner status anywhere on the pages read, no certification count appears, Hyva Enterprise was not found, and the whole suite is framed as being for Magento Open Source, so an Adobe Commerce merchant reading these pages would be pointed at Hyva Commerce when Hyva publishes that they need Hyva Enterprise. On published limits it is the only zero on this page. Nothing was found on the pages read stating what a Hyva licence or Hyva Checkout does not cover, there is no caution about implementation quality and no statement of project risk, across four product pages that otherwise read as the most complete product documentation any agency here publishes.

The gap worth raising on a call is between the pages and the proof. It publishes a dedicated page for Hyva Checkout and a dedicated page for Hyva POS and no client against either, and its flagship Hyva Commerce case publishes no metrics. It does take 4 of 10 on the licence line for something nobody above it manages cleanly: a July 2026 release post states that Hyva Themes, the base under Hyva Commerce, is now free to use and continues to be developed. That statement is correct and dated, and it sits in a release blog rather than on the Hyva Theme product page, which carries no mention of licence or cost at all.

If the question is how the licence actually works in practice, this is the most complete answer on the page, and it is also the most contradicted. Its Hyva Checkout guide publishes that the checkout requires its own licence separate from the theme, that Hyva Checkout requires a store already running the Hyva Themes front end, that after the first year a recurring annual fee of 250 euro covers support, security patches and new features, and, the detail a buyer almost never sees, that agencies must purchase a separate plan for each client project. It publishes Hyva Commerce correctly at 3,000 euro a year as an annual subscription and explains the trade in credit toward it. It also resells the licences openly: its own rapid launch product is priced at 2,999 euro with a Hyva Theme and Checkout licence offered as a 2,000 euro option.

That last figure is where the licence line comes apart, and it takes 2 of 10. It states the standard one time licence fee as 1,000 euro for Hyva Themes and another 1,000 euro for Hyva Checkout, on a page carrying no date, where the theme has been free since November 2025. Its main Hyva service page repeats that Hyva Themes involve a one time licence fee. And it publishes Hyva UI as a free library, in one place as provided free of charge to anyone holding a valid Hyva Theme or Hyva Commerce licence, where Hyva's own store sells it at 250 euro. Hyva UI being free is in fact the most commonly repeated error in this whole comparison, and this is one of the pages carrying it.

On named clients it takes the full mark. Rosemarie Schulz is published as a rescue in which it rolled out Hyva Theme and Hyva Checkout, moved payment processing to Mollie and customised the front end to preserve the store's familiar look, with Cumulative Layout Shift from 0.3 to 0.0, Largest Contentful Paint from 1.6 seconds to 0.8, First Contentful Paint from 1.3 to 0.7 and Time to First Byte from 0.9 to 0.4. No measurement tool is named beside those figures and no commercial figure is published, but the client, the licensed product and the scope are all there.

Its register listing is Gold, in Germany, read on 5 October 2026, and it publishes that accurately alongside Hyva Technology Partner and Core Contributor status, and it discloses its own tier history, Silver in 2024 and Gold in 2025, which is rarer than it sounds. On the Adobe side it takes 2 of 16: no Adobe partner status was found on the pages read, the only Adobe reference is a Magento Marketplace verified extension provider badge, and Adobe Commerce is named only inside its description of Hyva Enterprise as an add on for Adobe Commerce users providing compatibility for business to business features, Adobe Sensei and Live Search. On published limits it takes the full mark, because it treats the licence mechanics as limits in their own right and adds that Hyva implementation requires deep expertise in Magewire, Alpine.js and Tailwind CSS, while its own product pages argue against retained agency revenue by promising code ownership and no vendor lock in.