Rights OS by ColLabz is the rights and publishing tool for Sri Lankan music. Splits, owners, consents and agreements for every song, confirmed by the people on it and ready to show anyone who asks.
One whitelist for ColLabz and Rights OS. Rights OS opens in its own waves.
Mage Duwe
Song record · Rights OS
Real song. Signing and approval states are illustrative.
Release ready
A split agreed in the studio. A recording owner nobody wrote down. A session musician who never signed anything. It all holds until the song does well. Then everyone remembers it differently, and years later nobody can prove what was agreed.
Run a catalogue of writers and works. Track deals, territories and shares, see what every song still needs, and register works with collecting societies from clean data.
Use Rights OS on your own, with or without a publisher. Register your songs, set your splits and keep the proof, by subscription.
Own the recording clearly. Record who funded it, who owns it, who shares in what it earns, and that every performer signed.
Know a song is cleared for screen before you use it: the song, the recording and the performers, in one answer.
Signed with Kuvera Publishing? Rights OS is free for every work and writer Kuvera Publishing looks after.
Type it in, or paste a Spotify link. Songs already crediting you are found and offered to you.
Add a song
Workflow demoMage Duwe
Supun Perera · found on Spotify
Import the song’s existing credits, then ask collaborators to confirm.
Real catalogue data. Approval and signing states are illustrative.
Writers, composers, arrangers, producers, featured artists, session players and choirs. Each by role, with their IPI number (the ID a collecting society gives a writer) if they have one.
Everyone on “Mage Duwe”
Workflow demoSupun Perera
Singer
Nisal Gamage
Lyrics
Dinesh Gamage
Melody
Prakash Ranasinghe
Guitar
Wageshan Shivanathan
Veena
Palinda Udawela Arachchi
Performer
Real catalogue data. Approval and signing states are illustrative.
Set the shares, and every writer confirms their own. Nobody’s share is assumed. Change it later, and it becomes a new version that everyone confirms again.
Composition shares
Workflow demoIf the split changes, everyone confirms a new version.
Real catalogue data. Approval and signing states are illustrative.
Record who owns each recording, who shares in what it earns, and that every performer gave consent. A song can have many recordings, and each one is tracked on its own.
Original recording
Workflow demoReal catalogue data. Approval and signing states are illustrative.
Rights OS works out which agreements the song needs, drafts them from its details, and sends them out for e-signature.
Agreements this song needs
Workflow demoDrafted from the song’s details. Signatures shown as an example.
Real catalogue data. Approval and signing states are illustrative.
When nothing is missing, the song is release-ready. A chain-of-title certificate shows how every right got to where it is now.
Ready to release
Workflow demoRelease ready
Chain-of-title certificate
Example certificate · not issued
Real catalogue data. Approval and signing states are illustrative.
Rights OS keeps the song that was written separate from the recordings made of it. The original, the acoustic version, the remix and the cover each have their own owners, performers, ISRC and release status, and all of them belong to one song with one ISWC.
ISWC identifies a song as written. ISRC identifies one recording of it.
Mage Duwe
The song · ISWC not supplied · 2 writers
Original recording
Owner: RADIO music (Label) · QZQAY2540889
Example acoustic recording
Owner: To be defined · Not supplied
Example remix recording
Owner: To be defined · Not supplied
Example cover recording
Owner: To be defined · Not supplied
Only the original recording is in the source catalogue. Other branches show how versions would be organised.
Every writer sees their own share and confirms it, rejects it, or raises a dispute. Each change becomes a new version, so you can always see what was agreed, by whom, and when.
Split sheet · Mage Duwe
Composition shares · from catalogue
Nisal Gamage
Lyrics
Dinesh Gamage
Melody
Real writers and shares. Responses are illustrative. A writer can request a correction; a revised split needs everyone’s confirmation.
See the composition and each recording as separate pieces of the same work. Follow who owns what, who can use it, and the agreement or licence behind every connection.
Select a person or connection to follow the evidence.
Acting under both writers’ mandates, the publisher licenses the master owner to record and reproduce the song. Composition ownership stays with the writers.
Mechanical licence agreement
Example supporting record
Music publisherRecord label
Studio version · This recording · worldwide · 3 years · non-exclusive
Tell Rights OS how the song was made. Its rules engine works out what paperwork that needs, then drafts each agreement from the song’s own details, ready to sign.
Rights OS adds…
SampleSplit sheet confirmation
Drafted from the song’s details · ready to sign
Featured artist consent
Drafted from the song’s details · ready to sign
More than 20 agreement types, from split sheets to master licences. Each is e-signed, and the signer, the time and the exact version are kept.
From project agreements to music licences, Rights OS brings the song’s rights, your agreed terms and our knowledge base together. AI agents help curate sources, draft missing clauses and check the result. The system assembles the document, with a source trail and a human review before signing.
From source knowledge to a reviewable draft.
Example workflowSource library
Acts, standards and policies
Curator
Connects sources to rules
Knowledge base
Sources, rules and clauses
Clause drafter
Fills missing wording
Work & deal
An original recording
Rights engine
Identifies the documents and rights needed
Document engine
Combines clauses with confirmed facts
Evaluator
Checks the draft independently
Draft pack
Editable documents, with a source trail
Human review
Review, edit and decide when to send
You approve and send
Choose a node to see what happens inside.
Knowledge base
Original sources
Sri Lankan copyright and electronic-signing law, collecting-society rules, industry standards and platform policies.
Rules and context
Ownership, rights, consent and the conditions that apply to this document and jurisdiction.
Clauses and templates
Versioned wording, fields for agreed facts and document structures, with review and approval status.
Producer engagementMatched ruleOriginal source section
The producer’s role and agreed compensation select the relevant clause. The server fills the confirmed details from the work.
Illustrative workflow · not a live document request
A source behind the wording.Trace a clause to its version, the rule it satisfies and the original source.
A gap becomes a task.Missing facts or wording are surfaced for review. They don’t become invented terms.
People stay in control.Agents work with redacted facts. People review the draft and decide when to send it.
Rights OS checks every song across the composition, the recording, the performers, publishing, collecting societies, sync, AI use and the chain of title. Anything unresolved becomes a clear to-do: what’s missing, why it matters, and who has to act.
Mage Duwe
Example checklist · 3 things left
Readiness and to-dos shown as an example.
To do
When a song’s chain closes, Rights OS issues a numbered chain-of-title certificate. It shows who created the song, who owns it now, how every right moved, and the signed document behind each step. It can’t be issued while anything is missing, and it can’t be edited: a change issues a new certificate.
Send it to a distributor, a broadcaster, a film producer or a collecting society.
Chain-of-title certificate
Mage Duwe
Example certificate · not issued
Workflow demoWritten
Nisal Gamage and Dinesh Gamage
Example: signed split sheet
Recorded
Music, mix and master: Amith Guru
Example: producer agreement
Performed
4 named performers in the catalogue
Example: performer consents
Owned now
Recording: RADIO music (Label) · 100%
Example: ownership agreement
Most songs aren’t simple. Rights OS handles the complicated ones as a matter of course.
Rights OS is built on Sri Lanka’s Intellectual Property Act No. 36 of 2003. That matters. Here, a commissioned song can belong to whoever commissioned it unless the contract says otherwise, which is the opposite of what most foreign tools assume. When a song falls outside what the rules can decide, it goes to expert review instead of getting a guess.
Rights OS does not give legal advice. See the questions below.
A brand commissions a jingle. Who owns the song?
Most tools built abroad
The writer, always.
IP Act No. 36 of 2003, s.14(4)
It can be the brand, unless the contract says otherwise.
So Rights OS asks how the song came to be made before it decides who owns it first.
Record catalogue-wide deals and each song’s publishing share, with territories and terms. Track every work’s registration at every collecting society, each with its own ISWC. When a writer’s split changes, Rights OS asks for their publishing confirmation again, so nothing goes quietly out of date.
Nisal Gamage · catalogue
Real catalogue| Work | Writers | Nisal’s share | ISRC |
|---|---|---|---|
| Mage Duwe | 2 | 50% | QZQAY2540889 |
| Chaaru Devi | 2 | 75% | ATR981229382 |
| Aathin Mathin | 2 | 50% | QZTLA2551124 |
Composition shares from the supplied catalogue. Society registration and publishing administration status aren’t recorded in the export.
Catalogue deals and per-song shares, with territories, terms and sync authority
Registration status at each collecting society, ACPOSL included
Writers’ IPI numbers, aliases and society memberships
Registration-ready exports for collecting societies
Licensing requests for covers, sync and samples, answered from the rights record
Your team works on writers’ songs only with the writers’ consent, and every change is recorded
Every change is logged with who made it and when
Identity checks for the people who sign
Government ID numbers stored encrypted
Two-step sign-in
Files kept in private storage and opened by short-lived links
Staff never change ownership without the owners’ consent
Rights OS records your agreements. It never becomes part of them. It isn’t a distributor, a collecting society or a law firm, and it never takes a share of your songs. You and your collaborators own your rights. Rights OS keeps the proof.
Kuvera Publishing is a separate publisher. It administers only works whose writers have signed with it.
Rights OS is not
Everyone confirmed on a song in Rights OS can show it on their ColLabz page as a confirmed credit. The lyricist, the session drummer and the mixing engineer get the same proof as the singer, and ColLabz Scout ranks confirmed work first.
Real credit. Confirmation and page update shown as an example.
Mage Duwe
Rights OS · Prakash Ranasinghe, guitar
Prakash Ranasinghe
Session guitar · ColLabz page
Mage Duwe
Guitar · with Supun Perera
Free
SubscriptionFor a catalogue of writers and works
SubscriptionFor your own songs
FreeTo confirm their part of your song
Pricing is announced when Rights OS opens. Join the whitelist to hear first.
Get whitelistedRights OS starts with songs, where the most people share one piece of work. Next come films, photography, design and writing: any work where several people own a part and someone needs to prove it.
No. It’s software that publishers, administrators and songwriters use. Kuvera Publishing is a separate publisher, and it uses Rights OS for the works it looks after.
No. Songwriters and composition owners can use Rights OS on their own, by subscription.
No. Anyone you invite to a song confirms their part for free.
Sri Lanka’s Electronic Transactions Act No. 19 of 2006 recognises electronic signatures. Rights OS keeps the signed copy, who signed it, when, and which version they signed.
No. It works out which documents a song needs and drafts them from reviewed templates. Anything unusual goes to expert review, and you can always take a document to your own lawyer.
Yes, including songs whose writers have passed away. Their estates and successors are recorded with evidence.
Only the people on them, and anyone you invite.
No. Rights OS records who is owed which share. Your distributor, publisher and collecting society collect and pay, working from clean data.
Join the whitelist. It’s the same one as ColLabz, and Rights OS opens in its own waves.
Splits confirmed, owners clear, every agreement signed, before anyone has a reason to argue.