Hyvä just split its product line, and the choice between Hyvä Commerce and Hyvä Enterprise now comes down to one question: which Magento you run. At its Solstice townhall on July 29, 2026, Hyvä renamed and reorganised the whole suite, shipped a checkout rebuilt on Magewire v3, and put hard numbers on an ecosystem that now spans 7,600 live sites. For a studio that builds premium storefronts on Hyvä, this is the most consequential release of the year, and it finally clears up a naming tangle that has confused merchants for months.
What Hyvä Commerce and Hyvä Enterprise actually are
Hyvä Commerce is the full Hyvä suite for Magento Open Source and Mage-OS, and Hyvä Enterprise is that same suite with Adobe Commerce compatibility on top. That is the entire distinction. Before Solstice the Enterprise label read like a premium tier you paid up for, which pushed Open Source merchants toward assuming they were getting a lesser product. The rename kills that reading. Both products carry the same theme, the same UI kit, the same CMS and the same checkout. The only axis that matters is your Magento edition: Open Source and Mage-OS merchants take Commerce, Adobe Commerce merchants take Enterprise, per Hyvä's Solstice recap and a clear breakdown from Foundation Commerce. It is a positioning fix as much as a product one.
What shipped at Solstice
The headline releases are a Hyvä Checkout beta on Magewire v3, a generally available Menu Builder, and pilots for point of sale and a native mobile app. The checkout rewrite is the technical centre of gravity: Hyvä Checkout 1.4.0-beta moves to magewirephp/magewire 3.2.0 and raises the minimum PHP floor to 8.2, per the Hyvä Checkout changelog. Magewire is the layer that updates address forms and shipping options without a full page reload, so a major version bump there touches every custom step a merchant has bolted on. Menu Builder reached general availability as a standalone visual tool for mega menus and mobile drill-downs. Hyvä POS entered pilot at 50 euros per terminal per month for the Pro tier, and Hyvä Pocket launched as a free Apple app for store insights. The ecosystem numbers behind all this are real: 7,600 live sites, roughly 1,700 in the Netherlands, around 1,200 in the United States, and both Germany and the United Kingdom now in the 700s, with 500 agency partners and 31 new agencies joining in 2026.
Hyvä Commerce vs Hyvä Enterprise: which one you need
Choose by platform, not by feature list, because the feature sets are identical. If you run Magento Open Source or Mage-OS, you need Hyvä Commerce. If you run Adobe Commerce, you need Hyvä Enterprise. The interesting part for a studio is what this rename signals. Hyvä is treating Open Source and Mage-OS as first-class, not as the budget option, at exactly the moment more brands are questioning whether Adobe Commerce licensing earns its cost. We have made the data-ownership case for the open stack before in our note on Mage-OS versus the hosted platforms, and Solstice hardens it: a merchant can now run the same premium Hyvä front end on Mage-OS that an Adobe Commerce brand runs, with no feature penalty. That collapses one of the last real arguments for paying for the enterprise edition purely to get a better storefront. On our Hyvä commerce builds the edition question is now a licensing-and-scale decision, not a front-end-capability one.
What we would change this quarter
If you run Hyvä Checkout, start the Magewire v3 upgrade in staging now, but keep it out of production until it leaves beta. The 1.4.0 line is still beta, and its second beta already shipped a security fix for a payment-method availability bypass, dated July 13, 2026, per the same changelog. That is exactly the kind of fix you want landed and soaked before it touches real orders. Three concrete moves follow. Confirm your servers meet the PHP 8.2 floor, since anything older will not run the new checkout at all. Audit every Magewire customisation against the v3 extension points, because a checkout that reloads state on every field is where custom code breaks quietly. And decide the Commerce versus Enterprise question deliberately if you are also weighing a re-platform, rather than defaulting to Adobe Commerce out of habit. We fold this kind of version readiness into the deployment automation on our commerce work, so a Hyvä point release is a green or red build rather than a launch-week surprise. If a Luma to Hyvä move is on your roadmap, our migration guide and our earlier read on the Enterprise bundle both fold cleanly into the new naming.