Private beta

The agent for audio dev.

Describe the audio tool you want. Bring your own sounds or start from an idea. The Studio agent turns your direction into a playable, editable project.

Example prompts include sampler instruments, generated drum kits, modular racks, and MIDI tools.
SoundInstrumentEffectMIDIRack
Request access

Start with the whole idea or one small change. Studio builds a playable version, then you listen and tell it what to do next.

Build in the browser · bring supported projects to VST3 / AU / CLAP

Want the code and full control? Explore the Engine.

What you can make

Start with a sound. End with a tool you can play.

Make a drum kit from generated sounds, turn your recordings into an instrument, build an effect, or connect a few ideas into a rack. You can stop when you have something useful or keep going until it becomes a finished plugin.

01

Sounds and drum kits

Generate one-shots and loops, add your own recordings, and turn the sounds you like into a kit or sample bank.

02

Instruments

Turn a folder of samples or a synthesis idea into an instrument with the notes, layers, and controls you want.

03

Effects and MIDI tools

Build an effect for your sound, a chord generator, a sequencer, or another tool you wish you had in your setup.

04

Racks

Connect instruments, effects, and generators into a setup you can play, save, change, and eventually share with other people.

Describe it. Hear it. Keep shaping it.

You focus on what the tool should do and how it should feel. Studio handles the code and keeps a working version ready to play.

01

Tell Studio what you want

Describe the idea in your own words. You can also add recordings or MIDI when they are part of the tool.

02

Listen to a working version

The agent handles the code and puts together something you can play, rather than stopping at a written answer.

03

Ask for changes

Try it, move things around, and tell the agent what feels wrong or what you want to explore next.

04

Use what you made

Keep the project for yourself, share a supported web version, or prepare it for a compatible DAW when it is ready.

Why an agent?

You do not have to start over every time you ask for a change.

Studio remembers the tool you are building—its sounds, controls, and the choices you already made. You can say “make the kick shorter” or “put that control on the front” and continue from where you left off.

“The snare is close.”

“Make it drier, keep the pitch, and put the room amount on the front panel.”

01

It knows what you are building

The conversation stays connected to your sounds, controls, and earlier decisions, so you do not have to explain the whole project again.

02

It can make connected changes

Ask for a brighter sound, a simpler control, or a different layout. The agent can work on the parts that need to change together.

03

You stay in charge

Listen as you go, keep what works, and change direction whenever you want. The agent does the technical work; you make the creative decisions.

Use it in your setup

Play it in the browser. Bring it into your DAW when it is ready.

Try the tool while you build it. For supported projects, we can then prepare a VST3, Audio Unit (AU), or CLAP version for a compatible DAW. Because Studio is in beta, we check that path with you for each project.

VST3Audio UnitCLAP

01

Play as you build

Hear the instrument or effect in the browser and adjust it before worrying about packaging.

02

Keep your controls and presets

For supported builds, the controls and presets you shaped in Studio come with the tool into your DAW.

03

Prepare the plugin

We check the format and DAW, then prepare a supported build for you, your collaborators, or an agreed public release.

Native builds are not a one-click export yet. During the private beta, we work through packaging, installation, and any public release with you.

Request Studio access

Studio, Engine, or collaboration

Choose the way you want to build.

Use Studio when you want the agent to handle the code. Use the Engine when you want to work in the code yourself. Work with us when you want our team involved in the project.

Create with Studio

Describe the tool, add your sounds, and shape a playable result without writing code.

Request Studio access

Build on the Engine

Use the source, SDK, UI kit, and development tools directly when you want full control.

Request developer access

Work with our team

Bring us into a new instrument, an audio workflow, or a research project that needs product and engineering help.

Talk about a project

Studio FAQ

A few practical questions.

Studio is still early. Here is what you can expect from the private beta and where we are heading next.

Private beta

Want to build something with Studio?

Tell us what you want to make and how you work today. We are inviting a small group of creators to try Studio and help us decide what to build next.