# DAWs and audio software makers

> Choose how to host Maru products, embed the Engine or add connected audio services.

Canonical: https://maruaudio.com/help/daw-and-audio-software-makers
Documentation index: https://maruaudio.com/help/llms.txt

For a DAW or audio-software maker, “compatible with Maru” can mean several things. Start by choosing the experience you want your users to have.

## Choose what to add

| Goal | Integration path | Your product supplies |
| --- | --- | --- |
| Load a released Maru plugin | Your existing support for the release's native format | Plugin scanning, audio and MIDI routing, state and automation |
| Include a Maru instrument or effect in your application | An Engine host integration for the selected modules | Audio timing, input/output, lifecycle, assets and UI context |
| Add sound generation or processing | A hosted-service integration with agreed account access | User interaction, account or service access and result handling |
| Let an assistant work with musical projects | The appropriate local or hosted operations | Clear permissions, project context and review of changes |

The first path may need no special Maru-specific format: compatibility is tested against the actual released plugin and your host. An Engine integration is a deeper product relationship, with its own distribution terms.

## Begin with one musical example

A browser DAW could evaluate one instrument driven by its MIDI track and transport. A desktop application could test one effect, its automation and session recall. An existing plugin maker could adapt one interface while preserving an agreed sound implementation.

Define which parts remain in your application and which Maru supplies. [Website integration](https://maruaudio.com/help/embed-audio-on-your-website.md) and [DAW usage](https://maruaudio.com/help/daw-integration.md) explain the two reader perspectives.

## Evaluate compatibility beyond playback

Check the target operating systems, sample rates and channel layouts, saved sessions, parameter automation, preset recall, device changes and expected performance. For connected features, also test account changes, service failures and retained assets.

Loading a demo is an early milestone. Before offering the integration to customers, agree which hosts and platforms you will test, who fixes problems and how updates reach users.

## Scope the partnership

Contact [Maru](https://maruaudio.com/contact) with your application, target operating systems, the interaction you want to add, licensing needs, release cycle and one representative project. Ask which parts are available for your host and which need a guided beta integration. Agree distribution rights and maintenance before including the Engine in a commercial product.

The [integration reference](https://maruaudio.com/docs/integrate-maru.md) provides technical entry points. [Teams and organizations](https://maruaudio.com/help/enterprise.md) covers commercial scope and [privacy and compliance](https://maruaudio.com/help/privacy-and-compliance.md) covers data requirements.