Magento Open Source Adobe Commerce Storefront design & front-end Independent · not affiliated with Adobe
Magento Themes Store Storefront Lab
Published 13 Nov 2026 13 min read

What Magento actually costs, and why nobody can quote you a number

No single price can responsibly summarise Magento’s total cost, because licensing, implementation, extensions, integrations and ongoing operations vary substantially between projects.

The only firm price is the download

Magento Open Source is free to download. That is the only unambiguous price Adobe publishes for the platform, and it is also the number most often allowed to distort Magento cost comparisons.

Adobe Commerce is licensed. Adobe does not publish list pricing for it, so there is no official figure to place in a comparison table. Any precise “Adobe Commerce costs” number in circulation comes from an individual quote, an estimate or a commercial arrangement that applied at some point to some merchant. It is not a list price that can be checked and applied to a different catalogue, theme, integration set or operational workload.

That distinction matters because the licence is rarely the largest part of a Magento budget. The material costs tend to appear in infrastructure, implementation, commercial extensions, connected systems, payment and tax services, and the work required to keep the store supported and operational.

Giving a single total for Magento would therefore be misleading even if a defensible source existed. A meaningful figure has to state what is included, who is responsible for each part and which operating assumptions sit behind it.

What the software does—and does not—include

Magento Open Source provides the core commerce application. Adobe Commerce adds licensed capabilities under Adobe’s commercial agreement, but its price is not published in a form that permits a generic quote.

Neither option removes the need to budget for the work around the platform. The code is not a ready-made shop for a particular catalogue. It is a foundation that must be configured for products, customer accounts, pricing, promotions, checkout, fulfilment, tax, shipping and the operational processes of the business using it.

This is where quotations diverge most sharply. A store with a small catalogue and a straightforward delivery model may need relatively little customisation. A store with complex variants, approvals, subscription behaviour, regional pricing, multiple warehouses or tightly controlled B2B ordering will require substantially more design and implementation work.

The distinction between configuration and custom development is particularly important. Configuration uses behaviour already present in the platform and adjusts it to the business. Custom development creates new behaviour or changes core logic. A quote that presents both as “Magento setup” conceals the largest source of variation in the estimate.

Hosting is an operating budget, not a line item

Hosting must be judged against the services required by the current on-premises release rather than the lowest price that can run a demonstration. Adobe lists PHP 8.5, MariaDB 12.3 or MySQL 8.4, OpenSearch 3, Valkey 9, RabbitMQ 4.3 and Composer 2.10 as the supported combinations for 2.4.9.

That list changes what “Magento hosting” means. It is not simply web space for PHP and MySQL. The application also relies on search, cache and session handling, asynchronous messaging and suitable application capacity. Elasticsearch and Redis are not listed as supported for 2.4.9, which can force architecture and migration work for stores built around older combinations.

The cost drivers include catalogue size, traffic patterns, order volume, peak periods, image and media weight, background indexing, the number of queues and workers, and whether production and non-production environments are separated. A cheap environment may be adequate for browsing but underpowered when the catalogue is reindexed, imports run, queues build or a campaign sends a burst of traffic.

Operational maturity also affects the bill. Managed services can reduce server administration while adding recurring charges. A hosting team with Magento experience may cost more in the contract but avoid emergency work caused by unsuitable PHP workers, queue configuration or database tuning.

Before accepting a hosting figure, ask whether it includes production, staging, backups, monitoring, deployment, secrets, TLS, email delivery and a realistic response to failed jobs. See hosting and operations for the broader question of whether a provider’s offer is an application host or merely a server rental.

Queue workers and reindexing belong in the estimate

Magento is not only a collection of page templates serving requests. It performs asynchronous work through queues, cron and background consumers. Search indexing, catalogue imports, product updates, scheduled jobs and integration synchronisation can all create sustained demand for CPU, memory, database connections and messaging capacity.

Many operational surprises appear when these processes are treated as occasional housekeeping. If queue consumers are throttled, orders can be delayed while jobs wait. If indexing is scheduled during the busiest trading period, search and category pages can become slow. If worker capacity is reduced to save money, the application may appear healthy while order, stock or integration data is falling behind.

A credible budget therefore needs to describe normal load and peak load separately. The catalogue size matters, but so do the frequency of updates, the number of scheduled tasks, the behaviour of imported data and the amount of work triggered by a large promotion.

Reindexing should also be tested as an operation rather than mentioned in passing. The relevant questions are how long it takes, whether it affects live traffic, whether it can be stopped safely and whether another environment has enough capacity to carry it out. A quotation based on steady browsing activity may look economical while omitting the work that makes the platform dependable.

The build is shaped by the business, not by the platform

Implementation cost reflects the decisions that must be translated into technical behaviour. Product type design, navigation, search requirements, customer registration, wish lists, recurring payments, custom pricing, promotional rules, shipping logic and checkout requirements each add scope.

Custom work increases when Magento must accommodate a non-standard process. It also increases when existing business rules are undocumented or when different teams disagree about how the store should behave. Clarifying the process before development is generally more useful than asking an agency to estimate vague requirements, but that clarification is still work that belongs in the plan.

Theme work forms one part of this. Luma is the default Magento storefront theme and is built on LESS, Knockout.js and RequireJS, with Blank as its parent theme. A bespoke design still needs responsive templates, accessibility, performance, browser behaviour, product and category variants, checkout states and all the edge cases around real inventory.

Hyvä changes the front-end approach because it uses Tailwind CSS and Alpine.js rather than Knockout and RequireJS. Hyvä Theme became free and open source on 10 November 2025 after previously requiring a one-time licence. Hyvä Checkout, Hyvä Commerce and Hyvä Enterprise remain separate paid products. This can alter both build and maintenance cost, but it does not remove requirements such as catalogue migration, extension compatibility, checkout behaviour or testing.

A quote should separate theme design, front-end implementation, back-end configuration, custom development and quality assurance. Combining them hides whether a cheaper estimate omits work or simply applies a different scope.

Extensions can carry licence, development and future compatibility costs

Extensions cover everything from payment methods and shipment integrations to SEO, B2B functions, product feeds and advanced promotions. Their cost is not captured by a single category because an extension may be open source, commercially licensed, subscription-based or supplied under terms that include support and updates.

Two extensions with similar visible features can have very different total consequences. One may support the current Magento release and provide a supported upgrade path. Another may depend on older APIs, include a large amount of code or leave merchant-side compatibility work unresolved.

Compatibility should be assessed against the exact extension version, the exact Magento release and the customisations already present in the store. An extension that installs is not necessarily compatible with the whole implemented system. Its database changes, hooks, templates, observers and queues may conflict with other extensions or with custom code.

The commercial terms matter as well as the initial fee. Ask whether updates are included, how long access to releases or support remains available, what happens when the merchant changes plan, and whether the extension is covered for the next platform upgrade. A low purchase price can be less attractive when maintenance is separate or when the extension needs work before it supports the current release.

Keep the module layer separate from the implementation estimate. Otherwise it becomes impossible to tell whether a merchant is paying for a feature, an integration or the work needed to make that feature safe inside the store.

Integrations often cost more than the connection

An integration normally connects Magento to an ERP, PIM, CRM, accounting system, customer service platform, marketplace, warehouse, email provider or advertising service. The connector may have a licence, but the wider project can include mapping, data cleansing, synchronisation design, error handling and operational monitoring.

Direction matters. Magento may push orders to an ERP and receive stock levels back, but the commercial flow, system of record and acceptable delay can differ for every service. An apparently simple stock feed can require rules for bundles, configurable products, reservations, returns and multiple warehouse locations.

Existing data affects the effort. Duplicate customers, inconsistent SKUs, malformed product attributes and multiple catalogue sources can turn connector installation into a data project. The quote should identify who prepares the data and who resolves the exceptions.

Authentication and security also need to be included. This covers service accounts, encryption, secret rotation, access logs, webhook validation, IP allow lists and the handling of personal data. A connector that works in test may still need production-grade access controls and monitoring.

Integrations should be priced by business process rather than by connector. The relevant scope is which records move, which system owns each field, how often they move, what happens when synchronisation fails and who responds when it does.

Payment and tax costs sit beyond the storefront

Payment fees and tax service charges are not Magento licence costs, but they belong in a commercial budget for a Magento store. The merchant’s effective cost can vary with the provider, payment method, transaction profile, risk profile, currency, region and contract.

The project also needs a budget for gateway configuration, fraud controls, recurring payments, refunds, chargebacks, reconciliation and checkout states. Payment methods can alter the implementation because stored cards, tokenised methods, local payment schemes, instalments and marketplace transactions have different integration and testing needs.

Tax requirements need the same treatment. The cost may depend on jurisdictions, product categories, exemptions, shipping treatment, tax-inclusive pricing and the relationship between Magento and the selected tax service. A simple assumption about tax can become custom work once the business serves multiple regions or unusual product types.

These charges should be labelled as operating costs rather than folded invisibly into the build. A supplier claiming to quote “everything” should distinguish what Magento will charge from what gateways, payment processors, tax providers and the merchant’s own finance team will charge.

Maintenance is where the real operating cost appears

Initial delivery is only the visible part of the lifecycle. A production store needs monitoring, backups, security patching, dependency review, performance investigation, queue oversight, failed-job handling and periodic compatibility testing.

Magento releases and third-party extensions can introduce changed behaviour across the whole stack. Patching a package does not prove that the storefront still completes checkout, applies promotions correctly, updates inventory or synchronises orders. Maintenance should therefore include regression testing proportional to the change.

The support model also affects the work. A retained agency can provide continuous access to people who know the implementation. An internal team can control the work more closely but must have the capacity to deal with both routine tasks and unexpected production issues. Shared operational responsibility is often more practical than assigning every alert to one channel without an escalation path.

Support contracts should state response expectations, included hours, included services, exclusions and the treatment of third-party extension problems. “Maintenance” is too broad to compare unless both parties know what it contains.

Security and upgrades cannot be treated as optional extras

Security patching is continuous operational work. It includes monitoring for issues affecting Magento, PHP, the database, Composer packages, server libraries and any third-party code installed in the project. It also includes testing changes before they reach production.

Upgrading adds another layer. A new Magento release can require application work, dependency changes, database migrations, extension updates, revised integrations and updated customer-facing behaviour. The cost rises when custom code has diverged from core patterns, when several extensions lag behind or when the merchant has deferred changes for a long period.

For the current release, Adobe lists regular support for 2.4.9 until 31 May 2029, for 2.4.8 until 31 May 2028, and for 2.4.7 until 31 May 2027 with extended support to 31 May 2028. Regular support for 2.4.6 ended on 11 August 2026. Magento 1 reached end of life on 30 June 2020.

Staying on an unsupported release does not remove its cost. It postpones upgrade work, increases security and compatibility exposure, narrows access to current packages and makes future migration harder. The saving appears in the short term because the future work has not yet been paid for.

Magento Open Source is the free download, not a version that can be left running indefinitely without funded care. Adobe was founded around Magento’s acquisition in 2018, but the current ownership does not change the lifecycle arithmetic facing an individual store.

Staging and release discipline need to be funded

A safe Magento release needs somewhere to test it. Staging can mean a separate environment with production-like data, a sanitised dataset and enough capacity to run indexing, queues and integrations. It is not useful if it shares fragile resources with production or if credentials prevent realistic testing.

Some hosting arrangements include non-production environments, but the scope varies. Check database isolation, data refresh, mail delivery, payment sandbox access, secret management and the availability of background workers. These services consume resources even when nobody is browsing the staging site.

Deployment procedures also carry a cost. They need repeatable steps, rollback planning, database backup and restore checks, and a clear decision about who authorises a release during trading hours. If every update depends on one specialist manually changing production servers, the process will become a bottleneck and a risk.

Staging should appear as a named part of the operating model, not as an optional courtesy environment. It is also where compatibility work for lagging extensions can be identified before it affects customers.

How to obtain comparable quotes

A useful estimate starts with a scope, not a platform name. The brief should identify the catalogue structure, sales channels, markets, languages, payment methods, tax rules, shipping models, customer types, integrations, required functionality, current platform state and acceptance criteria.

Existing stores need an audit rather than an installation estimate. Include the Magento release, installed extensions, custom modules, theme work, integrations, technical debt, hosting setup, known performance problems and the desired release date. Without that information, two agencies may be pricing completely different transitions.

Hosting and agency proposals should use the same assumptions. Specify expected load, data volumes, environments, support hours, service boundaries and responsibility for third-party licences. Ask each supplier to separate software acquisition, implementation, recurring licences, infrastructure, operations and optional work.

The questions that expose a quote most likely to grow are direct. Which platform release is assumed? Which extensions and versions are included? What is custom work? Which environment receives the estimate? Does the test strategy cover the catalogue and integrations as they will operate? What is excluded? Who owns deployment, patching and upgrade preparation?

Also establish what happens when the scope changes. A reliable proposal identifies assumptions and change-control points. A suspiciously firm total often relies on assumptions that are neither written down nor challenged.

The defensible answer is a range built from evidence

Magento Open Source’s download price is clear. Adobe Commerce’s pricing is not publicly quotable as a standard figure, and a precise number offered as a general market price deserves scrutiny rather than confidence.

The honest Magento cost is assembled from the requirements of one store: the release it will run, the catalogue it must handle, the services it will use, the extensions it will rely on, the integrations it needs, the support model it wants and the amount of custom behaviour it requires.

That answer will still be a range, but it will be an operational range rather than a marketing claim. Its assumptions can be tested, its omissions can be exposed and its future increases can be anticipated. A generic number cannot do any of that, which is why quoting one would obscure the costs that matter rather than settle them.

Questions this page answers

Is Magento 2 free?
Magento Open Source is free to download. Adobe Commerce is licensed, and Adobe does not publish list pricing for it.
How much does Magento cost?
A single total would be misleading. A meaningful figure must state what is included, who is responsible for each part and which operating assumptions apply.
What does Magento include?
Magento Open Source provides the core commerce application, while Adobe Commerce adds licensed capabilities. Neither is a ready-made shop and both require configuration for products, accounts, pricing, checkout, fulfilment, tax, shipping and business operations.
What affects Magento hosting costs?
Costs depend on catalogue size, traffic patterns, order volume, peak periods, media weight, background indexing, queues, workers, and whether production and non-production environments are separated.

More in Platform choices

Editorial & corrections: [email protected]