Licenses and product access

If an installed plugin asks you to activate, approve the computer through Maru using the account that holds the product. Buying the product, activating a computer and letting an app access your account are separate steps. Your product license explains what you may do with it.

Buying and activating

For a release that uses Maru licensing, the customer starts activation from the plugin and approves it through Maru in their browser. The release's activation panel explains its state, available trial and device limits.

Maru-licensed releases need periodic online checks; activation is not indefinite offline access. If the plugin warns that you need to go online, connect so it can check the license. The plugin licensing guide explains the activation and offline states; your release's offer sets its trial and computer limits. Use purchases and downloads if the expected product is missing from an account.

Move to another computer

Open Plug-in activations to review the computers using your licenses. Choose Remove for a computer you no longer use, then activate the release on your new computer through its normal sign-in flow. Removing an activation frees that seat; the old installation stops at its next license check.

Revoking an access token or disconnecting an app does not perform this license-management step. Account security explains which control to use for each kind of access.

Creator choices

The supported beta licensing workflow lets a creator configure a native product's licensing, trial and seats, and arrange tester access. Release builds use the configured licensing flow; a development preview does not demonstrate customer activation.

Test with a representative release before distribution. The technical plugin licensing guide covers configuration and verification.

Generation is a separate permission

Owning an instrument does not automatically authorize it to spend the player's generation credits. The player approves that separately through the connected app flow.

Conversely, signing in to a creator app does not prove a purchase. Creator apps explains identity and admission, while generation and credits explains spending.

Refunds, access changes and support

Refunds, revoked tester access or changed permissions can affect later access checks. Follow the current Terms and refunds and the product's offer for the applicable rules.

If activation fails, confirm that you are using the account that acquired the product and review its available seats in Plug-in activations. If the problem persists, give support the product, release, operating system and visible activation state. Keep tokens and license secrets private. Creators preparing a paid release should also read selling on Maru.