Confirm rights and approval
Record who controls the recording, artwork and metadata, and who is authorized to submit or change each release.
For labels and multi-artist teams
Run releases like a system.
Build one repeatable operating rhythm for rights, metadata, files, release readiness and catalog continuity—then review the current Mazufa label account path when your team is ready.
Account functions, destinations, costs, deductions, timing and eligibility follow the current plan, applicable agreement and platform review. This page does not create an account.
Rights authority
Release metadata
Catalog continuity
Review & follow-up
Four controls before every delivery.
A strong label workflow starts with what your team can verify—not with an unsupported promise about stores, timing or revenue.
Freeze the release record
Check artist names, titles, contributors, identifiers, territories and version details against the approved source.
Package files and timing
Match audio, artwork, credits and planned dates before submission; allow for delivery queues and destination review.
Monitor the catalog
Keep a private record of identifiers, delivered metadata, current status and any approved correction or migration.
The operating rhythm
One path, every release.
- Collect authority and source evidence.
- Prepare accurate metadata and assets.
- Review the current plan and agreement.
- Submit only through the authorized account path.
- Monitor status and document approved changes.
Release-room checklist
What the team should have ready.
- Final audio and artwork files
- Approved artist and release names
- Contributor and rights information
- Existing ISRC/UPC details when applicable
- Territory and version decisions
- Planned date with review time
- Current agreement and service choices
- Private change and approval record
Choose the account that matches the work.
The account choice changes the registration profile. It does not promise acceptance, destinations, timing or commercial results.
Artist account
For an individual artist, band or project managing its own releases.
- One artist or project context
- Release preparation workflow
- Current agreement applies
Label account
For a label or team preparing releases for more than one artist or project.
- Label registration profile
- Multi-project working context
- Current agreement applies
Questions label teams ask first.
Does a label account guarantee delivery to every destination?
No. Available destinations and processing depend on the current plan, release details, territory, eligibility and each destination’s review.
Can we move a catalog without losing its history?
Continuity can depend on correct identifiers, matching metadata, rights, destination rules and timing. Preserve the current records and review the migration plan before changing delivery.
Does Mazufa promise a release date or revenue result?
No. Dates depend on readiness, delivery and platform review; revenue depends on actual usage, territories, rights, reporting and applicable terms.
What should we review before registration?
Review rights authority, the current plan and agreement, available destinations, optional services, takedown conditions, reporting, payments and privacy choices.
Ready for the next step?
Bring your catalog discipline. Choose the label path.
Start from verified information, keep the campaign source, and review the current terms before continuing.