Publish a plugin

Made with any framework. Tell Maru what you have and it takes you through one flow to a product page with your releases.

What do you have?

I have the source code

Let Maru build your project

Upload a folder or zip, or connect a GitHub repository. Maru builds it for macOS, Windows and Linux, runs health checks on every bundle, signs it after review and publishes it. NIH-plug and DPF projects build today.

I already build it

List the releases you build

Keep building in your own CI or by hand and attach the files to GitHub releases. Maru lists them under your name and Maru Desktop installs them. JUCE plugins publish this way for now.

I made it with Maru

Publish a Maru module

Publish from Studio or run maru publish in the project. It plays on its page in the browser, and Maru builds the native plugins from the same source.

What each route gives you

Maru builds your projectYour own releasesMaru module
Who builds itMaru, from your sourceYou, in your CIMaru, from your source
FrameworksNIH-plug, DPFAny, including JUCEMaru
SigningMaru signs after review; no developer account neededYou sign, or ship unsignedMaru signs
Health checksOn every buildLocally with maru plugin checkOn every build
Install with Maru DesktopYesYes, from zip releasesYes
Plays in the browserMeasured previewsNoYes

Every route ends on a product page with your releases, and every listing is free to publish. To sell a plugin built elsewhere, prepare a marketplace draft for review.

Publish from your coding agent

Claude Code, Codex or any MCP client can do all of this from the terminal with the maru CLI: detect the framework, build, read the health checks and publish a release. Paste these steps into your agent in the project folder.