Licenses and installation

Every Magento 2 extension is a one-time purchase licensed for one production store at one production domain. There is no recurring fee to keep using it, and updates are included.

Staging, development and test copies of that store are included at no extra cost. Each additional production store or production domain needs its own license.

The details are in our License Agreement.

Yes. Without buying extra licenses, you may install the extension on:

• staging or testing subdomains of your production domain, for example staging.example.com when your store is example.com;
• local development machines reached through localhost or a local (private) IP address.

These copies may be used only to develop, test and stage the licensed store. They must not be open to the public as a live store or serve real customers.

Each license key is bound to one production domain and can be activated once. After activation, it works only on that domain and on the development copies that belong to it.

Please do not bypass or change the license check, and do not use a key on a domain other than the one it was issued for.

If you need to move an extension to a different domain, for example after a rebrand or a platform migration, contact us. We may rebind the license key once the extension is no longer used on the original domain.

You can install an extension in two ways:

• download the ZIP file under My Account › My Downloadable Products, or
• install it from our private Composer repository, using Composer access keys you generate in your account.

Installation, configuration and customization are not part of the license. If you would like our engineers to do them, they are available through our support plans.

Composer access keys let you install the extensions you bought from our private Composer repository. You generate them in your account.

• Keep them confidential: do not commit them to public repositories or share them outside your team and the developers working on your licensed store.
• You can bind a key to a licensed domain, and we recommend that you do.
• We log each Composer download (package, version, IP address and time) to protect the repository.
• If a key appears to have been leaked or shared, we may reset it and will let you know.

Yes. Agencies and freelance developers may buy licenses for their clients' stores. The license then belongs to the client's production store: the agency passes the extension and the License Agreement on to the client and must not reuse the license key for another store.

Yes, for example when the business is sold, provided that:

• you tell us in writing beforehand;
• the new owner accepts the License Agreement; and
• you stop using the extension and delete all copies under your control.

Licenses cannot be transferred in any other way.

Yes. You may modify the source code for use on your own licensed store, for example to adapt it to your theme or business rules. The modified extension remains under the License Agreement.

Updates may overwrite changes made directly in the extension's files, so we recommend keeping your changes in a separate module or theme. We are not responsible for problems caused by modifications.