Help

Quick start

Beta and early access

Understand preview access, developing capabilities and how to propose a focused pilot.

If a feature is marked beta, early access or preview, check its limits before using it for a release or customer project. Access to one Maru feature does not automatically include every developing feature or download.

Read availability in context

Beta or early access means a workflow is being developed with users and may need guided setup. Preview means a capability is offered for evaluation with stated limits. Planned describes an intended direction that you should discuss with us before depending on it.

Check the product's release notes, the Apps directory, the options offered in your account and any agreed pilot scope. Those are the places to confirm the exact platform, download and access requirements. A guide describing a possible product is not a release announcement.

Opportunities to explore

Creators can discuss connected instruments, generative products and selling on Maru. Integration partners can explore game audio, website embeds and DAW integration projects.

There is no promised release date for every path. If your work depends on a particular download, host or selling feature, ask about that requirement before committing to it.

Ask for early access

Contact Maru with:

  • What you want people to make or hear.
  • The application, operating system or device where it should work.
  • Whether it needs sign-in, generation, private assets or paid access.
  • A small example we could evaluate together.

For a business integration, use teams and organizations to prepare the discussion.

Give actionable feedback

Include the product or project, version, environment, expected result and what happened. Keep a copy of important work, and remove credentials and private material from reports. Use support for a problem with an existing workflow.