Prepare your product

Understand what's necessary to bring your products to MuseHub

Publishing on MuseHub is a great opportunity to reach new customers and grow your product. There are some simple no-code steps required in order to ensure your product is compatible with the MuseHub platform, and can be delivered in seamless, secure way to the customer.

Content Guidelines

Please ensure your product meets the platform's content guidelines. This is to ensure a safe and secure environment for customers.

This means checking your code for viruses and ensuring there is no harmful content inside. Apps and plug-ins have additional requirements, such as ensuring the product doesn't open to a login screen or have a custom DRM solution. Additionally, the finished app or plug-in should be code-signed and/or notarized with your developer credentials.

Prepare your code

MuseHub operates as a custom licensing platform to ensure a smooth and consistent experience. The process of creating a Hub compatible version is straightforward:

• Start with an open/OEM version of your software; a binary free from other DRM solutions (serial licenses, dongles, activation codes etc) which opens directly.

• Ensure the product doesn't open to a login or license screen.

• If your application or plugin needs a user account (e.g., for cloud processing), use the MuseSDK to integrate directly with MuseHub. This allows your product to return a user ID for the MuseHub customer and supports seamless account creation on your backend.

MuseHub Developer Utility

If you have a paid product, you must run the MuseHub Developer utility to wrap your build with Muse DRM; this enables the Hub platform to function. The DRM service is provided as an easy "no code" way to enable compatibility with the commercial business models of MuseHub, and does not apply to free products. Once run, the service will return protected versions of your products, along with an ID key that you'll enter alongside the product binary when you upload it to the Partner Portal.

Codesign and notarise

Once the Muse DRM service has returned the protected version of your products, you must codesign and notarise your applicatoin using your developer credentials; this includes using your Apple Developer account credentials/certificates on macOS, and signing with a trusted certificate on Windows.

Build installers

With these Hub-compatible versions of the software, you can now build your installers as usual. If you're distributing just .vst3, .component, or .aax plugins, you can upload the wrapped and signed binaries directly to the Partner Portal. If you're including other dependencies, then you can use an installer. The installer will run silently on macOS 13+ and above, and for recognized installer types on Windows, so don't include any custom steps or things that might interfere with the silent install process.