Give your label or publishing team its own catalog controls for AI licensing. Clef’s software is free to self-host. When you adapt it, we ask you to contribute useful improvements back to the main project.
For teams with their own engineers. You install Clef, configure catalog policies and integrations, and run it in your infrastructure.
The current release is free to self-host. Your organization manages hosting, updates and administration.
US$0 software fee
For teams that want it running in their infrastructure without building it themselves.
We agree the configuration, integrations, branding and handover with your team before work begins. Your organization owns the installation and takes over day-to-day administration. Pilot organizations receive 50% off Clef’s standard setup fee for the agreed scope. Your quote shows the standard fee and the pilot discount; hosting and ongoing services are priced separately.
50% off Clef’s setup fee for pilots
Request a setup quoteYour release includes its software license. Current terms and planned own-node license. Installing for other organizations? Partner program.
Install the published software, adapt it to your workflow and administer your catalog in your own infrastructure.
Released alpha v0.1.0-alpha.1, AGPL-3.0-only. Your team covers hosting, maintenance and any third-party service charges.
An importer built for one publisher gives the next publisher a working starting point. When your team makes a useful change, propose it for inclusion in Clef so everyone can benefit.
This is our community expectation. The license included with your release defines your legal obligations.
Read the contribution guide ↗Use synthetic examples in public contributions. Keep private catalog records, contracts and credentials in your organization’s systems. Discuss a proposed improvement on GitHub.
Help labels and publishers install and maintain their own nodes. You set your service prices and retain your service revenue.
Explore the partner programProposed partner license
Proposed commercial program for a future designated release; applications express interest. The current AGPL release permits commercial services under its own terms. The partner first-client offer is separate from the 50% discount on Clef-assisted pilot setup fees.
Yes. The current release, v0.1.0-alpha.1, uses AGPL-3.0-only, which permits commercial use and redistribution subject to its terms. Labels and publishers can use it while licensing and administering the catalogs they represent. Read the current license and the proposed future terms.
We ask teams to offer reusable improvements to the main project. Submitting a contribution is voluntary. The current AGPL license separately requires corresponding source to be available in the circumstances it specifies, including an offer to remote users interacting with your modified version. Sharing source with those users and submitting a change to Clef are distinct actions. Read the AGPL source-sharing terms.
Report a reproducible problem, improve an instruction, translate a screen or explain a catalog workflow using synthetic examples. A useful report identifies what your team tried, what happened and what result it needed. Send product feedback.
Clef reviews proposed changes for usefulness, compatibility, security and maintainability. Discuss larger changes through a GitHub issue before commissioning work; agree an approach and the release terms for the contribution.
Pilot organizations receive 50% off Clef’s standard setup fee for the agreed scope. Your quote identifies the work and discount. The partner first-client offer is separate from the 50% discount on Clef-assisted pilot setup fees.
Yes, under the current AGPL license and its obligations. The proposed Own-Node and Partner Licenses concern a future source-available release once adopted. The partner page explains the proposed commercial offer.