Roster OS gives a manager or label one clear window across every artist who's granted them access — the money that's waiting, the paper that's ready, and what needs attention today. Access artists control by the switch, and can see every time you use it.
| held, awaiting accept | $86,400 · 11 people |
| diligence ready | 82% |
| needs a signature | 3 releases |
| open contests | 1 · named |
| your access | granted · revocable |
Every artist who's shared with you, ranked by what's active — instead of logging into each account one at a time.
The home screen leads with the short list actually waiting — pending confirmations, statement periods that just closed — so you work the exceptions, not the whole list.
An artist grants you precisely what you should see, nothing more, and every time you open a statement or catalog it's written to their trail. That's why they're comfortable sharing.
See the funds parked because a collaborator hasn't accepted yet — by counterparty, amount, and days aging — so nothing quietly stalls before a payout.
One readable view of the rights answers, confirmations, signed terms, and credentials for a release — and a flagged one shows both its clean paper and the open question, never a false "all clear."
A sweep that names where a split no longer matches its accepted terms, who hasn't signed, and what's contested — recorded facts you can act on, not appraisals.
Import a catalog from the distributor you already run — your identifiers are preserved exactly, never regenerated, because stream history follows them. Or move delivery to us and run it all in one place.
Reports come in as a double-entry ledger where every figure clicks through to its source and split — so the roster-level math foots back to the artist statements exactly.
The roster view only matters if the foundation under it holds. Here is what holds it up — stated specifically, so you can ask us to show you any of it.
Access rules run in the database itself, underneath the application. A request with no grant behind it returns nothing — permission is checked on every read, not assumed from the screen.
When an artist withdraws access, the very next request is refused. Their numbers drop out of your view from that moment — and they're told how this works before they ever grant it.
Signed records and the audit trail are append-only. Change a byte and verification fails — what's on the record stays on the record.
Tested against cross-account access, revoked-mid-session, scope-isolation, and identifier-guessing cases — the specific ways a roster view could leak what it shouldn't.
One real release workflow — the messier the better.
Together we map the people, the terms, the evidence, and the open items.
You see exactly what Splitkeep would make visible — and what it would name as waiting.
You keep your distributor, your identifiers, and your history throughout.
Every label and team is different, so Roster OS is quoted after a short evaluation of your scale and what you need — not a flat, one-size fee. Tell us about your operation and we'll put together terms that fit.
We're onboarding a small number of managers and labels as design partners while the last rails get finished. Tell us about your roster and what you're trying to keep straight, and we'll walk the whole record with you.