Hyva’s total cost of ownership has three parts, and one of them just went to zero. Since the core theme became free and open source in November 2025, the licensing line disappeared, leaving the one-time migration build ($25,000 to $85,000 for most US mid-market stores) and ongoing maintenance, which runs lower than Luma. Phased delivery keeps each stage revenue-safe.
Most Hyva cost articles quote a migration price and stop. That answers “what will the project cost,” not the question a CFO actually asks: “what does this frontend cost me to own for three years, and how do I fund it without betting the store on one big launch?” This model answers both. It separates the build from the run, prices each honestly for 2026, and lays out a phased delivery plan so you are never one deploy away from a revenue outage.
Bemeir is the USA’s first official Hyva Gold Partner, and we scope these projects for US merchants every week. The numbers below are planning ranges, not quotes, and the drivers that move you within them are called out explicitly.
What “total cost of ownership” actually includes
A migration quote is one number. Total cost of ownership is four:
- Build. The one-time cost to migrate Luma to Hyva: frontend rebuild, extension compatibility work, design, and QA.
- License. What you pay Hyva. As of November 2025 this is zero for the core theme, with optional paid add-ons.
- Run. Ongoing maintenance, security patching, upgrades, and small enhancements, year over year.
- Risk and opportunity. The cost of downtime during cutover, and the revenue you leave on the table by not shipping the performance win sooner.
Teams that only budget the build get surprised by the run. Teams that only chase the performance win forget the cutover risk. A real TCO view holds all four at once.
The license line, after open source
This is the part of the model that changed most in the last year. Hyva’s core theme is now free and open source under the OSL 3.0 and AFL 3.0 licenses, available on GitHub and via free license keys (up to five keys per account). The former per-store license fee is gone. What remains paid is optional.
| Hyva product | 2026 cost | What it is | Do you need it? |
|---|---|---|---|
| Hyva core theme | Free (OSL/AFL) | The base frontend that replaces Luma | Yes, this is the theme |
| Hyva UI | Paid add-on, per store | Ready-made component library for faster build | Optional, speeds design work |
| Hyva Checkout | Paid add-on | Conversion-optimized checkout with PSP integrations | Optional, for advanced checkout |
| Hyva Enterprise | Paid add-on | Adobe Commerce and B2B feature compatibility | Only if you run Adobe Commerce B2B |
The takeaway for your model: the recurring license cost of a standard Hyva frontend is now effectively nil. If you evaluated Hyva before late 2025 and rejected it on license cost, the math has changed. Budget the add-ons only for the capabilities you actually use.
The build: one-time migration cost
The build is the largest single line, and its size is set almost entirely by how many of your frontend extensions need rebuilding. The ranges below are US market planning figures for 2026.
| Store profile | Frontend extensions to rebuild | Timeline | Build cost range (US) |
|---|---|---|---|
| Lean B2C | Under 10 | 4 to 6 weeks | $25,000 to $45,000 |
| Mid-market B2C/B2B | 10 to 25 | 6 to 10 weeks | $45,000 to $70,000 |
| Adobe Commerce B2B | 25+ plus B2B storefront flows | 12 to 16 weeks | $70,000 to $85,000+ |
These figures assume you are already on a Hyva-supported Magento 2.4 version. If you are on an older release, add a platform upgrade as a separate, prior cost. For the full breakdown of what drives these numbers, our Magento and Adobe Commerce development practice scopes each build against the extension inventory, not a template price list.
The run: three-year cost of ownership, Luma versus Hyva
Here is where Hyva earns its keep, and where single-number cost articles go silent. A Hyva frontend is cheaper to run than a Luma one, because the codebase is smaller, upgrades are cleaner, and the frontend has fewer moving parts to break. The illustrative model below compares owning a mid-market frontend for three years. Treat the figures as planning ranges that depend on your store’s complexity and support model.
| Cost line, 3-year horizon | Staying on Luma | Migrating to Hyva |
|---|---|---|
| Year 0 build | $0 | $45,000 to $70,000 |
| Frontend license (3 yr) | $0 | $0 (core is free) |
| Annual maintenance and patching | Higher; Luma frontend is heavier to maintain | Lower; smaller, cleaner frontend |
| Magento upgrade effort (per major) | Higher; more frontend to reconcile | Lower; Hyva structure simplifies upgrades |
| Performance and conversion | Flat; Luma performance ceiling | Higher; faster pages lift conversion |
| Developer velocity | Slower; legacy stack | Faster; modern Tailwind and Alpine |
The build is a real upfront cost. What the migration buys is a lower run rate for the next several years plus a performance ceiling that Luma cannot reach. Industry guidance puts the payback period at roughly 12 to 18 months for mid-market stores once you count reduced maintenance and improved conversion. Your payback is faster if your Luma store is currently slow, because the conversion delta is larger.
The phased delivery plan
Phasing is a cost-control tool, not just a project-management preference. A big-bang launch concentrates all your risk into one night. A phased plan spreads it, lets you bank early wins, and gives you exit points if priorities change. This is the delivery model we recommend for most mid-market migrations.
Phase 1: Audit and baseline (week 1 to 2, 10 to 15% of budget). Inventory every extension and customization, sort each into rebuild buckets, and capture your current Core Web Vitals and conversion baseline. This phase is cheap and it sizes everything else. Skipping it is the single most common cause of overruns.
Phase 2: Foundation and templates (weeks 2 to 5, 30 to 40%). Stand up the Hyva child theme and rebuild the highest-traffic templates first: home, category, and product. These are where the performance win lands hardest, so building them first means the value shows up in your data early.
Phase 3: Extensions and B2B flows (weeks 4 to 9, 25 to 35%). Rebuild or replace the frontend extensions from Phase 1, and wire in any B2B storefront flows. This is the variable phase; its size is your Phase 1 inventory total.
Phase 4: Data-layer, SEO, and checkout parity (weeks 8 to 11, 15 to 20%). Reattach analytics and Google Tag Manager, verify structured data and canonical tags, and confirm the checkout path. This is the quiet phase that protects revenue, and it is the one rushed projects cut.
Phase 5: Cutover and stabilization (launch plus 2 weeks, 10%). Deploy behind a rehearsed rollback, run a 72-hour watch on error logs and conversion, then hand off. Budget stabilization time explicitly; it is not free.
Because Phases 2 and 3 deliver visible template and performance improvements before the full project ends, phasing also improves the internal case for the investment. You are showing results, not just spending against a launch date months away.
Where TCO quietly leaks
Three mistakes inflate the total cost of ownership more than any pricing decision.
Skipping the Phase 1 audit. Teams jump into template work, then discover in week five that a critical extension has no Hyva build and needs a custom compatibility module. That surprise lands as both a schedule slip and an unbudgeted line. Audit first, always.
Underbudgeting the Tailwind v4 ramp. Hyva 1.4 moved to Tailwind CSS v4 and a Rust-based build engine, changing class conventions and config from v3. A team fluent in v3 is not instantly fluent in v4. Build the ramp into the estimate rather than absorbing it as slippage.
Over-customizing what Hyva gives you for free. The strongest cost discipline in a Hyva build is using the base components and paid add-ons where they fit instead of hand-rolling everything. Custom code is the most expensive thing you own, because you maintain it forever.
When phasing beats a big-bang launch
Phase almost always, for anything past a lean B2C store. Reserve a single-shot launch for small catalogs with few extensions and no B2B, where the whole build fits in a few weeks and the rollback risk is trivial. The moment you have B2B flows, a large extension footprint, or meaningful traffic, the phased plan is cheaper in expectation once you price the downtime risk of a big-bang cutover.
If the ownership math pushes you to reconsider the platform entirely rather than the frontend, that is a separate conversation, and an honest one. Bemeir also builds on Shopify Plus, BigCommerce, and Shopware, so we can tell you when a replatform beats a reskin. More often, for a Magento store with real integration depth, a phased Hyva migration is the lower-TCO path. You can see how we work as an extension of your team and the depth of our technology partner ecosystem that keeps the run cost low, and if you are still getting oriented, our explainer on what Hyva Commerce is covers the product landscape. The short version of who we are lives on the Bemeir homepage.
Frequently asked questions
Is Hyva really free now?
Yes. The Hyva core theme became free and open source in November 2025 under the OSL 3.0 and AFL 3.0 licenses, available on GitHub and via free license keys. The former per-store license fee is gone. Optional paid products remain (Hyva UI, Hyva Checkout, and Hyva Enterprise for Adobe Commerce B2B), but a standard Hyva frontend carries no recurring theme license cost. If you rejected Hyva on license cost before late 2025, that objection no longer applies.
What is the real 3-year total cost of ownership of a Hyva frontend?
For a mid-market US store, plan for a one-time build of roughly $45,000 to $70,000, zero recurring core license, and lower annual maintenance than an equivalent Luma frontend. The build is the dominant cost; the multi-year story is a lower run rate plus a higher performance ceiling. Most mid-market stores recoup the investment in 12 to 18 months through reduced maintenance and improved conversion, faster if the current Luma store is slow.
How do we migrate without downtime?
Phase the work and rehearse the rollback. Build and test each phase on staging, rebuild your highest-traffic templates first so value shows up early, protect the data-layer and SEO parity in a dedicated phase, and cut over behind a rollback you have already timed to run in under ten minutes. The 72-hour post-launch watch catches the rare issue before it costs revenue.
Does Hyva actually lower ongoing maintenance cost?
Yes, for a structural reason. Hyva’s frontend is a smaller, cleaner codebase than Luma’s Knockout and RequireJS stack, so upgrades reconcile faster and there is less surface area to break. The saving is in developer time on every future Magento upgrade and enhancement, which compounds over the years you own the store.
How should we budget the phases?
Roughly: 10 to 15% for audit and baseline, 30 to 40% for foundation and core templates, 25 to 35% for extensions and B2B flows, 15 to 20% for data-layer and SEO parity, and 10% for cutover and stabilization. The extension phase is the variable one; your Phase 1 inventory sets its true size, which is exactly why the cheap audit phase comes first.
