For music hackathon teams and workshop participants

Prototype a musical idea. Keep it going.

Move quickly from an idea to something you can play. Shape an instrument, effect, or musical interaction with Studio or Engine, listen as you build, and refine it with your team. When the event ends, take the prototype toward a tool you can keep using.

Studio and developer access are in beta. Check access and project fit before your event.

Two ways to begin

Start with Maru. Or bring what you already made.

Start with one sound or interaction you want to try. You choose the tools and how far to take it.

Starting a new project?

Describe the idea to Studio and direct the result with an agent, or develop it yourself with Engine. Build a small playable version, audition it, and change what you hear and how it feels.

Request Studio beta for a new idea

Already made something?

Bring the instrument, effect, or performance experiment your team already made. Work through a blocker or plan the next useful version, keeping your existing stack when it serves the project.

Discuss my existing prototype

Fast prototyping

Build, listen, change. Repeat.

Keep the feedback loop close to the music, from the first sound to the demo your team can play.

  1. Pick one playable idea

    Choose the sound, timing, or interaction you want to explore. Keep the first version small enough to try with your team.

  2. Hear each change

    Use the live preview to audition the sound and controls as you edit. Adjust the behavior, interface, and presets around what works musically.

  3. Make the demo easy to play

    Give teammates a clear starting preset and simple controls. Try it in the event setup, gather feedback, and choose the next change.

Reusable starting points

Plenty of examples to build on.

Explore instruments, effects, MIDI tools, and experimental interactions. Play the examples, find a useful starting point, and adapt it to your idea.

Find a sound to start from

Try the module library for synthesis, sampling, and effects. Hear how controls change the sound before choosing a direction.

Browse musical examples

Explore a different way to play

Look at sequencing, MIDI, gesture control, and generative music. Combine musical building blocks into an interaction your team wants to try.

Explore Engine

Make the example your own

Use the authoring guides, shared audio building blocks, and interface controls to change a project's sound and behavior.

Read the authoring guides

After the event

Choose what happens after the demo.

Bring us the prototype and the part you want to take further. We can scope the next version with your team, from a personal tool to an agreed release.

Use it yourself or with your team

Finish the controls, saved settings, and setup instructions needed to return to it after the event.

Prepare an open-source release

Scope reproducible setup, contributor permissions, a license, and a maintainer so another person can use and change it.

Explore a commercial release

Agree a bounded plan for demos, qualification, delivery, rights, funding, and continuing support.

FAQ

Before you begin

What should your team still be using after the event?

Describe a new idea and event setup, or bring an existing demo and its blocker. We’ll help you choose a playable first version or scope what comes next, and check access and project fit.

Sign in to submit the brief. We review project fit and the next step with you.

Discuss my project’s next version