Documentation
Create with an agent in Studio, develop a self-contained module, or integrate the engine into your existing workflow. Find guides for editing, the SDK, DSP, UI kit, presets and publishing to supported targets.
Getting started
Find your path through Maru Studio, module authoring, the UI kit and publishing.
Open a starter, shape it with an agent, and hear it in the workbench.
Turn a musical brief into a working audio tool without becoming a plugin-framework specialist.
One typed project contains the sound, interface, and path to each supported target.
The few project areas you change and the output the toolkit generates.
How the portable module model can extend to pedals and instruments.
Load a built VST3 in a plugin host and check its audio, controls, MIDI, and state.
Studio tools
Create with an agent, edit live, save a revision and prepare a supported release.
Map your sounds, audition keys or pads, save versions and export a playable sampler bank.
Write chords, keys, drums and seeded generators as code in the Code Sequencer, and build songs from the layers of other songs.
Concepts
Choose an authoring workflow around your product, existing tools and delivery needs.
How layered testing keeps audio dependable across browsers, native builds, plugin hosts, and hardware.
Prepare a module, presets and assets for a reviewed beta release.
Ownership and commercial terms during the private beta.
SDK
The typed boundary shared by module graphs, browser audio, and native hosts.
CLI
The project component that develops, checks, builds, and bundles a Maru tool.
Begin with a runnable private-beta starter or an existing module.
Live audio, MIDI, hot reload, diagnostics, and agent-assisted iteration.
Build and verify the targets supported by a private-beta project.