All comparisons

JUCE and the Maru framework

Choose the foundation that fits your product. You can bring an existing built release to the Maru marketplace without changing frameworks.

Plugin frameworks

Choose around the work you need to ship.

Compare documented capabilities with the exact output you need. Maru is a developing framework in selected preview; a browser demo or successful compile alone does not qualify a plugin release.

Already on JUCE?

Keep your source, build system and existing GitHub release assets. The marketplace pilot reviews third-party products for distribution. It does not compile, port or generate a browser audition for an arbitrary native plugin. Public source sharing is optional; your licence obligations still apply.

Marketplace for developersPrepare a listing with your agent

Starting something new?

Try Maru for a module project with shared DSP, schema-bound controls, a live workbench and project-aware agent tools. If you need broad native platform coverage or an existing C++ product stack, assess JUCE first. Maru’s supported outputs and host acceptance remain specific to each module and release.

Explore the Maru framework
Maru and JUCE framework comparison, sources checked October 27, 2026
Your decisionMaruDeveloping framework · selected previewJUCEEstablished C++ framework
Languages and DSPTypeScript 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 standaloneExisting 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 AAXCLAP 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 previewModule 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 stateShared 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 costPrivate-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 signingShared 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 maturityProject-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 MaruOptional 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.

Sources checked October 27, 2026. Links beside each claim lead to the primary documentation or Maru’s current guidance. On small screens, scroll the table to compare both columns.

Other frameworks

iPlug2, DPF, nih-plug, Cmajor and other frameworks are in scope here for distribution of existing built releases only, subject to pilot admission and artifact review. This page does not compare their authoring features or promise that Maru can compile their source. A playable web build is a separate supplied artifact.

Prepare the release you already have.

The shared agent flow inspects your repository, validates listing metadata and previews an exact candidate before preparation or submission. The first pilot is invite-only and free-first; submission does not make a listing public.

Prompt for your coding agent
Inspect this repository and its existing binary release. Prepare a free Maru marketplace listing using the shared inspect_marketplace, validate_marketplace and preview_marketplace operations. Reuse our release workflow. Show the exact metadata diff, source exclusions, declared and actually tested targets, media origin and visibility before writing. Ask only unresolved identity, licence, source-access and update-policy questions. Keep source private unless I choose otherwise, and identify any required source obligations. Report missing checks as not-run. Submit only the exact candidate I review; retain product, release and review IDs.

Agent publishing is in private preview. Use the tooling version supplied for your pilot and follow its included maker guide.

Read the current marketplace pilot guide

Framework licensing and optional marketplace services are separate. Paid marketplace selling, hosted builds and installer delivery are later work. This is a documentation and implementation comparison, not a matched productivity benchmark or an endorsement by the named framework owners.