# Developer concepts and documentation

> Find the technical guides for modules, integrations and agent workflows.

Canonical: https://maruaudio.com/help/developer-concepts
Documentation index: https://maruaudio.com/help/llms.txt

Use the developer documentation when you want to build a module, put an instrument in your application or connect generation to your service. Choose a guide below based on the experience you want to deliver.

## Projects, modules and releases

A **project** is editable work. A **module** defines an instrument, effect or musical tool, including its behavior and interface. A **release** is a prepared version for the destinations it supports.

Use [Start here](https://maruaudio.com/docs/start-here.md) for the technical orientation and [Quickstart](https://maruaudio.com/docs/quickstart.md) for a first local module. [Publishing](https://maruaudio.com/docs/publishing.md) covers release preparation.

## SDKs and interfaces

The [Audio SDK](https://maruaudio.com/docs/audio-sdk.md) defines audio module contracts. The [UI guide](https://maruaudio.com/docs/ui.md) covers interfaces and shared controls. Use them when you need to define an instrument's inputs, controls and interface.

## Agents and hosted services

Use [working with coding agents](https://maruaudio.com/docs/working-with-coding-agents.md) for source editing, [MCP](https://maruaudio.com/docs/mcp.md) for hosted tools and [generative features](https://maruaudio.com/docs/generative-features.md) for app integration.

For an event or webhook integration, read the [integration guide](https://maruaudio.com/docs/integrate-maru.md). If it does not document the event you need, [ask Maru](https://maruaudio.com/contact) before building around it. Include what should trigger the event, which system should receive it and what should happen if delivery fails.

## Start from the user's goal

| Product question | Help path | Technical continuation |
| --- | --- | --- |
| How do I make an instrument? | [Build an instrument or effect](https://maruaudio.com/help/building-instruments-and-effects.md) | [Local quickstart](https://maruaudio.com/docs/quickstart.md) |
| Can players connect their accounts and generate? | [Creator apps](https://maruaudio.com/help/creator-apps.md) and [generative products](https://maruaudio.com/help/generation-in-your-products.md) | [App generation integration](https://maruaudio.com/docs/generative-features.md) |
| Can I put it in my website or DAW? | [Web embeds](https://maruaudio.com/help/embed-audio-on-your-website.md) and [audio software makers](https://maruaudio.com/help/daw-and-audio-software-makers.md) | [Module player](https://maruaudio.com/docs/module-player-react.md) |
| Can I sell and maintain it? | [Marketplace preparation](https://maruaudio.com/help/selling-on-maru.md) | [Plugin licensing](https://maruaudio.com/docs/plugin-licensing.md) and [packaging releases](https://maruaudio.com/docs/packaging-and-releasing-plugins.md) |
| Can it run on a device? | [Hardware and controllers](https://maruaudio.com/help/hardware-and-controllers.md) | [Hardware platforms](https://maruaudio.com/docs/hardware-platforms.md) |

## Before committing to an integration

Confirm access to the tools and target host, and review the [toolkit's licensing terms](https://maruaudio.com/docs/licensing.md) before distributing a product. For an integration that needs custom access or delivery, [contact Maru](https://maruaudio.com/contact) with your application, target platforms and the interaction you want to build.

For everyday product use, return to [Help](https://maruaudio.com/help/welcome.md). For musical technique, use [Learn](https://maruaudio.com/learn).