For studios & labels
Consistent output across a catalogue
The same analysis, the same targets and the same measured report on every track, whoever ran the job and whenever they ran it.
What actually gets in the way
Consistency across a catalogue is manual
Twelve tracks, three engineers and a deadline produce twelve defensible masters that do not sit together as a record. Making them match is a pass nobody costed.
Volume work is the work you cannot take
A back catalogue of four hundred recordings to clean up is either a quote nobody accepts or a project nobody staffs. The unit economics only change if the per-item cost does.
You are responsible for other people's recordings
Unreleased material sitting in a third-party tool is a conversation with an artist you'd rather not have, and 'we use a cloud service' isn't an answer to it.
The workflow
How it goes
- 01
One target, applied to everything
Set the loudness and tonal target once — from a reference track if the record already has one — and every track in the run is measured against the same target and reports its measured result. Consistency becomes something you can verify rather than something you hope for.
- 02
Volume through the API
The same contract the app uses. Submit jobs, receive signed webhooks on completion, fetch results by signed URL. Audio never passes through the API itself, and every response carries a request identifier that traces to the job and its stages.
- 03
Isolation you can describe to an artist
Each workspace has its own prefix in storage and its own credentials; audio is reachable only by signed, expiring URLs; decoding runs in a sandbox with no network. Staff can't listen to your audio. That's an access model, not a policy statement, and internal reads are audited.
- 04
Seats when you need them
A workspace's plan sets its usage envelope, pooled across everyone in it, and seats attach to Professional and Max without changing plan. A three-person room doesn't have to buy the top tier to be three people.
The suite
The parts you would use
AI Mastering
Streaming-ready loudness and tone, with every move explained.
Audio Restoration
Remove noise, clicks, clipping and room without hollowing out the take.
Stem Separation
Split a finished track into its parts, up to five stems.
Spatial Audio
Binaural mixes that hold up on headphones, built from your stems.
Questions
What people ask before starting
- How consistent is it across a catalogue?
- The same input produces the same output — processing is deterministic, and an identical re-run resolves to the prior result rather than being computed again. What varies between two tracks is what the analysis found in them, which is the variation you want.
- What happens when a job fails?
- Jobs that fail for our reasons are not metered. The fault taxonomy is part of the published API contract rather than something a support ticket decides case by case, so an automated pipeline can branch on it.
- Who can access our audio?
- Your workspace. Staff cannot listen to it by default, every internal read is recorded and auditable, and audio moves only through signed URLs that expire. It is never used to train anything without a separate, explicit decision.
- Can we run this through our own pipeline?
- Yes. The API is async-only, with jobs, live progress and signed file URLs, and it is the same engine the app uses rather than a reduced version of it.
- How does this work for a room with several people?
- A workspace's plan sets the usage envelope and it is pooled across everyone in it, with seats attaching to the upper tiers. A three-person room does not have to buy the top tier in order to be three people.
- What about volume commitments?
- Catalogue work is a conversation rather than a checkout — tell us the shape of it and we will tell you honestly whether we are the right answer for it yet.
Next