Cue vs Disco.

Disco is the standard catalog tool. They're great at file management, metadata, branded playlists, watermarking. If catalog management is your only job, you'll be happy there.

Cue is a workspace for music in motion. We do the catalog and sharing competently — same metadata, same branding, same watermarking — and we go further into the work that comes after sharing: feedback rounds, voice notes, transcription, and AI rewrites in engineer language.

Honest list:

• ·Disco's been around longer and has more enterprise customers. If you need SSO, custom territories, and an established procurement story, they have it; we don't yet.
• ·Their AI search / similarity / instant-instrumental discovery suite is a paid add-on but it's polished. We'll match this feature space over time, but it's not where we lead.
• ·They support more integrations into label distribution pipelines (DDEX, Distributor Ingestion) than we do today.

• ·Timestamped, anchored comments — Cue notes attach to the second of music, not the file. Disco comments attach to the file.
• ·Voice notes that transcribe automatically — record straight from the page; the transcript shows up under the audio in seconds. Disco doesn't have voice notes.
• ·Hone — single-button rewrite of casual feedback into engineer terminology. The use case Disco isn't built for.
• ·Takes that stack with notes that survive — upload v2 and the v1 notes travel with the song, with a 'noted on take 1' pill so you remember which version got the remark. Disco versions are siblings with no shared comment surface.
• ·Reply threading on individual notes — Basecamp-style discussion under any comment.
• ·Self-review scratchpad — internal-only notes on your own mixes. Disco doesn't have this surface.
• ·Pricing — Disco's Plus + Pro tiers cap at 1K files; Cue is unlimited during early access.

Pick Disco if catalog management at enterprise scale (5+ team seats, cross-territory rights, distribution pipelines) is your primary need and you're not running structured feedback over the same surface.

Pick Cue if you're a producer or mixer who also needs to pitch, an A&R who also takes notes, an artist team who wants the EPK + the feedback loop in one place, or a sync agent who follows up the listen with requested edits.

Run both if the catalog is in Disco for historical reasons but the actual creative work — review, takes, structured feedback — should live somewhere built for it. CSV import is on Cue's roadmap; we want the two-tool flow to be painless.

We respect Disco. They built the standard. We're not trying to take their lunch; we're trying to build the thing that comes after they walk away. If you've been on their platform for years and want to keep using it for catalog while running rounds + reviews on Cue, that's a fine workflow and we won't try to talk you out of it.