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
Explore Maru's instruments, plugins, racks, agent-led Studio, Engine, PluginUI, music-theory computation, learning tools and research.
Install the maru CLI, create a module, 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.
Audition a module, map pedal controls, build and emulate, then qualify the exact artifact on a board.
Load a built VST3 in a plugin host and check its audio, controls, MIDI, and state.
Install the Maru skill for your coding agent and use it to create plugins, sample kits and banks.
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.
SDK
Build a flexible module face with host-bound controls, portable dependencies, and the UI kit.
Reusable, prepared audio building blocks for filters, effects, synthesis, and analysis.
The typed boundary shared by module graphs, browser audio, and native hosts.
Render chords, MIDI takes and free improvisations as audio with the experimental Accompanist module.
Concepts
Choose an authoring workflow around your product, existing tools and delivery needs.
How the Engine connects one portable module to a Linux pedal service or microcontroller firmware.
How to make a small number of physical controls useful across modules with many parameters.
The Pi 5, Pico 2, Daisy and ESP32-S3 target lanes, their delivery paths and the evidence still needed on real boards.
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.
CLI
Install the maru command, find its command groups, and use it from a terminal, a script, CI or a coding agent.
Sign the maru CLI in to your Maru account with maru login, check it with maru whoami, and use tokens in CI.
Create a runnable effect or instrument project with maru init, then open it in the workbench.
Live audio, MIDI, hot reload, diagnostics, and agent-assisted iteration with maru dev.
Validate, evaluate, preview, build, export and prepare a release of a module with the maru module commands.
Build, verify, inspect, install and remove AU, VST3, CLAP and AAX plugins with the maru plugin commands.
Install the Maru agent skill, serve Maru's operations over MCP, and let an agent discover guides and schemas from the CLI.