# Maru for teams and organizations

> Find a practical integration path for audio companies, creative platforms, publishers and research partners.

Canonical: https://maruaudio.com/help/enterprise
Documentation index: https://maruaudio.com/help/llms.txt

Contact Maru to discuss an integration, artist product, audio workflow or research project for your organization. Access, delivery, pricing and support are agreed for the project; an individual account does not include a custom deployment or organization-wide service commitment.

## Find your use case

- [DAWs and audio software makers](https://maruaudio.com/help/daw-and-audio-software-makers.md): host released plugins, embed musical tools or add connected services.
- [Creative platforms, publishers and education](https://maruaudio.com/help/creative-platforms-and-education.md): make content playable, support a lesson or develop an artist product.
- [Game audio and creative tools](https://maruaudio.com/help/game-audio-and-creative-tools.md): evaluate effects and sound workflows in Unity, Unreal or TouchDesigner.
- [Controllers and hardware](https://maruaudio.com/help/hardware-and-controllers.md): explore one instrument or effect on a specific physical setup.
- [Research and custom projects](https://maruaudio.com/help/research-and-custom-projects.md): investigate an audio question with an agreed prototype, evaluation or product outcome.

## Define a first project

Describe your current workflow, intended users and destination: a browser application, a DAW, an existing plugin line or another environment. Describe what would make the project worth adopting: for example, recalling an effect correctly in your DAW's saved sessions or letting students keep the sounds they make in a lesson.

[Apps and integrations](https://maruaudio.com/help/apps-and-integrations.md) explains the main connection points. The [Engine overview](https://maruaudio.com/engine) introduces the technical foundation.

## Discuss access and delivery

Send [Maru](https://maruaudio.com/contact) a brief with your intended users, target application or device, example project, desired timing and needs for account access, content ownership, deployment, support and purchasing. Discuss requirements such as single sign-on, data location, procurement documents and service commitments before choosing a setup.

These are requirements to agree, not features automatically included with an individual account. Identify who maintains the integration, how users get help and what happens when an online service is unavailable. A pilot should specify a useful result and how both sides will evaluate it.

Use [billing and usage](https://maruaudio.com/help/billing-and-usage.md) for individual account questions. Ask for an offer covering your organization's users, usage, delivery and support needs.

## Review data requirements early

Identify what recordings, project material and account data the work would involve. [Privacy and compliance](https://maruaudio.com/help/privacy-and-compliance.md) points to the current policy and a route for questions. Resolve requirements before submitting confidential material or committing to an integration.