Gorilla Compiler

Gorilla Compiler is the final stage of product creation. Once the sound core, application logic, interface, and assets are ready, Gorilla Compiler brings them together and creates the installers you can deliver to customers.

From a single product project, you select the formats you want to ship, including VST, VST3, Audio Unit (AU), AAX, and Standalone applications. Gorilla Compiler packages those formats with your .blob files, JavaScript code, UI assets, presets, license agreement, and other product resources into installers for macOS and Windows.

This is also where release requirements are applied. Gorilla Compiler handles code signing, installer signing, Apple notarization, and optional PACE signing or PACE copy protection as part of creating the finished product. Instead of treating these as disconnected post-build tasks, you configure them alongside the product that will be packaged and distributed.

Release Build Settings

Scaffolded projects and the Gorilla Engine React examples enable debugger support and a standalone application for rapid development. Review both settings before creating final installers.

Disable experimental debugger support for release builds. Set pluginConfig.experimentalDebuggerSupport to false in your .ugep file. Leaving debugger support enabled makes it easier to inspect and tamper with application code, including licensing logic, and retains an experimental development feature that can introduce stability risks. Disabling it reduces that exposure; it does not replace licensing or copy protection.

Strongly consider omitting Standalone from final installers unless it provides a clear customer benefit. Standalone is useful for rapid iteration, but for many DAW-focused instruments and effects it adds little value for end users. It also introduces a different class of support requests: audio-device and driver selection, MIDI-device configuration, latency, and troubleshooting outside a DAW. Manufacturers must maintain and support that additional application alongside their plugin formats.

To exclude it, uncheck Standalone under Plugin Settings > Plugin Formats, or set pluginConfig.buildStandalone to false in the .ugep file. Keep it enabled only when standalone use is an intentional, tested part of your product. Changing either setting requires rebuilding the product and its final installers. Editing the .ugep file does not change existing binaries. Install the rebuilt product when testing these release settings; existing installed development builds are not changed automatically.

Continue with the Gorilla Compiler User Guide to configure a project, select product formats and assets, set up signing and protection, and create your first installer.