| Languages and DSP | TypeScript module projectsGraph composition or restricted-TypeScript Processors, shared DSP leaves and React/TypeScript faces. Realtime restrictions and supported dependencies apply. | C++ frameworkC++ DSP and application code, with reusable audio, MIDI and interface modules. Web interfaces can use HTML, CSS and JavaScript. |
| VST3, AU and standalone | Existing macOS shell pathsVST3, AU v2 and standalone paths exist for supported modules. A generated shell is not a qualified release; exact artifact and host evidence must pass. Windows/Linux delivery is not generally qualified. | Upstream build targetsVST3, AU and standalone are documented targets. Platform SDKs and toolchains are required; AU is enabled on macOS. Test the actual product in each host. |
| CLAP and AAX | CLAP path; AAX unqualifiedA macOS CLAP shell exists with release-specific gates. AAX delivery is not qualified. Listing an existing AAX artifact does not add AAX export to the framework. | AAX upstream; CLAP extensionAAX is a JUCE target with a separate SDK and Avid licensing/signing prerequisites. CLAP uses the third-party, unofficial clap-juce-extensions; it is not JUCE-team support. |
| Web and browser preview | Module workbench and web ProgramsAudition supported modules with their shared face and JS/WASM Programs. Browser readiness does not establish native or hardware readiness, or create a web version of an arbitrary native plugin. | WebView interfaces in native appsJUCE documents web frontends inside an application or plugin. This embeds a browser UI; running the audio DSP on a public web page requires a separate runtime/build integration. |
| UI and saved state | Shared face contractUI-kit controls consume the module's parameter schema and host bindings. The product owns layout and DSP; hosts own devices, automation and state integration. | Native widgets or web frontendUse JUCE widgets and LookAndFeel, or a web frontend with parameter attachments. A web interface is already an option in JUCE. |
| Framework licensing and cost | Private-beta termsFramework redistribution and commercial permissions depend on written beta terms. The SDK and generated native shells are not generally open-source licensed. Check current terms before paying or committing a release. | AGPLv3 or JUCE licenceJUCE modules are dual-licensed. Commercial Starter is free within its eligibility limits; paid Indie/Pro plans have per-user prices and revenue/funding conditions. Read the version's licence and current plans. |
| Builds and signing | Shared project tooling, separate gatesBuild/export commands prepare supported outputs. Audio, state, format validation, signing, notarization and clean-machine delivery are separate release checks. Hosted builds are not part of the marketplace pilot. | CMake or ProjucerIntegrate platform toolchains and your release pipeline. JUCE documents custom post-build signing steps; a successful framework build does not complete product distribution. |
| Agent tooling and maturity | Project-aware operationsCLI, MCP and Studio reuse shared operations and module contracts. Selected preview, limited qualification and a developing ecosystem; no measured productivity advantage is established. | Source, examples and ecosystemJUCE provides source, examples, learning material and third-party modules. Coding agents can edit the project; this comparison does not establish a framework-specific agent success rate. |
| Distribution on Maru | Optional marketplace serviceFramework adoption and marketplace listing are separate choices. The first marketplace pilot is invite-only and free-first; paid selling, hosted builds and installer delivery come later. | Bring an existing built releaseThe marketplace pilot accepts third-party framework products for review without a port. Keep your release workflow; provide actual artifacts, rights and tested targets. Public publishing remains gated. |