Everything from an upload to a paid-out royalty.

The system of record. Releases and tracks carry the complete contributor and composer graph rather than a flat text field, so a credit is an entity you can query, correct once, and deliver consistently to every store.

The upload surface your artists actually touch. Release, Tracks and Distribution as three tabs over one record, saving as they type, with a live validation panel beside them. Submission unlocks only on a clean report — so a release does not reach your queue, or a store, in a state someone has to send back.

Delivery orchestration with a per-account store catalogue on top. The reach is a function of the relationships you hold, not of the software: through aggregator and partner routes the addressable network runs past 400 platforms and sub-platforms, and the delivery layer is built to target any endpoint you have a deal with. Every client sees only the destinations you enabled for them.

The delivery relationship and the software that drives it do not have to come from the same company, and every credible platform in this category now says so. The difference is in the detail: this is not restricted to a higher plan tier, not limited to a short allowlist of endpoints, and the API you would automate it with is publicly documented rather than issued under an account. Where your upstream partner exposes an API, the whole system is built on top of it — artist dashboards, admin console, catalogue, analytics, royalties, payouts and support.

Quality control that exists now, rather than the automated engine described on the QC page. Releases arrive pre-validated by the builder, land in a review queue, and are approved, returned with a reason, or held. The automated checks being built plug into this queue rather than replacing it — the queue is where anything a machine should not decide alone ends up either way.

Who owns what, who is owed what, and on what evidence — held against the release and track rather than in a spreadsheet somebody has to remember to update.

Statements arrive in as many shapes as there are reporting parties. The pipeline normalises them into one table, deduplicates on the period and the reporting source rather than on a filename, and attributes every line to the recording it belongs to.

Earnings become payments without anyone maintaining a parallel spreadsheet. A monthly run picks up every account whose latest statement clears the threshold, and the amount actually paid is recorded in the account's own currency.

Reporting built on the ingested statements rather than on a separate analytics product, so the number an artist sees and the number you pay out are the same number from the same row.

Every account is a hard boundary. Isolation is enforced in the query layer and asserted by a scoping matrix in the test suite, because 'we scope by account everywhere' is a claim that needs a machine checking it, not a convention.

The money layer, including the parts nobody demos. Currency is derived from the account's country rather than trusted from the client, mandates are never charged before the account is approved, and every redirect flow is confirmed server-side.

A distribution platform is a support business wearing a technology coat. This is a full desk — inbound email parsed and threaded on message identity, shared and personal mailboxes, SLA clocks that stop and start with status.

Masters, artwork and documents held in object storage behind signed, expiring URLs, with large uploads going straight from the browser to the bucket so a big master never has to squeeze through the application.

Moving a live catalogue is the single biggest reason a label stays on a platform it has outgrown. Migration tooling matches on identifiers first, reports what it could not resolve, and never silently invents a record.

The other half of the rights picture. A recording is one asset; the work behind it is another, with its own owners, its own registrations and its own money. Bringing works into the same system of record is the next major expansion — and it is partner-plural by design: publishing routes through whichever administrators and societies the client already works with, not through one we picked for them.