Apps and integrations
Embed instruments, effects and racks
Put a playable example on your site or plan an integrated musical experience.
Use a module's Embed option to put its player on your website when that option is available. If you want an effect to process your site's audio, or an instrument to follow your sequencer, you need a developer integration instead.
Embed an available player
On a module page, open the ⋮ menu and choose Embed this module. Copy the iframe code into your website’s HTML or embed block. The dialog also offers a direct player URL and a link to this guide.
A creator module needs a saved revision and public or unlisted visibility. A private module cannot play in an embed. Use a site that permits embedded content.
If you own the module, the dialog also offers Use in a web app and Explore game audio. These lead to hosting and integration guides for reusing the module’s DSP and connecting its controls to your project. Native and game-engine support depends on the module and target.
Try the published page as a visitor. Confirm that the player loads, its controls fit on smaller screens and the person can start audio. The site builder's embedding rules and browser permissions can affect playback.
An effect needs an input source. An instrument needs notes or a sequence. Include enough context for the visitor to hear the intended result, with playback help nearby when useful.
Connect audio inside your application
If the effect needs to process your application's audio, or an instrument must follow your transport and MIDI, a developer integration is the appropriate path. Your application supplies the audio, timing, devices and resource access; the module supplies its musical behavior.
The module player reference explains how to host a module. An independent embedded player does not automatically process audio from its surrounding page.
Plan a rack experience
A rack can combine an instrument, MIDI tools and effects into one playable setup. It needs a shared host to manage connections, saved settings and assets. Several unrelated embeds do not become a connected rack.
Use the available rack workflows, and contact Maru for an early-access rack embed or custom player. A module's Embed snippet cannot export a whole connected rack. In your request, include the modules, their connections, where settings should be saved and whether visitors need to sign in.
Account access and commercial use
Embedding a player does not grant private content access, a product license or generation spending permission. Explain any sign-in requirement and use creator-app consent when connecting a visitor's Maru account.
Review content visibility and rights before publishing assets. For a learning platform, catalog or branded service, see creative platforms and education.