Capture the split at the moment of creation, generate the CWR automatically and deliver it via SFTP to your CMOs. One workflow, every society your roster operates in.
Urban Sunrise
M. López · C. Vega · A. Ríos
HDRPB SPLEET GRHNWR0000102.10 TRN00000000NWR SPU0000000100000001 SPT0000000200000001
Three structural problems that publishers — independent or otherwise — recognise from day one.
The UK Government's own metadata report identifies it: multiple writers are involved and splits are rarely formalised in the studio. By the time the publisher tries to register, the data is partial and the writers are no longer aligned. Errors compound from there.
UK Gov · Music Streaming Metadata Report
SGAE in Spain, SACEM in France, GEMA in Germany, PRS in the UK, and four major PROs in the US (ASCAP, BMI, SESAC, GMR) plus new entrants. Each one with its own CWR fields, deadlines and delivery channel. The US Copyright Office itself has flagged the proliferation as a structural problem.
US Copyright Office · PRO Proliferation Letter
The academic literature on Spanish independent publishers describes 'Reclamación' as a core editorial function: contacting CMOs to flag missing or delayed royalty payments. When the original registration isn't clean, the money doesn't arrive — and someone on your team is on email all week trying to recover it.
EPSIR · Estudio de las editoriales musicales independientes en España
Spleet listens for the moment a split sheet is signed and takes care of the rest.
Your composer signs the split sheet from web or WhatsApp. Legally valid, with audio and video evidence.
We generate the CWR in the version each CMO accepts — today CWR 2.1 (CISAC standard, Rev 8) — with your publisher data, IPI numbers and territories already mapped. If a society asks for a different variant, we adapt per society.
We push the file via SFTP to each of your CMO accounts. You get a confirmation per society and a full delivery log.
Spleet rebuilds the ownership chain straight from the CWR: writers, publishers, IPIs, CISAC roles, societies, shares and territories. If something doesn't add up, you see it — we never hide it.
Urban Sunrise
ISWC T-321.054.942-1
Marina López
IPI 00489271044
Worldwide (implicit)
Carlos Vega
IPI 00701338219
Worldwide (implicit)
Fides la Diosa
IPI 00388120554
This is the very same view (real component) your team sees on each work's detail in the catalog. Shown here with sample data.
Direct SFTP delivery, no intermediaries. We generate the CWR in the version and variant each CMO accepts — no one-format-fits-all. We add new societies every month based on customer demand.
SGAE
ASCAP
BMI
SACEM
GEMA
PRS
JASRAC
SOCAN
APRA
SIAE
Don't see your CMO? Let us know and we'll prioritise it during onboarding.
See every composer, every catalog, every delivery in real time. No more spreadsheets.
Onboard your composers once. Their IPI, PRO and territories are reused on every future registration.
When a composer in your roster signs a split, you get a notification on WhatsApp the same minute.
Every CWR delivered, every confirmation received, every retry — visible from a single screen.
Urban Sunrise
LiveMarina López
Signed
Carlos Vega
Signed
Ana Ríos
Delivered to CMOs
Spleet uses Supabase Vault, the same primitives banks and healthcare apps use to protect secrets in Postgres.
If somebody ever got hold of a full database dump, they'd see only ciphertext — never the key. The key is managed by Supabase's secured backend systems, kept physically separate from your data.
Every credential is encrypted and signed (libsodium AEAD). If anyone tries to swap or tamper with a stored value, the signature is rejected and the decryption fails. It's not just confidentiality — it's integrity.
Database dumps and replication streams preserve the encryption. A leaked backup is unreadable without the off-database key. Decryption only happens in memory at the moment we deliver the CWR.
Each signed split is captured with Documenso (SOC 2 Type II, eIDAS and ESIGN Act compliant) and timestamped on the NEAR blockchain. Audit trail and legal validity, in two layers.
Yes, in Supabase Vault with authenticated AEAD encryption. The decryption key lives outside the database, so neither our team can read them nor is a stolen DB dump readable. They're only decrypted in memory at the moment of the SFTP delivery, and you can revoke them from your dashboard at any time.
Today we generate CWR 2.1 (CISAC standard, Functional Specification Rev 8 — the version every operating CMO accepts: SGAE, ASCAP, BMI, PRS, GEMA, SACEM, JASRAC, SOCAN, APRA…). If a CMO in your roster asks for a specific variant, we adapt per society — we don't lock you into a single format. CWR 3.0 (XML-based) is rolling out very gradually and we add support as each CMO certifies it.
Yes. Every signed split sheet goes into a review queue where your admin can edit ISRC, ISWC, territories, alternate titles or publisher splits before the CWR is generated and sent.
Spleet looks up the ISWC automatically when one already exists. If the CMO requires assignment, we coordinate with the society. Composer IPI numbers are stored in the roster once and reused on every future registration.
We're in early access during beta. Pricing is being co-defined with the first publishers we onboard. Reach out via the form and we'll discuss it transparently — there's no per-registration fee planned.
It depends on how many CMOs you operate in and how cleanly your existing roster data is structured. The first delivery to a single CMO typically takes a couple of weeks; multi-CMO setups are sequenced. We don't promise a fixed timeline blindly.
Songwriters can already use Spleet free for unlimited split sheets. CMO auto-delivery is publisher-specific because it requires SFTP credentials and IPI numbers held by a registered editorial entity, not by individual writers.
Leave your work email and we'll get on a call to set up your roster, your CMOs and your first batch.