Skip to content
DOCS

Cloud builds

Build signed macOS and Windows versions in the Freqlab cloud, check their results, download them and release them.

A cloud build makes your plugin for macOS and Windows on Freqlab's build machines, signs and notarizes it with your credentials, and checks it against the Freqlab Standard (pluginval and clap-validator; warnings still pass). You need to be signed in and have cloud build credits. Each platform costs one credit, except on plans with unlimited builds. Builds that fail on Freqlab's side are always refunded.

Start oneLink to this section

  1. Build the project locally first. A cloud build won't start without a local build, which catches most errors before they cost a credit.
  2. Click Cloud Build on the project's row.
  3. On Submit, pick the product it's for (Select a product…), or No Licensing.
  4. Check the Platforms and Formats: VST3 and CLAP, plus AU for JUCE and iPlug2 (AU needs macOS checked).
  5. Pick your Signing Credentials for each platform, or None.
  6. Click the build button, which shows the cost. You can close the window: the build keeps going.
OptionWhat it does
Include .env filesUploads your .env files, only if your build needs them
Skip the Freqlab Standard check (faster, for testing)Skips validation. freqlab.co won't list these files
Apply license enforcementBuilds licensing into the plugin. Shown under Licensing after you pick a product with licensing turned on. Express warns if your project doesn't reference the licensing SDK, or pins an old version or a branch: fix it, or check Ignore this warning and build anyway

Your project is uploaded as a zip within your plan's limit (10 MB on the free plan). Build output, .git and node_modules are left out, plus your Cloud excludes, and .env files unless you check Include .env files. Add signing credentials at creator.freqlab.co. Without them the build still works, but macOS blocks the plugin until the user allows it, and Windows shows a warning.

ResultsLink to this section

Status shows builds In Progress and the History. Notarization usually takes 2 to 5 minutes, or hours for a new developer account. Cancel refunds platforms that haven't started.

Each finished platform shows Signed and Notarized, Licensed or Not licensed, and Validation Details with its Freqlab Standard results. Partly notarized means some formats weren't notarized, so macOS blocks those on other Macs until the user allows them. Not licensed means no @freqlab:require-license tag was found: add one and build again.

If it failedWhat to do
Compile ErrorFix the code, then build again
Signing ErrorCheck your signing credentials, then build again
System ErrorBuilding again usually works
Blocked by Security ScanThe scan flagged the build, so its files aren't available

Download and releaseLink to this section

Click a format to download it, or Download All. Files save to Downloads/Freqlab/<project>/<version>/<platform>/; change the folder in Settings, Cloud. Builds are kept 30 days (failed ones for 7), and your 3 newest builds of each project are always kept.

Build Again (on failed, canceled, partly notarized or expired builds) fills in Submit with that build's settings, to check and send again. Distribute on a completed build lets you pick New Product or Add to Existing Product, then opens Freqlab Distro.