labelflow

Pre-flight validation for every distributor.

Every distributor has its own rules - allowed genres, file format requirements, metadata field minimums, naming conventions, ISRC handling, lead-time windows. Most are documented across PDFs and partner portals; most labels learn them by getting a release rejected. Distributor Playbook is the rule set codified into Labelflow.

The rules, made operational.

Distributor-specific rule library

Every distributor's actual rules - genre allow-lists, metadata field minimums, naming conventions, ISRC handling, lead-time windows. Maintained centrally, updated as distributors update their rules.

Pre-flight validation

Before a release ships, it's checked against your distributor's actual rules. Anything that would trigger a rejection is flagged with the specific rule that's failing.

Specific error messages

Not "metadata invalid" - "track 4's genre tag isn't on this distributor's allow list" or "ISRC for track 2 conflicts with an earlier release". You know what to fix.

Auto-fix suggestions

Where the fix is obvious, Labelflow proposes it. Genre tag mismatch? Here are the closest accepted alternatives. Metadata field empty? Here's what to fill in.

The submit-and-wait-for-rejection loop.

Bundled in every plan. Proton at launch.

Distributor Playbook is core - bundled in every tier. Proton SoundSystem rules ship at launch; more distributors added throughout the year as the rule library expands. See pricing →   See the roadmap →

Made for the music.

Ship clean. Every time.

Beta is invite-only. The Distributor Playbook starts paying back on the first rejection it prevents - the days of release-cycle time you keep instead of lose.