Hardware just opened up.

Take your gear further. Discover new software for the devices you own, build on someone else’s ideas, or create something of your own.

Maru brings a shared DSP library and tools for building across platforms. We’re extending that foundation to more devices, so the same musical algorithms can power a plugin, a web instrument or your own hardware—without starting again for each one.

Explore firmwaresBuild for hardware
FM-1, MPC-style and KICK-style instruments connected to branching synth, sampler and sequencer software

The FM-1, reimagined by its creators

New synthesis engines, sampling and sequencing on the same pocket instrument. Explore what each project changes and the code its creators share.

The FM-1 movement

A pocket synth became a starting point.

A small, affordable instrument with keys, knobs, a screen and a speaker. Community developers saw room for new synth engines, samplers and sequencers, and started making them.

The FM-1’s community-built firmware is open source where its authors choose it. The device itself is not an open-hardware design. Its documented update path is what makes these experiments possible.

Play the virtual FM-1

By device

By use

By type

One project. More places to run it.

An instrument shouldn’t need a different codebase for every place you want to play it. Maru’s shared DSP library and microcontroller targets provide the foundation. We’re extending it to more device platforms.

Keep the synthesis, effects and parameter behavior together. Adapt the controls and connections to the hardware. Improve the engine once, then build and test the versions you want to share.

Explore the toolkit

Your sound engine

  • In your DAW

    Plugin controls, automation and presets.

  • On the web

    An interactive preview people can open with a link.

  • On your device

    Firmware adapted to the device’s controls and resources.

  • In your own design

    A microcontroller, custom pedal or instrument you build.

Shared musical code, target-specific builds. Availability depends on the project and target; each device still needs physical testing. Build guides describe current support and experimental paths.

Writing the firmware is only part of the job.

People need to know which device it runs on, which version to download, how to install it and how to get back to the previous one. Creators need a way to test changes, package releases and keep that information up to date.

We’re building the same path for firmware that we’re building for plugins: edit the project, check the build, publish a version and help people install it.

  1. Edit

    Start from a project or a permitted remix. Change its sound and controls while keeping source, licence and author credit together.

  2. Validate

    Check sound, controls and performance against the exact build. Record browser, emulator and physical-device results separately.

  3. Publish

    Attach versioned files, compatibility information and release notes to the project so people can find the right build.

  4. Install & update

    Guide people through the device’s installer, prerequisites and recovery steps, then help them keep track of updates.

Today, the catalog links to authors’ releases and installation instructions. Maru’s development tools provide build and diagnostic workflows for supported targets. Integrated firmware publishing and installation are in development.

Build & publish with Maru