Source ↗

Help shape catalog controls

Review how Clef connects recordings and compositions, records permissions, and helps labels and publishers administer their catalogs. Tell us what your team would need to use it.

Watch the walkthrough ↗Try the sample catalog ↗

The public alpha uses synthetic examples. Start with the walkthrough, then explore the part that matters to your work.

The MLC supplies U.S. publishing information and DSP-supplied recording references. Labels and publishers provide evidence of the rights, shares and territories they control.

Read how each source supports a decision
Two music staves, one above the other. The top staff opens with a treble clef and holds the first four bars of the Ode to Joy melody. The bottom staff opens with a bass clef and copies each note to the same place, where it reads as a different note.
The opening of Beethoven’s Ode to Joy, with each note copied to the same place on a second staff, where a bass clef turns its first notes, E E F G, into G G A B. A machine reads the same notes as numbers for pitch, onset and length.

What would make Clef useful to you?

Choose the perspective closest to your work. Each one asks a question the alpha cannot answer alone.

Read the technical review guide ↗

Labels, publishers and rights organizations

Follow a request through catalog terms, rights evidence, approval, and reporting. Which decisions, team roles, or client requirements should the workflow handle?

Artists, songwriters and managers

Look at how permitted uses, credits, and payment evidence are recorded. What would you need to understand, agree to, or challenge?

Music-data and standards specialists

Review how recording and composition references, including ISRCs and ISWCs, relate to rights records. Which matching evidence or exchange fields would your organization require?

License seekers and AI developers

Try describing your intended use, source material, model, and duration. Can you express the request and understand the terms you would need to fulfill?

Implementation, security and legal teams

Review installation, access controls, supporting contracts, and signed records. What would your organization need before running Clef for its clients?

Researchers, advocates and supporters

Examine the public source and sample workflow. What evidence would help you assess its usefulness to creators or support an installation?

Technical feedback goes to GitHub

Each route opens a template, so your report reaches the people who maintain that part of the code.

What would your team need?

We may publish the substance of accepted, rejected, and unresolved feedback. Public attribution to you or your organization requires your approval.