An open database made music credits editable, not automatically true

MusicBrainz stores CC0-licensed, volunteer-edited relationships, which helps disputed credits but is not a verified registry.

Historical event

July 17, 2000

Site publication

September 18, 2026

What happened

MusicBrainz launched on 17 July 2000, created by Rob Kaye, according to its own About page, in direct response to the commercialisation of CDDB, a formerly open disc-identification database. The page states the project runs as a 'community-maintained, open source encyclopedia of music information', where volunteers contribute artist, release and recording data and relationships such as composer or performer credits. It is operated by the MetaBrainz Foundation, a non-profit that, as retrieved on 16 September 2026, also runs related projects including ListenBrainz and the Cover Art Archive.

What the documents say

MusicBrainz states plainly that it does 'not actually store or have access to any music recordings' itself; it stores metadata and relationships about them. Most of that data is released under a Creative Commons Zero licence, meaning, in the page's words, 'you can download the data and use it however you like', with a smaller remainder under a non-commercial share-alike licence and paid commercial licensing available through MetaBrainz. The foundation's own page describes its data as 'gathered by volunteers and peer-reviewed for accuracy', a community-review process rather than a label- or publisher-verified one.

Why it matters for makers

The mechanism that matters here is structural: MusicBrainz records relationships, who composed, performed, produced or engineered a given recording, as open, queryable, editable data rather than as a line in a single company's proprietary catalogue. When a credit is disputed, for example whether a generated stem's underlying performance should list a named artist, an open, versioned record of who edited what and when is a different kind of evidence than a closed database's internal, unauditable entry, though it is only as accurate as the volunteers who maintain it.

What to check before you use it

If you rely on MusicBrainz data for crediting or metadata matching, check the edit history on the specific entry, since CC0 openness does not guarantee accuracy, only that errors can be seen and corrected by anyone. This is an editorial point beyond the documents themselves: treat MusicBrainz as a starting point for open, checkable metadata, not as a substitute for a rights-holder's own registration or a collecting society's records where a specific claim needs weight.

• Does the MusicBrainz entry you are relying on have a visible, recent edit history, or is it unreviewed since creation?
• For a disputed credit, does an open metadata record change what you can prove versus what a closed database would show?
• Which licence tier applies to the specific data you want to reuse, CC0 or the non-commercial share-alike remainder?

Open, volunteer-maintained metadata is a genuinely different kind of record from a proprietary catalogue: checkable and correctable, but only as strong as its editors. That trade-off is exactly what MusicBrainz's own documentation describes, not an assumption added on top of it.

Sources & reading trail

States the 17 July 2000 founding, the CC0 and non-commercial licence split, and that recordings themselves are not stored.

Source published: Not established · Retrieved: 16 September 2026

Describes the non-profit's open-data mission and its volunteer, peer-reviewed data model.

Source published: Not established · Retrieved: 16 September 2026

Papers, terms and official documents establish the record; the maker reading and the checks are Signal to Song editorial analysis. This retrospective draft does not imply the site published on the event date.

Continue reading

• YouTube's own blog places Content ID's launch in 2007
• A DDEX-built credit standard is how Spotify's AI labels arrive
• Music’s AI credit standard is still being built by DDEX
• Browse the complete the archive

Published September 18, 2026, not on the date of the event described.