How much does Magento cost? Every layer, with sources.

Magento Open Source costs nothing to license; you pay for hosting, extensions, development and upkeep. Adobe Commerce has no public price list: it is licensed by quote, at a pricing level Adobe ties to gross merchandise value (GMV) and average order value (AOV), or to an order limit. As of October 16, 2026, the Magento agency Atwix estimates simple customizations from $5,000 and comprehensive Adobe Commerce builds at $50,000 to $500,000 or more.

Last reviewed October 16, 2026. Every Magento cost figure below names its publisher, and the table links each one.

This Magento cost guide is for merchants pricing a first build, an Adobe Commerce renewal or the upgrade they keep putting off. For the license, Magestore estimates Adobe Commerce at $22,000 to $125,000 a year on-premises; for the work, IWD Agency puts experienced freelancers at $50 to $100 an hour and established US agencies at $100 to $200 or more. Both are estimates.

Magento cost at a glance#

There is no single Magento price. Magento cost is a stack of layers, each with its own price model. The license is free or quoted, depending on the edition. Hosting is bundled on Adobe's two cloud offerings, up to the allowances in the contract, and bought separately everywhere else. Theme add-ons and extensions are priced by their vendors, development is quoted per project, upgrades come due on Adobe's dates, and card payments carry a processing fee.

The table below keeps two kinds of figure apart:

• Published by the vendor: the seller's own price page or license terms. You can check it, and it changes only when the vendor changes it.
• Published by agencies and directories: each publisher's estimate. It describes stores in general, not yours, and two estimates for the same layer can sit far apart.

Each row also names the edition it applies to, the publisher, the page, the date we read it and how often it's charged. When a page stops showing a number, the row goes, rather than keeping a stale figure.

Three readings stand out. The vendor rows hold two free licenses, Hyvä's add-ons, one hosting plan and a card fee; Adobe's own rows say how the fee is measured but name no price. As of October 16, 2026, Stripe's US standard rate is 2.9% + 30¢ per successful transaction for domestic cards, whichever edition you run. Every Adobe Commerce license price is an estimate, because Adobe publishes none. And no agency page we read prices a version upgrade, so upgrades get their own section below.

Comparing Magento with other platforms? Our sibling guide covers what an ecommerce website costs beyond Magento.

Magento pricing: Open Source and Adobe Commerce#

Magento comes in two editions with opposite price models: one is free to license, and the other has no public price at all.

Magento Open Source: free to license#

Adobe publishes Magento Open Source on GitHub under the Open Software License 3.0, and the repository also carries the Academic Free License 3.0. Both grant "a worldwide, royalty-free" license, so there is no fee to use the code. Mage-OS, a community-driven distribution of Magento Open Source, builds on the same code. Free to license isn't free to run.

Adobe Commerce pricing: a quote tied to GMV and AOV#

Adobe Commerce has no public price list: Adobe's pricing page doesn't list on-premises at all, and Elogic and IWD Agency both say Adobe doesn't publish one. What Adobe does publish is how the fee is measured. Its on-premises product description, effective July 31, 2023, licenses the software "per Base Package" at "the Pricing Level identified in the Sales Order", defined as "the GMV and AOV tiers, Order Limit, or other pricing tier." Under Adobe's General Terms, use beyond what you licensed is invoiced. Three details matter before you sign:

• GMV leaves out shipping, handling and customs costs, taxes and financing charges.
• An order counts as a transaction "even if such order is later subject to a refund, return, chargeback". Returns don't shrink your GMV.
• The base package includes "up to 15 Store Views"; more are sold as an add-on, "Per Pack of 15", and Adobe's terms require notice "promptly upon the launch of each Store View".

As of October 16, 2026, Magestore estimates $22,000 to $125,000 a year on-premises, tiered by annual gross revenue. Elogic's GMV bands match Magestore's almost figure for figure, starting at "About $22,000" on-premises under $1 million GMV. IWD Agency notes that "published starting figures sat around the low twenty thousands annually for the self-hosted edition", and adds: "Treat those as historical reference points, not quotes." Elogic's caveat: "Your quote from Adobe can be different."

Adobe Commerce Cloud pricing#

Adobe hosts both cloud offerings, and its pricing page shows each with "Get pricing" and no figure. As of October 16, 2026, Magestore estimates the cloud license at $40,000 to $190,000 a year, tiered by annual gross revenue, and Elogic at about $40,000 a year under $1 million GMV. Magestore counts the hosting inside that license, but Adobe's product description limits it to the vCPU, storage and CDN allowances in the contract; keep exceeding one and you "will be required to license additional capacity." Adobe Commerce as a Cloud Service, per its overview, delivers updates continuously, which "eliminates the need for manual patching"; its product description sets the licensed "GMV/AOV or Order Limit" in the Sales Order and meters storefront requests, SKUs and catalog calls.

Magento hosting costs#

On Adobe's two cloud offerings, Adobe runs the hosting. Everywhere else it's a separate bill, and Adobe's system requirements set the floor. For 2.4.9, the on-premises table lists PHP 8.5, OpenSearch 3, MariaDB 12.3 or MySQL 8.4, Valkey 9, Varnish 8 and RabbitMQ 4.3, and Adobe "supports only the system requirement combinations listed". That stack, your catalog and your traffic size the server, so a hosting figure that knows none of them is a guess.

One vendor publishes a starting point: as of October 16, 2026, Hypernode lists cloud plans from €129 a month with 2 CPUs, 4 GB RAM and 150 GB SSD, excluding VAT.

The estimates, as of October 16, 2026:

• IWD Agency: managed Magento hosting for a small-to-midsize store "generally runs from under a hundred dollars a month into the low thousands for high-traffic stores on dedicated or clustered infrastructure."
• Magestore: $100 to $500 a year for Open Source, and $500 to $6,500 a year for Adobe Commerce on your own servers.
• Elogic: "About $5,000 to $60,000 or more a year" for Adobe Commerce on-premises.

The last two price the same layer and barely overlap.

Hosting is also where speed is won or lost, and speed is work we do: server response times cut from seconds to milliseconds.

Theme and extension costs#

Since November 10, 2025, the Hyvä Theme has been free. Hyvä relicensed it "to OSL3 + AFL3", and its license page reads "Now entirely Open Source and Free." Hyvä's paid products, from its product page as of October 16, 2026, in euros as listed:

• Hyvä UI: €250.
• Hyvä Checkout: €1,000.
• Hyvä Commerce: €3,000 a year.
• Hyvä Enterprise, sold as "All-in-one for Adobe Commerce": €7,500 the first year, then €5,000 a year.

Hyvä's configurator adds an update-and-support plan to UI and Checkout: €250 a year from the second year, or €1,000 once for five years.

Extensions are priced by each vendor. As of October 16, 2026, Magestore estimates $60 to $600 per extension, and IWD Agency says quality commercial extensions "generally run from under a hundred to several hundred dollars each, many now on annual subscription."

The license is only the first cost. Every extension needs a release for your next Magento version, or someone replaces or ports it. On Hyvä, "Modules based on the Magento luma or blank themes require a Compatibility Module to work with Hyvä," per Hyvä's docs. Count your extensions before anything else: each one is a line item in every future upgrade.

Magento development cost#

Atwix is one of the agencies that publish prices, in the FAQ on its custom Magento development page, which carries no date. As of October 16, 2026, it lists these estimated ranges:

• Simple customizations: "start at $5,000–$10,000".
• Custom modules: "$10,000–$30,000".
• ERP integrations: "$25,000–$75,000".
• Comprehensive Adobe Commerce builds: "$50,000–$500,000+".

Atwix's own framing: "Ranges vary by scope." Elogic estimates "a custom mid-market build" at "about $25,000 to $150,000" and enterprise builds at "about $100,000 to $500,000 or more".

Hourly rates, each its publisher's estimate:

• IWD Agency: experienced freelancers "$50 to $100 per hour"; established US-based agencies "$100 to $200 or more".
• Elogic: "about $40 to $80 per hour in Eastern Europe and $60 to $130 in Western Europe".
• Clutch: its Magento directory listed 6,757 companies on October 16, 2026, and the agency profiles on its first page listed hourly rate bands from under $25 up to $150–$199.

IWD Agency's two bands meet at $100 an hour: a freelancer at the top of the range costs what an agency charges at the bottom.

Why the spread? A "custom module" can be a shipping rule or a two-way ERP sync, and one band has to cover both. Rates follow region and seniority, and the total is rate times hours, so a cheaper hour can still make a pricier project. Compare the scope lines, not the rates: which modules, which integrations, which tests, and who fixes what breaks after launch. Every band also prices stores its author hasn't seen. That's why we don't publish ours: our number comes after we've read your code, your integrations and your data.

What a Magento upgrade costs#

None of the four agency pages we read on October 16, 2026 publishes a price band for a version upgrade. Atwix lists none, Elogic's upgrade row reads "One project per release line" with no price, and IWD Agency offers only that "Small, regular upgrades cost a fraction of a multi-version rescue project." The nearest figure is an estimate in Magestore's support table: "Magento update and security patch installation" from $1,000 a year, which is upkeep, not an upgrade project.

The cost follows seven drivers:

• The version gap. From Adobe Commerce 2.4.4-p18 to 2.4.9, Adobe's requirements move PHP from 8.1 to 8.5, OpenSearch from 2.19 to 3, MariaDB from 10.6 to 12.3 and the cache from Redis 7.2 to Valkey 9.
• Extensions. Each needs a release for the target version, a replacement or a port.
• Custom modules. Each one is tested against the new PHP and the new core.
• The theme. Luma with overrides, Hyvä with its compatibility modules, or fully custom.
• Integrations. ERP, shipping, tax and marketplace connections each need a regression run.
• Hosting. Who controls the PHP, database and search versions, and whether Adobe's cloud deadlines apply.
• Test coverage. Automated tests shrink the regression work. Without them, someone writes the checklist first.

The edition matters too: Adobe's Upgrade Compatibility Tool "is available for Adobe Commerce instances only", so on Open Source that check takes other tools and hand work.

The work recurs. Adobe ships security patch releases (the -p versions) at least once a year for every supported line (2026's came on March 10 and May 12), and between them monthly isolated security patches, "tested exclusively against" the latest -p release of each line and applied "cumulatively, in release order." A store behind on -p releases sits outside what Adobe tested.

Adobe's dates set the deadlines. As of October 16, 2026, its lifecycle policy ends standard support for 2.4.7 on May 31, 2027, for 2.4.8 on May 31, 2028 and for 2.4.9 on May 31, 2029. Our Magento upgrade service page carries the full table. Coming from Magento 1 is a different job, scoped as an ecommerce migration.

The cost of staying on an unsupported version#

As of October 16, 2026, Adobe's lifecycle policy gives 2.4.4 and 2.4.5 security-only fixes until May 31, 2027, and 2.4.6 extended support until August 31, 2027, then security-only fixes until May 31, 2028. For 2.4.6, Adobe's requirements page says those provisions "are available to Adobe Commerce customers only." Open Source gets less: Adobe's APSB26-153 update says "Open Source merchants can only download patches for version 2.4.7 or later."

On Adobe's cloud, Adobe "will no longer maintain Cloud environments running unsupported Commerce versions": from June 1, 2027 for 2.4.4 and 2.4.5, and June 1, 2028 for 2.4.6 and 2.4.7, after which "your ecommerce storefront will go offline." PHP runs out too: 8.1 reached end of life on December 31, 2025 and 8.2 ends December 31, 2026; Adobe marks both "PCI compliance at risk".

The emergency version: CVE-2026-75650, rated CVSS 10.0, entered CISA's catalog of known exploited vulnerabilities on September 8, 2026, and Adobe's fix, which reaches back to 2.4.4 on both editions, includes rotating the encryption key and every credential it protected.

Or patch first. We backport the security fixes Adobe no longer ships for your version and test them on a copy of your store. It lowers the risk. It doesn't remove it, and it doesn't fix an end-of-life PHP. Our standard: pen-test findings closed and retested against every bypass variant we could throw at them. Backports that help more than one store will be published on our free Magento security patches page.

Stuck on an old version? We'll patch you now and upgrade you when you're ready.

Magento B2B pricing#

Adobe's native B2B features (company accounts, shared catalogs, negotiable quotes, requisition lists, Quick Order, purchase orders, payment on account and company credit) come from a B2B extension that Adobe's B2B introduction describes as installed "in your Adobe Commerce store". So B2B on Adobe's own module needs an Adobe Commerce license plus a separate B2B license: Adobe's extensions page labels Adobe Commerce B2B "Adobe Commerce only, requires a separate license", and its Commerce on Cloud product description lists the B2B Module as an add-on. None of the license estimates above says whether it covers B2B, so ask for it as its own line in the quote. On Magento Open Source, each B2B feature comes from an extension or custom code, with its own license and its own line in every upgrade. If the storefront is Hyvä, Hyvä pitches Hyvä Enterprise to "Make the most of the B2B Suite". Which features you need natively decides the edition, and Magento B2B walks through that choice.

What drives the total#

Two quotes for the same Magento store can sit far apart, and often they priced different stores. Eight inputs set the total. Pin them down and quotes start to line up:

• Edition. Open Source has no license fee. Adobe Commerce adds a quote at a pricing level set by GMV and AOV tiers or an order limit, and B2B is licensed separately.
• Version gap. The distance from your version to a line in standard support, which as of October 16, 2026 means 2.4.7, 2.4.8 or 2.4.9.
• Catalog size. SKUs, variants, attributes and price rules. A bigger catalog means more indexing, import and test work.
• Storefronts. Each store view, language and currency adds setup and testing, and Adobe's base package includes up to 15 store views, with more sold in packs of 15.
• Integrations. Each system named (ERP, PIM, shipping, tax, marketplaces), with the direction data flows and how often. Atwix's estimate for ERP integrations alone runs from $25,000 to $75,000.
• Customizations. Pricing rules, configurators, checkout changes and anything else that overrides core behavior.
• Data quality. Duplicate products, missing attributes, unusable images and years of URL history all turn into hours.
• Team. Who on your side decides, writes content and tests. A quote that assumes you'll do the testing looks cheaper on paper.

Send every bidder the same brief: your version and edition, the module list from composer.json and app/code, every system the store talks to, a SKU count and who signs off. Then ask which items each price covers. Different answers explain different totals. A quote that arrives without asking for most of this priced a store it imagined.

It's the brief we ask for before we scope Magento development, and it makes every quote easier to compare, ours included.

When moving costs less than staying#

Leaving Magento sometimes costs less than staying. The inputs decide it, not anyone's sticker price. On the staying side: license renewals, hosting, the extension count, the upgrade debt between your version and a supported one, and custom code you'd rebuild anyway. On the moving side: the new platform's plan and app fees, the rebuilt theme and integrations, the data move, a redirect for every changed URL, and replacements for B2B features the new platform lacks. Compare both over the same number of years. If Shopify is the likely destination, start with moving from Magento to Shopify.

Magento cost questions

Sources