Prepare the release
Title, artist, genre, release date, territories, ISRC and UPC. The form validates the metadata that distributors normally reject first.
Distribution
Distribution built around metadata and rights
Orca Universe treats a release as a set of rights objects and delivery targets rather than a single upload. The workflow below is fully usable today; the store delivery layer is a labelled prototype until real integrations exist.
Delivery simulated
What is real, and what is not
Real today
- Release submission, storage and catalogue management
- Contributor and split records
- Royalty modelling and scenario comparison
- Admin review queue and activity history
Prototype
- Delivery to streaming services is simulated in-app
- No relationship with any streaming service is claimed
- Royalty figures are estimates, not statements
- Service payments run as demo checkout records
Workflow
Four steps from master to catalogue
Attach audio and artwork
Audio masters and cover art are stored against the release. In this prototype the file references are recorded rather than transcoded.
Declare splits and contributors
Collaborators, roles and revenue splits are captured per release so the royalty model has something honest to calculate from.
Track delivery
Each platform target moves through pending, metadata review, delivered, scheduled and live. These stages are simulated — no store receives the release.
Scope
Territory model
Releases carry explicit territory scope so rights can be reasoned about per region.
WorldwideUnited StatesUnited KingdomGermanyFranceSpainNetherlandsJapanBrazilMexico
Submit a release in the workspace
Open the artist workspace and walk the full submission flow.