How much does Magento 2 cost? Implementation, maintenance and development

Magento Open Source: PLN 0 for the licence

Magento Open Source is free e‑commerce software developed in the open. You can use it without paying a licence fee for the platform itself.

This is confirmed by the official Magento Open Source page (opens in a new tab).

The Open Source edition provides, among other things:

• management of products, categories and variants;
• customers, the cart and orders;
• price rules and promotions;
• configuration of several websites, stores and store views;
• content management;
• an API for integrating Magento with other systems;
• the ability to install extensions and build your own features.

No licence fee does not mean, however, that Adobe provides free hosting, server administration or technical support.

A company using Magento Open Source is itself responsible for providing suitable infrastructure and organising the work of maintaining the platform. It can do this with its own team or hand it to a Magento agency.

Say a manufacturer launches a D2C store on Magento Open Source. It pays Adobe no subscription for the software itself. It does bear the costs of building the store, hosting, ongoing maintenance and any extensions.

Adobe Commerce: the paid version of Magento

Adobe Commerce is a commercial product. Compared with Magento Open Source it offers additional capabilities, including extensive B2B sales features.

Several Adobe Commerce delivery models need to be told apart, though:

The Adobe Commerce models differ in how much control you have over the application, how it is extended and who is responsible for updates.

Adobe Commerce as a Cloud Service, for example, is a SaaS offering in which Adobe manages the core application, the infrastructure and updates. The on-premises and PaaS models allow different ways of customising and maintaining the code.

Adobe does not publish a single Adobe Commerce licence price for every company.

Commercial terms are agreed individually. You can check the current offer model on the official Adobe Commerce pricing page (opens in a new tab).

Before comparing costs, establish which services and resources the contract includes. Do not automatically add separate hosting to an option where suitable infrastructure is already covered by the Adobe Commerce fee.

Is Magento Open Source always cheaper than Adobe Commerce?

That cannot be judged from the licence price alone.

Magento Open Source avoids the cost of commercial software. But if the company needs many advanced features that Adobe Commerce provides out of the box or through its products, you need to compare the cost of building and later maintaining them yourself.

B2B sales are a good example. A standard Magento Open Source install does not include the full set of B2B features that Adobe Commerce offers.

Complex company account structures, order approval processes or quote negotiation may call for additional extensions or custom development.

That is why, before choosing a Magento edition, it is worth comparing the total cost of the solution over several years, not just the first invoice. We cover the differences between the editions in more depth in our comparison of Magento 2 with other open-source platforms.

A Magento 2 implementation for PLN 39,000 net: AURORA ONE

Aurora Creation offers a Magento 2 implementation with a Hyvä frontend as AURORA ONE for PLN 39,000 net.

It is a specific offer for projects that meet the requirements of a standard implementation. It covers one market, one language version and one main currency.

The scope includes, among other things:

• installing and configuring Magento 2;
• a Hyvä frontend tailored to the brand identity;
• configuration of the core sales features;
• the standard store views;
• moving products and customer accounts within an agreed scope;
• the ElasticSuite search engine;
• Google Tag Manager and GA4 configuration;
• testing the main purchase paths;
• launching the store in production;
• 10 hours of support and an SLA in the first month after launch.

The planned implementation time is 1 to 3 months, provided the project's start conditions are met and the necessary materials are delivered.

What matters, though, is what the standard price does not cover.

An extensive ERP integration, custom B2B processes, migrating order history, a complex SEO migration or a bespoke design of every view from scratch all need a separate analysis and quote.

The same applies when a new store has to serve several markets with different sales rules from day one.

PLN 39,000 net is the price of the specific AURORA ONE scope, not a universal price for implementing any Magento 2 store.

Can a Magento 2 implementation be paid in instalments?

Yes, at least with some offers on the market.

Aurora Creation offers two ways to pay for the standard AURORA ONE scope:

The twelve-month option adds up to more than the base implementation price. When comparing proposals, check not just the size of the instalment but the sum of all payments.

Spreading the implementation cost over several months also does not mean the store's other running costs are automatically included in the instalment.

How much does a custom Magento 2 implementation cost?

A custom Magento 2 implementation has no fixed price. It requires an estimate of the actual scope of work.

A large project can cost more than PLN 100,000 net, and with many non-standard processes and integrations the budget can reach several hundred thousand złoty. These are not official Adobe price ranges, however, nor a verified average for the Polish market. Every project has to be assessed on its own.

Compare two scenarios.

1. 01

   Scenario A: a manufacturer launches a new D2C store

   The company has its product data ready, wants to sell in one market and needs standard catalogue, cart, payment and delivery features. It does not need extensive integrations with internal systems.

   Such a project can fit a fixed-scope implementation model.

2. 02

   Scenario B: a manufacturer launches a D2C and B2B platform

   The company wants to sell directly to consumers and to its distributors. Trading partners have individual prices and purchasing terms, and product availability has to match the data in the ERP.

   On top of that, B2B orders have to respect credit limits, the right account managers and a specific way of fulfilling deliveries.

   In a project like this you design not only the store's interface but also how the business processes work and how information flows between systems.

It is these differences that decide the development scope and the cost. You can read more about such a solution on the Magento 2 implementation for B2C and B2B sales page.

Does Magento 2 need a dedicated server?

Not always.

A properly prepared VPS can be enough to run a Magento 2 store if its load and requirements fit within the available resources.

A dedicated server or larger infrastructure can be justified by higher traffic, heavy data imports, many integrations or more demanding processes.

The choice of infrastructure should follow from the project's real requirements, not from the mere fact of using Magento.

What should the price of Magento hosting include?

When comparing offers, look beyond the CPU, RAM and disk space.

What also matters:

• server administration and updates to infrastructure components;
• service monitoring;
• backups;
• the ability to restore the store after an outage;
• management of certificates and infrastructure security;
• the scope of technical support.

It is also worth asking about test and staging environments, especially if the store will be developed regularly.

How much does Magento 2 maintenance cost at Aurora Creation?

Aurora Creation offers Magento 2 maintenance as AURORA CARE. It is a monthly technical service covering monitoring, security, outage handling and an SLA.

There are three packages, differing in the team's hours of availability.

Every package has the same core maintenance scope. The difference is the team's availability.

The care covers store monitoring, handling critical outages, security updates, basic stability care and technical adjustments to legal changes within the scope of the service.

That is an important distinction. If a problem can be detected automatically, the client should not be the only one who learns about it first.

Monitoring can, for example, detect a stopped process responsible for certain background tasks, or a problem affecting order placement. That lets diagnosis start sooner, instead of waiting for reports from the store's users.

What is an SLA in Magento 2 maintenance?

An SLA (Service Level Agreement) sets the agreed parameters of the service, including support availability and commitments on handling outages.

For AURORA CARE, the public offer states a response time of up to 2 hours and a fix time of up to 4 hours under the rules of the chosen package. The detailed terms, incident classification and exceptions should be checked in the SLA agreement.

When comparing offers, watch the difference between response time and fix time.

Response time is about starting to handle a ticket. Fix time refers to the commitment to restore correct operation, under the terms of the agreement.

The words “24/7 support” on their own do not yet say on what terms and how quickly the provider must act.

Does Magento 2 maintenance include updates?

Ongoing technical care should cover responding to vulnerabilities and installing agreed security updates.

That work has to be kept apart, however, from larger Magento version upgrades, which may require code changes, adapting extensions and extensive testing.

In Aurora Creation's offer, security updates belong to AURORA CARE, while larger upgrades that need a project of their own are delivered as development tasks.

Is hosting included in the price of Magento maintenance?

Do not assume so.

At Aurora Creation, hosting with server administration and AURORA CARE are separate services. They can be used together, but their prices have to be added up.

For example:

The amount does not include planned development or external tools and subscriptions.

Magento 2 development: hourly billing or a fixed price?

There are different ways of billing development work on the market.

In the hourly model, the client pays for the time worked. With a fixed price, the price of the agreed scope is known before the work starts.

Aurora Creation offers fixed-price Magento 2 development as AURORA EVOLUTION.

Before a task starts, its scope, acceptance criteria and price are agreed. If the agreed task takes longer than planned, the cost of the accepted scope does not go up.

Additional requirements that come up later get a separate quote.

AURORA EVOLUTION covers planned development of the store. Maintenance, monitoring, outages and security updates remain the separate domain of AURORA CARE.

How much does adding another market to Magento 2 cost?

As AURORA CROSS, Aurora Creation offers launching another market in an existing Magento 2 store for PLN 8,000 net.

The price covers one additional market to a defined standard, using the current template and architecture of the running store.

The scope can include configuring the market version, language, domain, currency, taxes and basic sales settings, and importing supplied translations.

The fixed price depends on being able to reuse existing solutions, without building new, custom integrations and processes.

If launching a new country requires rebuilding the checkout, adding new modules or an extensive ERP integration, that work is quoted separately.

Example 1. A standard Magento 2 store with basic maintenance

A manufacturer launches a new D2C store in one market. It chooses an AURORA ONE implementation, VPS hosting and the basic maintenance package.

On these assumptions, the company should plan PLN 77,400 net for the implementation and the store's first year after launch.

This is not the total cost of running an e‑commerce business. The calculation leaves out, among other things, marketing, payment provider fees, order handling costs, additional licences and planned development.

Example 2. A Magento 2 store with extended technical care

The company chooses the same implementation standard but needs longer team availability and a dedicated server.

In this option the cost comes to PLN 103,800 net.

Both examples assume the store fits the standard AURORA ONE scope. These amounts cannot be applied automatically to a B2B platform with dedicated integrations or a custom frontend.

How do you plan a budget for Magento 2 development?

It is worth separating the spending needed to keep the platform stable from investment in extending it.

A manufacturer might, for example, plan to launch a new market in year two and to expand B2B sales in year three.

These are not ongoing maintenance costs. They are separate projects whose scope and price should be set from their requirements.

When building a budget for the coming years, prepare a base cost scenario first and then add the planned development tasks.

Paid modules and extensions

Magento has a large extension ecosystem. Some extensions are free; others carry licence or subscription fees.

Before buying, check the update terms, the availability of support, compatibility with your Magento version and whether the module works with the chosen frontend.

A module that at first looks cheaper than building your own can bring extra costs at upgrades or architecture changes.

External tools

A store may use paid search, marketing automation, analytics, marketplace integration, review management and other tools.

Payment provider fees and other transaction charges come on top.

Not all of these costs are specific to Magento, but they belong in the overall e‑commerce budget.

Preparing product data

Putting the product catalogue in order can take extra work, especially for manufacturers with a large range and many variants.

Technical data, descriptions, media and category structures should be prepared so they can be imported correctly and updated later.

With ERP and PIM integration, it also matters to settle which system owns which information.

Larger platform upgrades

Upgrades may require changes to installed modules, custom code and integrations.

The scope of that work depends on the technical state of the store and the extent of earlier modifications.

It is worth agreeing before the implementation how larger upgrades will be planned and quoted.

The client team's time

The budget should also account for the time of the people responsible for e‑commerce, product data, logistics, accounting and internal systems.

The company's staff have to make decisions, supply data and take part in testing.

This is especially important in projects involving ERP, WMS and B2B sales.

Do not build every feature at once

A company launching its first D2C store does not need, from the start, everything required for future sales in several markets.

Allow for growth in the architecture, but some features can be added later.

Use what Magento offers as standard

Custom solutions are justified when they meet a real business need.

If standard Magento or a proven extension already handles a process, building your own alternative does not always make sense.

Every additional modification can raise the later cost of maintenance and upgrades.

Clean up your data before the implementation

Correct SKUs, consistent product variants, unambiguous prices and clearly defined data sources reduce the risk of rework during the project.

This matters especially with larger catalogues and ERP and PIM integrations.

Look after documentation and code quality

Poorly built extensions and missing documentation can make the platform harder to develop.

If you change agency, the new vendor then has to spend more time understanding the existing solution.

Plan maintenance before the store launches

Know who will handle outages, updates and infrastructure before the first production order.

Taking over a store later without documentation, monitoring and agreed responsibilities can require extra work.