# Publishing plugins

> Prepare an instrument or effect so other people understand and can use it.

Canonical: https://maruaudio.com/help/publishing-plugins
Documentation index: https://maruaudio.com/help/llms.txt

To release an instrument or effect, prepare the version people will actually use: its controls, presets, required sounds and downloads for the intended host. Publishing and paid delivery can require guided early-access steps; saving a project does not put it on sale.

## Describe the musical result

Give the tool a clear name and description. Explain its inputs, a useful first preset and where it fits in a musician's workflow. Use artwork and examples that represent the real product.

Keep a record of the source and permissions for recordings, samples, code and other dependencies. Publication is not permission to redistribute someone else's material.

## Check the delivered product

Install the release in the DAW and operating system you plan to offer. Play its presets, move the controls, save a session and reopen it to check that the sound and required assets return.

[DAW integration](https://maruaudio.com/help/daw-integration.md) explains what a musician needs to check. [Exports](https://maruaudio.com/help/exporting-your-work.md) distinguishes native builds from banks and audio files.

## Prepare the publication

Prepare a saved revision, a description and demo, asset permissions, and the operating systems and hosts you intend to support. If your account does not offer the release step you need, include those details when you contact Maru for early-access publishing help.

For the technical release process, read [Publishing](https://maruaudio.com/docs/publishing.md). Return to [publishing and exports](https://maruaudio.com/help/publishing-and-exports.md) when deciding what to share, and [contact Maru](https://maruaudio.com/contact#help) when a required delivery step is unavailable.

## Decide how people get access

Decide whether people should play the product online, copy its editable source, download a build or activate a licensed installation. Explain exactly what they receive. [Licenses and product access](https://maruaudio.com/help/licenses-and-product-access.md) explains customer activation and paid access.

If the instrument connects to generation, explain its account requirements and who pays for each request. [Generation in your products](https://maruaudio.com/help/generation-in-your-products.md) covers destination-specific limits.

## Launch and maintain

Use [selling on Maru](https://maruaudio.com/help/selling-on-maru.md) to prepare a commercial beta release. Plan a support route, preserve the source behind the release and explain where updates will appear. [Maintaining your products](https://maruaudio.com/help/maintaining-your-products.md) covers the ongoing work.