All posts
Product4 min read

Shipping the Polaris SDK for JUCE

A licensing SDK that adds 40MB and a Rust toolchain to your plugin build is not a licensing SDK. It is a tax. Notes on shipping something small.

Plugin developers have a build tolerance close to zero, and they are right to. Your reverb does not need a package manager. So the constraint we set ourselves was simple: header, source file, no toolchain.

What integration looks like

Drop two files into your JUCE project, add your product key, and call validate on startup. That is the whole surface. There is no build step, no vendored dependency tree, and no linker archaeology when it breaks.

  • Two files, no external dependencies
  • Under 200KB compiled
  • Synchronous and async validation paths
  • Works offline against a cached entitlement

What we cut

We dropped the built-in UI entirely. Every vendor we spoke to had already designed their own activation dialog and resented ours. The SDK now returns state and lets you draw it.