How do I add a new project to my Hyvä license?
You can’t attach a second store to an existing paid Hyvä license. To add one, open Hyvä Licenses in the Hyvä Portal, click “Add a license”, and enter the new store’s domain. Before you create one, check whether your new project is already covered.
Quick Answer
In your hyva.io account, the “Add a license” button on the Hyvä Licenses page offers two routes. Enter the new domain for a free Hyvä Theme key, or buy Hyvä Commerce for paid features. Moving an existing store to a new domain uses “Edit domain” instead, and the credentials stay the same.
Paid Hyvä licenses (Hyvä Commerce, Hyvä Checkout, Hyvä Enterprise) cover one production Magento installation. That includes unlimited store views and same-business domains, plus staging and dev copies. As of October 2026, free Hyvä Theme keys go one per domain. Each account can hold up to 5, or 50 per Agency Partner group.
Does my existing Hyvä license cover a new project?
| Your situation | What to do |
|---|---|
| New store view or domain, same installation, same business | Nothing. Your existing license covers it. |
| Staging, UAT, or local dev copy | Nothing. Hyvä allows non-production use. |
| Same store moving to a new domain | Click “Edit domain”. Hyvä reviews it and emails you. |
| New installation or new client | New license, or a new free Hyvä Theme key. |
| Adobe Commerce store | Hyvä Enterprise, not Hyvä Commerce. |
Hyvä Theme has been free and open source since November 2025. One account can hold 5 free keys, or 50 per Agency Partner group, per the Hyvä Theme license FAQ.
Free Hyvä Theme keys come with a catch. The same FAQ lets Hyvä disable keys left unused for a long time, with no fixed period.
Multivendor, SaaS, or PaaS setups fall outside standard licensing. Hyvä asks you to contact them for custom terms.
How to add a new project in the Hyvä Portal
- Open Hyvä Licenses: Log in at hyva.io and go to the Hyvä Licenses page. If you joined an agency team on your own, verify your email first. Team features stay locked until you do.
- Click “Add a license”: Choose Hyvä Theme and enter the new project’s domain. A local domain like
hyva.testworks for development. Click “Get Hyvä Theme for free” to finish. For paid features, choose Hyvä Commerce instead. - Get the Composer credentials: Your new project’s Hyvä license key appears under the All Licenses tab. Click its domain name, then “Show Composer Credentials” to see the key and your packagist.com repository URL.
- Configure the new Magento project: Add the key and repository URL to the new Magento project’s Composer setup.
composer config --auth http-basic.hyva-themes.repo.packagist.com token yourLicenseKey
composer config repositories.private-packagist composer https://hyva-themes.repo.packagist.com/yourProjectName/Next, run composer require hyva-themes/magento2-default-theme and bin/magento setup:upgrade. Hyvä’s getting started guide covers child theme setup from there.
Portal labels checked October 2026.
Why Composer returns 401 or 403 for a Hyvä key
Don’t copy another client’s Hyvä Composer key into a new Magento project. Each key ties to a specific license, and Hyvä warns against committing it to any public repository. Composer errors like HTTP 401, 402, or 403 from hyva-themes.repo.packagist.com point to a key mismatch or an inactive subscription. The key in auth.json must match the project name in the repository URL, per the Hyvä POS install guide.
Can agencies transfer or trade in a Hyvä license?
Agencies can buy a Hyvä Commerce license for testing and transfer it to the client later. Only the license owner can transfer, renew, or change the domain. The Hyvä license agreement requires a separate license for each customer and bans reusing a production license for another store.
Hyvä Commerce trade-in credit, the cashback on a paid Hyvä Theme or Hyvä Checkout license, is narrower than a transfer. Per the Hyvä Commerce FAQ, trade-in credit only applies to the same merchant and domain that bought the original license. One client’s credit can’t fund another client’s upgrade.
In practice, register each new production store on its own key or license. Put it under the account of whoever will run the store long term. That keeps credentials separate and avoids a transfer at handover. If you’re planning a Hyvä rollout across several stores, our Hyvä development team can map licensing before the build starts. For background, see What is Hyvä and how does it work with Magento 2?
Related Answers
Was this answer helpful?
Your feedback helps us improve our answers.
Still need help?
Talk to our Hyvä experts
Setting up Hyvä across several stores or client projects? We can help you sort the licensing and get each install running cleanly.