Bulk ingestion via Excel templates and SFTP. limbo/ auto-assigns ISRCs and UPCs, or carries your own ISRC ranges and catalog-number sequences.
The rails your
catalog runs on
limbo/SupplyChain is the delivery infrastructure behind the music. DDEX-native ingestion, identifier management, validation, and delivery to every DSP, with catalog migration that loses nothing. Approved by the major DSPs, and trusted to carry the catalogs of labels, distributors and even other Merlin members.
From ingestion to
live on the stores
limbo/SupplyChain manages the full lifecycle of a release: ingestion, identifiers, DDEX packaging, validation, delivery, takedowns, updates and redelivery, with a clear status on every release at every step. It is built as infrastructure, so it scales and stays consistent instead of depending on who is at the desk.
ERN 4.3 and 3.8.2, validated before queueing, delivered per DSP and per territory with scheduled releases, takedowns, updates and redelivery, and a full release-status state machine.
Move catalogs in on the same UPCs and ISRCs, preserving play counts, playlist placements and algorithmic data. You keep your numbers when you switch.
The independent
supply chain
The other serious supply chains are owned by the people you compete with. limbo/ is not, and for infrastructure, that is the whole point.
FUGA is owned by Downtown, now part of Universal, and the other serious supply chains sit under a major label or private equity. limbo/ is independent and founder-owned, so your delivery layer answers only to you.
Approved by the major DSPs and used by other Merlin members to deliver their own catalogs. When others build on your rails, the rails are good.
Drive the whole supply chain through the API, and pair it with distribution, royalties and the rest of the Music Blocks.
Supply chain,
answered
What is a music supply chain?
It is the infrastructure that moves a release from ingestion to live on the stores: validating metadata and audio, generating or carrying identifiers, packaging in DDEX, delivering to each DSP, and handling takedowns, updates and redelivery. limbo/SupplyChain is that layer, run as real infrastructure rather than a manual back office.
Is limbo/ approved by the DSPs?
Yes. limbo/ is an approved delivery partner across the major DSPs, which is what lets it deliver directly and reliably, and is why other companies trust it to carry their catalogs.
Can limbo/ deliver content for other distributors and Merlin members?
Yes. limbo/'s supply chain delivers not only for labels and distributors, but also for other Merlin members who use it as their delivery infrastructure to the DSPs. It is the rails, not just a destination.
Can I migrate my catalog without losing streams?
Yes. Catalog migration reuses your existing UPCs and ISRCs, which preserves play counts, playlist placements and algorithmic data across the move. You do not lose your numbers when you switch to limbo/.
Can I bring my own ISRC and catalog numbers?
Yes. limbo/ can auto-assign ISRCs and UPCs, or use your own ISRC ranges and catalog-number sequences, with bulk ingestion via Excel templates and SFTP for volume.
How is limbo/ different from FUGA and other supply chains?
Ownership. FUGA is owned by Downtown, now part of Universal, and the other serious supply chains sit under a major label or private equity. limbo/ is independent and founder-owned, so the infrastructure you run on has no conflict of interest with your business.
Deliver on
independent rails
Apply to partner with limbo/ and move your catalog onto a supply chain that is approved by the DSPs, trusted by other Merlin members, and owned by no one but its founders.
Last updated: June 2026. A short qualification form starts every partnership. Senior engineering joins the first call.