AURORA ONE – a Magento 2 build with Hyvä at a fixed price
A new store built to a prepared standard: one market, one language version, a Hyvä frontend, Magento 2 configuration and a clearly described starting scope. Before the offer we review your processes, data and required integrations.
- Magento 2
- Hyvä frontend
- one market
- one language version
- fixed price
A Magento 2 build with Hyvä for PLN 39,000 net
An MVP foundation you can develop freely later on: a fixed scope, one market and a price you know before the contract is signed.
- PLN 39,000
- The price of the standard implementation scope, net.
- 1–3 months
- The delivery plan depends on qualification, materials and team availability.
- 1 market
- One language version and one main currency in the starting configuration.
- 10 hours
- Support and an SLA in the first month after launch.
AURORA ONE fits a project that can be closed within a prepared standard
A fixed price requires clearly defined boundaries. We establish them before the contract is drafted, so additional requirements don't surface halfway through the build.
| Your situation | The right path |
|---|---|
| You are launching a B2C or D2C store on a single market | AURORA ONE |
| You start with one language version and one main currency | AURORA ONE |
| Your brand identity can be applied to the prepared Hyvä component system | AURORA ONE |
| You need the standard Magento 2 selling features | AURORA ONE |
| The data scope covers products and customers, without order history | AURORA ONE |
| Extensive integrations are not a condition of the first launch | AURORA ONE |
| You accept a fixed scope of views and starting features | AURORA ONE |
| You need multiple markets and language versions | AURORA CROSS |
| You sell B2B or combine B2C with B2B | B2B implementationB2C + B2B implementation |
| You want a bespoke UX and a frontend designed from scratch | D2C implementation on Magento 2 |
| You face a complex migration of data, SEO and integrations | Migration to Magento 2 |
You are launching a B2C or D2C store on a single market
The right path
AURORA ONEYou start with one language version and one main currency
The right path
AURORA ONEYour brand identity can be applied to the prepared Hyvä component system
The right path
AURORA ONEYou need the standard Magento 2 selling features
The right path
AURORA ONEThe data scope covers products and customers, without order history
The right path
AURORA ONEExtensive integrations are not a condition of the first launch
The right path
AURORA ONEYou accept a fixed scope of views and starting features
The right path
AURORA ONEYou want a bespoke UX and a frontend designed from scratch
The right path
D2C implementation on Magento 2If a project goes beyond the standard, we analyse the needs and price the additional scope. You know upfront what the whole thing will cost, and we deliver the extra elements either after the basic scope goes live or straight away, depending on what we agree.
A fixed scope shortens the build, because the core decisions are prepared up front
The project doesn't start by defining the whole architecture and designing every element from a blank page. AURORA ONE uses a prepared Magento 2 configuration, Hyvä UI components, design rules and a launch checklist.
Decisions about the catalogue, communication, brand identity, payments, shipping and data are still needed. There are simply fewer of them than in a dedicated build.
The price stays fixed as long as the requirements fit the described model. Needs beyond the standard are identified during qualification and moved to a separate quote.
See what the standard covers- 01
Magento 2 foundation
Configuration of the store, catalogue, sales, users and orders.
- 02
Hyvä frontend
Prepared components, responsive views and a consistent frontend layer.
- 03
AURORA ONE standard
The scope of features, configuration, testing and the launch process.
- 04
Client brand
Typography, colours, content, photography, banners and catalogue configuration.
What is Hyvä in Magento 2, and why do we build AURORA ONE on it?
Hyvä is a frontend for Magento 2 — the layer your customer sees. It replaces the platform's default theme with lighter code and a library of ready components. In AURORA ONE, the whole repeatable implementation scope stands on it.
Magento 2's default frontend builds the interface on an extensive JavaScript layer that has to be worked around with every change to the look. Hyvä replaces it with a simpler set of tools: Tailwind CSS and Alpine.js instead of RequireJS and Knockout. The backend stays the same — catalogue, prices, cart, orders and integrations work exactly as before; what changes is how the customer-facing layer is built.
A fixed price needs a layer that can be assembled once and reused on the next project. Hyvä UI components give us that base: the designer does not draw every view from a blank page, but sets typography, colours, the grid and the way products are presented to match your brand identity, while the structure of the components stays standard. That is where a scope you can price before the work starts comes from.
See a case study of a Magento 2 store with HyväWhat Hyvä gives an AURORA ONE build
- a repeatable frontend scope that can be priced before the start,
- a look matched to your brand without working around the default theme,
- a lighter frontend and less code to maintain after launch,
- a lower cost for later work on the customer-facing layer.
Hyvä Bronze Partner
Aurora Creation is an official Hyvä partner at Bronze level. Every AURORA ONE build runs on this frontend, and we use it to rebuild the presentation layer of live Magento 2 stores.
What does a Magento 2 build with Hyvä cover in AURORA ONE?
The full implementation scope goes into an annex to the offer and the contract. Before signing we confirm the features, the limits and the responsibilities of both sides.
Magento 2 and the Hyvä frontend
- Magento 2 installation and configuration,
- a frontend based on Hyvä,
- use of Hyvä UI components,
- component styling aligned with your brand identity,
- responsiveness of the core views,
- a test environment and code versioning.
Single-market configuration
- one language version,
- one main currency,
- tax and VAT rate configuration,
- users and admin roles,
- order statuses,
- attributes and the basic product structure,
- system and transactional messages.
Store data
- transfer of products together with descriptions, attributes and media,
- transfer of customer accounts,
- data validation after import,
- order history stays outside the standard scope.
The volume of products, customers, attributes and media is confirmed during project qualification.
Design and core views
- global styles and a basic styleguide,
- home page,
- product listing,
- product page,
- cart and checkout elements,
- launch banners for the home page,
- desktop and mobile views.
The number of launch banners and the scope of work on the cart and checkout are confirmed in the scope document.
Search and product presentation
- ElasticSuite search,
- suggestions as the query is typed,
- typo handling within the range offered by the tool's configuration,
- filtering by attributes,
- ordering and product promotion rules,
- “New”, “Sale” and “Bestseller” labels.
Analytics and marketing elements
- Google Tag Manager configuration,
- Google Analytics 4 configuration,
- a consent management mechanism compliant with Consent Mode v2,
- a product feed,
- a blog module,
- static terms and privacy policy pages based on materials supplied by the client.
Product feed formats are agreed before the project starts.
Testing and launch
- testing of the core purchase paths,
- verification of views on the agreed devices and browsers,
- production deployment,
- post-launch monitoring,
- 10 hours of support and an SLA in the first month.
The parameters of the starting SLA are confirmed in the contract.
- Magento 2 installation and configuration,
- a frontend based on Hyvä,
- use of Hyvä UI components,
- component styling aligned with your brand identity,
- responsiveness of the core views,
- a test environment and code versioning.
- one language version,
- one main currency,
- tax and VAT rate configuration,
- users and admin roles,
- order statuses,
- attributes and the basic product structure,
- system and transactional messages.
- transfer of products together with descriptions, attributes and media,
- transfer of customer accounts,
- data validation after import,
- order history stays outside the standard scope.
The volume of products, customers, attributes and media is confirmed during project qualification.
- global styles and a basic styleguide,
- home page,
- product listing,
- product page,
- cart and checkout elements,
- launch banners for the home page,
- desktop and mobile views.
The number of launch banners and the scope of work on the cart and checkout are confirmed in the scope document.
- ElasticSuite search,
- suggestions as the query is typed,
- typo handling within the range offered by the tool's configuration,
- filtering by attributes,
- ordering and product promotion rules,
- “New”, “Sale” and “Bestseller” labels.
- Google Tag Manager configuration,
- Google Analytics 4 configuration,
- a consent management mechanism compliant with Consent Mode v2,
- a product feed,
- a blog module,
- static terms and privacy policy pages based on materials supplied by the client.
Product feed formats are agreed before the project starts.
- testing of the core purchase paths,
- verification of views on the agreed devices and browsers,
- production deployment,
- post-launch monitoring,
- 10 hours of support and an SLA in the first month.
The parameters of the starting SLA are confirmed in the contract.
Handled separately, outside the implementation scope:
The price stays fixed when the project fits the described standard
Requirements outside the scope should not appear as unexpected surcharges halfway through the project. We establish them during qualification and point to the right way of delivering them.
| Need | How it is handled | The right path |
|---|---|---|
| A bespoke UX and every view designed from scratch | Separate analysis and quote | D2C implementation on Magento 2 |
| Sales to business customers, credit limits, account managers and B2B price lists | A B2B process design | B2B implementationB2C + B2B implementation |
| Several countries, languages, currencies and pricing policies | An expansion and localisation plan | AURORA CROSS |
| Extensive ERP, PIM, WMS or CRM integrations | Data flow analysis and integration | Dedicated Magento 2 implementations |
| Custom modules and a non-standard checkout | A separate specification | Dedicated Magento 2 implementations |
| Server, administration and infrastructure monitoring | A separate service | Magento 2 hosting |
| Maintenance, incident response and an SLA after the starting period | Ongoing care | AURORA CARE |
| Planned feature development after launch | Separate tasks priced before delivery | AURORA EVOLUTION |
Need
A bespoke UX and every view designed from scratch
How it is handled
Separate analysis and quote
The right path
D2C implementation on Magento 2Need
Sales to business customers, credit limits, account managers and B2B price lists
How it is handled
A B2B process design
The right path
B2B implementationB2C + B2B implementationNeed
Several countries, languages, currencies and pricing policies
How it is handled
An expansion and localisation plan
The right path
AURORA CROSSNeed
Extensive ERP, PIM, WMS or CRM integrations
How it is handled
Data flow analysis and integration
The right path
Dedicated Magento 2 implementationsNeed
Custom modules and a non-standard checkout
How it is handled
A separate specification
The right path
Dedicated Magento 2 implementationsNeed
Server, administration and infrastructure monitoring
How it is handled
A separate service
The right path
Magento 2 hostingNeed
Maintenance, incident response and an SLA after the starting period
How it is handled
Ongoing care
The right path
AURORA CARENeed
Planned feature development after launch
How it is handled
Separate tasks priced before delivery
The right path
AURORA EVOLUTIONPrepared components shorten the work, and your brand gives them their character
AURORA ONE does not require designing the whole frontend from scratch. The designer works on a prepared component system and adapts its visual layer to your company's identity.
Typography, colours, photography, content layout, banners and the way products are presented all change. The structure of the key components stays aligned with the AURORA ONE standard.
This model limits the amount of code written for a single project only. Further Magento features can be developed after launch, but every change should respect the architecture used in the starting variant.
Home page
Mobile search
Product listing
Product page
What gets adapted
- styling aligned with your brand identity
- responsive views
- a consistent component system
- the ability to edit selected content in the admin
- store development after launch
The project moves through five clearly described stages
Each stage ends with a decision or a document, so it is clear what has been agreed and what is still to be confirmed.
- 01
Qualification
We review the sales model, the number of markets, the data, the frontend scope and the required integrations. The outcome is a decision on whether the project fits AURORA ONE.
Aurora Creation
- Analysis of requirements and data
- A decision on the fit with the standard
On your side
- Information about the current store
- A list of required integrations
- 02
Scope confirmation
The scope, exclusions, responsibilities of both sides and the terms for changing the arrangements go into the offer and the contract. You know which materials you need to hand over before the next stage begins.
Aurora Creation
- A scope and exclusions document
- The offer and the schedule
On your side
- Scope approval
- Confirmation of the materials list
- 03
Brand adaptation
We agree the styles, content, home page structure and the way products are presented. The design is built on the components available in the standard.
Aurora Creation
- A styleguide and component styling
- The home page layout
On your side
- Brand identity and photography
- Content and launch banners
- 04
Configuration and build
We configure Magento 2, the Hyvä frontend, the catalogue, payments, shipping, data and the remaining elements included in the approved scope.
Aurora Creation
- Magento 2 and Hyvä configuration
- Data import and validation
On your side
- Product and customer data
- Accounts with payment and shipping providers
- 05
Testing and launch
The store goes through testing of the agreed paths. After approval it goes into production, followed by the starting support period.
Aurora Creation
- Purchase path testing
- Production deployment and post-launch monitoring
On your side
- Sign-off on the agreed paths
- The decision to go live
PLN 39,000 net for the standard AURORA ONE scope
The price covers the elements described on this page and confirmed in the project documentation. Needs outside the scope are identified before the contract is signed.
PLN 39,000net
The price of the standard scope of a Magento 2 build with a Hyvä frontend.
- Payment
- The fee can be paid in tranches or spread into instalments, whichever you prefer:
- 4 × PLN 9,750 net
- 12 × PLN 3,800 net
- Planned delivery time
- 1–3 months from meeting the project start conditions and handing over the required materials. The exact date is confirmed after qualification.
- Post-launch support
- 10 hours of support and an SLA in the first month after going live.
- Scope changes
- A new requirement is first described and priced. Delivery starts once you approve the change.
Maintenance, development and expansion have their own terms of cooperation
AURORA CARE
Monitoring, incident response, security and an SLA once the starting period ends.
Explore AURORA CAREAURORA EVOLUTION
Planned development of a live Magento 2 store. Every task gets a scope and a price before delivery starts.
Explore AURORA EVOLUTIONAURORA CROSS
Extending sales to further countries, language versions and local requirements.
Explore AURORA CROSSMagento 2 hosting
Infrastructure matched to load and integrations, with a clear split of responsibility for the server.
Check Magento 2 hostingFAQ — a Magento 2 build with Hyvä
AURORA ONE is a Magento 2 store implementation with a Hyvä frontend, delivered in a prepared and fixed scope. The model is intended for projects whose requirements fit a standard covering one market and one language version. The features of the platform itself — catalogue, cart, orders and the admin panel — can be checked in the Magento 2 demo.
Hyvä is a frontend for Magento 2 — the layer your customer sees. It replaces the platform's default theme with lighter code: Tailwind CSS and Alpine.js instead of an extensive JavaScript layer. The Magento backend stays untouched: catalogue, prices, cart, orders and integrations work the same. Aurora Creation is an official Hyvä partner at Bronze level and builds every AURORA ONE implementation on this frontend.
The standard AURORA ONE scope costs PLN 39,000 net and includes the Hyvä licence. The fee can be spread over 4 tranches of PLN 9,750 net or 12 instalments of PLN 3,800 net. Requirements beyond that scope are identified during qualification and need a separate quote.
Magento 2 installation and configuration, a Hyvä frontend styled to your brand identity, configuration of one market with one language version and one currency, the transfer of products and customer accounts, the core store views, ElasticSuite search, analytics with Google Tag Manager and GA4, testing of the purchase paths, production deployment, and 10 hours of support with an SLA in the first month. The full list, exclusions included, is set out in the implementation scope on this page.
Yes. The cost of the Hyvä licence sits inside the PLN 39,000 net price for the standard AURORA ONE scope and is not charged separately.
The current assumption is 1–3 months. The timeline depends on team availability, the readiness of your data and materials, and how quickly decisions are made on your side.
The frontend uses prepared Hyvä UI components that are adapted to your brand identity. The amount of bespoke design work is smaller than in a dedicated implementation.
The standard can cover moving products and customer accounts. Order history, extensive data mapping, SEO redirects and rebuilding integrations require a migration project under Migration to Magento 2.
No. The server, its administration and monitoring are a separate service, because infrastructure is matched to the catalogue, the traffic and the integrations of a specific store. The scope is described under Magento 2 hosting, and we confirm the environment the store will run on before the project starts.
Extensive integrations are not part of the currently described standard. Their scope is analysed separately before an offer is presented.
Such projects need broader analysis. B2B sales are covered by the B2B implementation and B2C + B2B services. Expansion into further markets is handled by AURORA CROSS.
Yes. Hyvä changes the presentation layer, not the Magento 2 backend, so further features and integrations are delivered exactly as they would be on the default theme. Modules written only for that theme need adapting to Hyvä — we check that when pricing a specific task. Subsequent tasks can be delivered under AURORA EVOLUTION, while maintenance and incident response are covered by AURORA CARE.
Let's check whether AURORA ONE fits your project
Send us the basics about your current store, the planned market, your data and integrations. On that basis we'll assess whether the requirements fit the AURORA ONE standard or whether a broader implementation variant is needed.
