Build inside the DAW.
Get paid every run.
Not another export-import tool nobody opens twice. Actions that run where the work actually happens.
Founding access · Logic Pro is the first release · nothing leaves your machine
outside the room.
You built something good for producers. To use it they have to bounce, leave the DAW, open your thing, do the work, export, come back and re-import.
So they use it once, tell you it's great, and never open it again. Not because it's bad — because the workflow costs more than the feature saves.
is a different wall.
Logic has no API. Ableton never published a control-surface spec. Pro Tools' SDK is NDA-gated. Cubase's is dual-licensed in a way that will ruin your afternoon.
Getting inside one is months. Getting inside all of them is a company, and it's a company nobody wants to run.
got through the wall.
Revo is an AI co-producer that lives inside the DAW. It reads project state and drives real operations — the same access an assistant has inside a code editor, pointed at a session.
You write a skill once against the open protocol. It runs in every DAW we cover, and in every DAW anyone else adds later.
You never touch a DAW SDK again.
every time it runs.
A skill, a workflow, a plugin chain, an action, an adapter. Anything a producer invokes and a machine executes.
Usage-based, split with you, paid monthly. No approval gatekeeping beyond conformance and security review.
The marketplace is the point. We take a cut of it, not a cut of you.
An assistant that actually moves things.
Not a chatbot beside the DAW. A layer inside it that reads the session and performs real operations on it.
Producers ask for the boring twenty minutes: gain-stage everything, rename and export forty stems, comp fourteen takes to the first pass, prep the session for a mix engineer, rebuild the same drum bus they build on every record.
Those twenty minutes are the product. And most of them are things somebody else already knows how to do better than we do.
The engine is ours. Everything above it is yours.
That's the whole of it. We hold one layer — the part that turns a sentence into a correct operation list — and everything a producer actually chooses to run belongs to whoever wrote it.
No CLA. No copyright assignment. We never acquire ownership of anything you publish.
Four things you can publish. All of them pay.
How the money splits
Running a skill consumes credits. Credits cover the inference the intent engine does to execute it. So the split is on what's left after that compute is paid for — because a share of gross would eventually pay you out of a margin that doesn't exist, and then we'd change the terms.
Adapters are paid differently, because they aren't chosen by a user — they're infrastructure everything else runs on. Those draw from a pool of 10% of B2B verification income, split pro-rata by sealed sessions running through them, with a 1.5× founding multiplier for whoever ships before there's any revenue at all.
What we won't do
- Compete with you from the store. If we ship a first-party skill in a category you already serve, yours keeps its placement and its share.
- Gatekeep beyond conformance and security. Review is about whether it works and whether it's safe, never whether we like it.
- Change the split retroactively. Terms in force when you publish hold for that version, for the life of that version.
- Take your copyright. Ever. It's your repository and your name.
One honest caveat: the marketplace pays what it earns.
Revo Co-Pilot is early. If usage stays small, 70% of a small number is a small number, and we'd rather you hear that from us than discover it from a statement. What we can promise is that the share, the accounting and the reporting stay the same whether it's ten runs a month or ten million.