Link Search Menu Expand Document
Gorilla Engine
Table of contents

How to Release Your Products with Gorilla Compiler and Product Hub

This guide walks you through the end-to-end process of releasing an audio plugin product using Gorilla Compiler and Product Hub — from account setup to distributing your product to end users.

Note: Usage of Product Hub requires a signed add-on agreement with UJAM, which comes with additional costs. Please reach out to your UJAM contact for details.

1. Get Access

Before you can use Gorilla Compiler with Product Hub, you need an enabled account:

  1. Create an account at gorilla-engine.com if you haven’t already.
  2. Notify your UJAM contact which email address you used for your gorilla-engine.com account.
  3. Wait for confirmation that your account has been enabled for use with Gorilla Compiler and Product Hub.

Once confirmed, you can log in to Product Hub and Gorilla Compiler using the same credentials.

2. Create a Product in Product Hub

Before you can upload builds, you need to create a product entry in Product Hub:

  1. Log in to Product Hub.
  2. Navigate to Products and create a new product.
  3. Fill in the required product metadata
  4. Take note of the Product ID (UUID) — you will need this in Gorilla Compiler.

3. Configure Gorilla Compiler

Open your project in Gorilla Compiler and configure the Product Hub integration:

  1. Navigate to the Product Hub tab.
  2. Enter the Product ID you obtained from Product Hub in the previous step.
  3. Enable uploads to Product Hub so that builds are automatically uploaded when created.
  4. Enable Downloader Creation if desired — this is especially recommended when your products are very large, as it provides end users with a small downloader application instead of requiring them to download the full installer.

4. Build and Upload

With your project configured, use the Create Product workflow in Gorilla Compiler to build and upload:

  1. In Gorilla Compiler, go to the menu bar and click Create Product.
  2. Gorilla Compiler will:
    • Build the product
    • Create the platform installer (.dmg/.pkg for macOS, .exe for Windows)
    • Automatically upload the build to Product Hub (if uploads are enabled)
    • Generate a downloader (if Downloader Creation is enabled), placed in the same output directory as the installer
  3. Repeat this process on both macOS and Windows to create builds for both platforms.

CLI Alternative

For CI/CD pipelines, you can also build and upload via the command line:

gorilla-compiler \
  --project-file /path/to/your/project.ugep \
  --create-installer \
  --upload \
  --email <your-gorilla-engine-email> \
  --password <your-gorilla-engine-password> \
  --product-id <your-product-id> \
  --build-number <number>
  • --email / --password — Your gorilla-engine.com login credentials.
  • --build-number (-b) — Use this to pass the build number from your CI system (e.g. Jenkins BUILD_NUMBER). If omitted, Gorilla Compiler will automatically assign a build number one higher than the latest existing build of that product and platform in Product Hub.
  • --autorelease (-a) — Automatically create a release when builds for both platforms with the same build number are available.

5. Distribute Your Product

Once your builds are uploaded to Product Hub, you have two distribution options:

Option A: Without Downloader (Direct Distribution)

  1. In Product Hub, navigate to Products > Your Product > Builds.
  2. Click into the details of a build to see the download links for associated files.
  3. You can either:
    • Distribute the links directly to your users, or
    • Copy the files to your own hosting/download location.

Note on Windows installers: There is no way of preventing Windows installers from being split into multiple files if they grow large. To avoid end users having to download multiple files separately, consider zipping all installer parts together and distributing the zip from your own location.

Option B: With Downloader

The downloader is a small application that handles downloading and installing the full product for the end user. To use this approach:

  1. In Product Hub, navigate to Products > Your Product > Builds.
  2. Select one macOS build and one Windows build and create a Release from them.
  3. To make the release publicly available via the Product Hub API (which is a prerequisite for the downloader to work):
    • Navigate to Products > Your Product > Releases.
    • Click the edit icon on the release you want to publish.
    • Check the checkbox for the “Release” channel and save.
  4. The downloader application was placed in the same output directory as the installer by Gorilla Compiler. It should now be ready to use — test it by launching the downloader to verify the full download and installation flow works correctly.

Important: A release must always contain one build for each platform (one macOS build and one Windows build). There is no way of distributing your release

6. Optional: Integrate Licensing via Product Hub

If you want to use Product Hub not just for delivery but also for licensing (trial activation, license activation, subscription activation), you can integrate the Product Hub JavaScript client library (@gorilla-engine-sdk/ge-product-hub) into your plugin to provide your users with an email & password based product activation.

Note: The client library is hosted on UJAM’s internal package registry. You will need an access token to install it. Contact your UJAM representative to obtain the token and registry configuration.

For the full API reference, integration guide, and usage examples (activation, trials, subscription, license expiration, hardware fingerprinting), see the @gorilla-engine-sdk/ge-product-hub package documentation.