Skip to content
DOCS

Cloud builds

Build signed macOS and Windows versions of your plugin in the Freqlab cloud, with licensing if you sell it.

A cloud build makes your plugin for macOS and Windows on Freqlab's build machines, signs and notarizes it with your credentials, checks it against the Freqlab Standard, and gives you the files to download or release.

You need to be signed in and have cloud build credits. Each platform costs one credit, except on plans with unlimited builds.

Start a cloud buildLink to this section

  1. Build the project in Studio first. A cloud build won't start until the current version has a local build, which catches most errors before they cost a credit.
  2. Click the cloud button (Cloud Build & Distribute) at the top of the window.
  3. On Submit, choose the Project, and the Distribution Product it's for (or No Licensing).
  4. Under Build Targets, check the Platforms (macOS, Windows) and Formats: VST3 and CLAP, plus AU for JUCE and iPlug2 (AU needs macOS checked).
  5. Under Signing Credentials, pick the credentials for each platform, or None.
  6. Click the build button, which shows the platforms and cost (for example Build for macOS + Windows · 2 credits). You can close the window: the build keeps going.

Studio remembers your choices per project for next time.

OptionsLink to this section

OptionWhat it does
Include .env filesUploads your .env files. Only check it if your build needs them
Skip the Freqlab Standard check (faster, for testing)Skips validation. freqlab.co won't list these files. Never remembered

LicensingLink to this section

After you pick a product with licensing turned on in Distro, the Licensing section has Apply license enforcement, on by default. It builds licensing into the plugin. With it on, Studio checks your project references the licensing SDK, and warns if it's pinned to an old version or a branch. Fix it, or check Ignore this warning and build anyway.

SigningLink to this section

Signed plugins open without security warnings: Apple notarizes signed macOS builds, and Windows trusts builds signed with Azure Artifact Signing. Add your Apple and Windows signing credentials at creator.freqlab.co (Manage Credentials). Without them the build still works, but macOS blocks the plugin until the user allows it, and Windows shows a warning.

What's uploadedLink to this section

Your project folder, as a zip within your plan's limit (10 MB on the free plan). Build output, .git, node_modules, caches and agent folders are always left out, and so are .env files unless you check Include .env files. Leave out more in Project Settings, Cloud Build.

CreditsLink to this section

The footer shows the cost and your balance. Buy Credits opens your billing page; your plan's credits are listed in Settings, Cloud. Builds that fail on Freqlab's side are always refunded. Some plans also refund a few code or signing failures each billing period (Settings, Cloud).