Skip to content
Sign up
Docs
Close menu

Revelator Alternative for Labels and Distributors

Short answer: Revelator and LabelGrid sell the same shape of thing, a platform for a business that distributes other people’s music, a white-label configuration of it, and an API on top. The argument is not about whose product list is longer. It comes down to where each company publishes its price, how a developer reaches a test environment, and one distribution clause. Imprint, our white-label portal, is by waiting list and scoped at onboarding rather than published. Every Revelator value in the table below is from their own published pages, read 23 September 2026.

Where does each company publish its price?

Revelator’s Terms say “Current fee schedules are available on the Site or in your Dashboard” and, in the distribution appendix, “These fees may be amended from time to time by us without notice to you”; their 32 distinct captured pages, read 23 September 2026, carry no price for Revelator Pro, the Revelator API or the white-label platform, and their own published site index at revelator.com/llms.txt lists no pricing page. At LabelGrid every self-serve distribution plan and every API tier is priced on our pricing page, including the Custom Distribution and API starting prices, and Imprint is by waiting list and scoped at onboarding rather than published, which is the half of this axis we concede. The claim is about where each company publishes, and nothing wider.

3

Products on one backend

7

Free-trial days on self-serve distribution plans

100%

Yours on your own DSP deals, on Custom Distribution and the API tiers

2017

Founded

SOURCED ROW BY ROW

Row by row, from their own pages

Each Revelator value below is taken from one of their own published pages, linked beneath the table with the date we read them. A dimension their pages do not state is left out rather than guessed at, which is why some rows a sales deck would happily fill are missing here.
FeatureLabelGridRevelator
What the company sellsThree products on one backend: self-serve distribution for labels and artists, Imprint the white-label portal, and Engine the APIRevelator Pro, Revelator API, Revelator Wallet, white label
Where the price is publishedEvery self-serve distribution plan and every API tier is priced on the pricing page, including the Custom Distribution and API starting prices; Imprint is by waiting list and scoped at onboarding rather than publishedFee schedule lives in the Site or Dashboard and may be amended without notice
What the percentage is a percentage ofYou keep 85% on Solo and Basic and 90% on Pro; from Custom Distribution and the API tiers up you keep 95% of standard-DSP royalties earned through LabelGrid's own deals and 100% of what you earn on your own. Our Terms state accounting fees in a range of 0-20% of net payable revenue, depending on the plan100% of Revelator’s actual receipts, minus disbursement fees it sets
Your own DSP deals or the platform'sDeliver on LabelGrid's own standard-DSP deals and keep 95%, or on your own deals through SOBO and keep 100% — on Custom Distribution and the API tiers onlyDeliver on your own DSP deals or on Revelator’s
API documentationPublic REST documentation for Engine, readable without an account, plus an open-source MCP server (MIT) listed on the public MCP registryPublic API documentation at api-docs.revelator.com
How a developer gets a test environmentThe sandbox is enabled as part of the API upgrade, so it opens once the plan is active; an active, paid API plan is required for both the sandbox and the MCP serverTesting runs in production on a sandbox account requested by email; the separate staging environment is retired
ExclusivityThe LabelGrid distribution licence is global and non-exclusive: you may distribute the same content elsewhere at the same time, and no exclusivity survives terminationThe licence is non-exclusive; the terms separately ask the customer not to use another distributor for the DSPs Revelator serves
Account structureImprint composes each end customer as a full workspace with the same capability, side by side rather than nested under a parent; a label workspace and an artist workspace get the same surface, and only the reseller sees across workspacesParent-child client and end-user accounts, with enterprise client endpoints in the API
Royalty accounting and splitsStatements, payouts and royalty transparency in the platform, with automated splits and artist royalty management from Basic up and on every API tier; Solo is the only distribution plan without themAutomated royalty runs, approvals, rights-holder portal
Catalogue reviewEvery release on a distribution plan is manually reviewed for quality, metadata and rights before delivery, at no extra cost, unless the account distributes only through its own direct dealsPublished content policy with periodic catalogue review
Minimum payout balanceLabelGrid’s Terms allow a minimum payout threshold; if one applies to your account we let you know, and a balance below it can carry forward to a later payment cycle; no figure is publishedPublished $5.00 minimum balance for a PayPal withdrawal (Terms § 7.4)

Each of the 11 Revelator values above is sourced from their own published pages, read 2026-09-23: api-docs.revelator.com/en/getting-started, revelator.com/anti-fraud-policy, revelator.com/content-policy, revelator.com/features/royalty-accounting, revelator.com/product/revelator-api, revelator.com/product/revelator-pro, revelator.com/terms-and-conditions. Dimensions we could not source from one of their primary pages are omitted rather than guessed.

WHAT YOU CAN CHECK FIRST

How a developer gets a test environment

Both companies publish API documentation without a login, and theirs is substantial: the Revelator getting-started page covers authentication, account signup, permissions, invitations and enterprise client endpoints. That half is parity, and anyone telling you otherwise has not read it.

The route to credentials is where the two diverge. Their getting-started page says “All testing should be done in a production environment using a dedicated sandbox account. If you do not already have a sandbox account, please contact us at [email protected] to create one”, adds that a staging environment “is no longer supported”, and their API product page tells you to “contact your Revelator representative” for sandbox access and credentials.

At LabelGrid the API tier prices are published and the sandbox is enabled as part of the API upgrade, so it opens once your plan is active. The limit is worth saying plainly: a B2B account here begins with a conversation too, with onboarding screening and KYC or KYB checks, and the sandbox is not a pre-purchase trial. What you can read before any of that is the price and the documentation.

What you can read today

Published plan prices

Every self-serve distribution plan and every API tier carries its price on our pricing page.

Public API docs

The Engine REST documentation is readable without an account and without a sales call.

Sandbox with the plan

The sandbox is enabled at the API upgrade, so it opens once the plan is active.

Open-source clients

Our MCP server is MIT-licensed on npm and listed on the public MCP registry.

YOUR CATALOGUE, YOUR SITE

Run the catalogue from your own domain

The LabelGrid Tools plugin syncs releases, artists and download gates into WordPress every six hours, then builds release landing pages with Spotify pre-saves before release day and gated downloads afterwards. It is available to every account at no extra cost and needs no API plan. The same public API carries an open-source MCP server and a companion CLI.
See the WordPress plugin

HOW THE MONEY WORKS

What the percentage is a percentage of

Our rate is a published plan term. You keep 85% on Solo, 85% on Basic and 90% on Pro; from Custom Distribution and the API tiers up you keep 95% of standard-DSP royalties earned through LabelGrid’s own deals and 100% of what you earn on your own. Our Terms state accounting fees in a range between 0 and 20% of net payable revenue depending on the plan.

Revelator’s distribution terms pay “one hundred percent (100%) of our actual receipts ... minus any applicable disbursements of funds fees as to be determined by us from time to time”, with the Service Fee charged separately. That is the same shape as ours, a platform fee alongside a share of what the company receives. So the useful question is not whose definition of receipts reads better; it is where you can read the number before you sign.

Both licences are non-exclusive and ownership stays with you. Their distribution terms add that “you agree not to use any other Digital Distribution service with respect to any DSPs except only to the extent that an Internet consumer store is no longer a DSP hereunder”. Ours is global and non-exclusive, the same content may go elsewhere at the same time, and no exclusivity survives termination.

Across the distribution plans

Splits from Basic up

Royalty splits run automatically on Basic, Pro, Custom Distribution and every API tier; Solo does not include them.

Payout rhythm

Statements generate from the 21st, payments are initiated between the 3rd and the 14th of the next month, and funds land in 3 to 7 business days.

Trial and review

The self-serve distribution plans start with a 7-day free trial, and a person reviews every release before delivery unless the account distributes only through its own direct deals.

ACCOUNT STRUCTURE

Two ways to shape a reseller platform

Both companies sell a white-label configuration of the same platform, so the question is how end customers sit inside it. Neither shape is free of cost to the operator, and this is the section where we say what ours costs.

Their shape: parent and child

Revelator’s white-label page offers a fully branded platform with “custom domains, subdomains, and a personalized user interface”, a “Label and Artist Portals” section to “Manage labels and artists at any scale”, and their distributor page offers “unlimited label and artist portals”. The structure is stated as parent-child: their Anti-Fraud Policy is written around “parent-child accounts” and a Client answering for “their end users/sub-accounts”, and their API documents an enterprise client model. Their help centre publishes operator documentation for running it.

Our shape: workspaces side by side

Imprint puts your brand on your own domain and composes each end customer as a full workspace with identical capability, side by side rather than nested under a parent. A label workspace and an artist workspace get the same surface, and you are the one who sees across them. That costs you something real: a label customer does not inherit a supervised tier of artists beneath it, so an operator who wants that hierarchy is better served by a parent-child model. Imprint is by waiting list and scoped at onboarding.

When the ladder does not fit

The published ladder is the floor of a conversation rather than its ceiling. Label limits run Solo 1, Basic 3, Pro 5 and Custom Distribution 50. On the API tiers the same meter runs higher, at 5 on Starter, 25 on Growth and 100 on Scale. Each standard API tier can add one pack of extra label portals through support, sized by tier at 5 on Starter, 10 on Growth and 25 on Scale. Past one pack the answer is the next tier up rather than a second pack, and past the top of the published ladder it is a custom deal, whose numbers are not public.

An operation running thousands of single-label artists is exactly the case bulk label pricing exists for, and the pricing page is where that conversation starts. The WordPress plugin and the public API both serve release pages and pre-saves from the same data, so the catalogue can live on your own site as well as in the portal.

FOR PEOPLE WHO BUILD

What the API costs and what it meters

Engine is a documented REST API with three published tiers plus Custom API, and every starting price is on the pricing page. The documentation is readable without an account. The sandbox is enabled as part of the API upgrade, so it opens once the plan is active rather than before purchase, and an active paid plan is required; the 7-day trial on the self-serve distribution plans carries no API or sandbox access.

Three meters decide which tier you are on: a track limit, a label limit counted in registered labels, and a monthly cap on royalties processed of $35,000, $115,000 or $350,000. Crossing the cap carries no overage fee, because sustained excess is a conversation about the next tier rather than a bill. Custom API sets its own royalty cap with a per-track overage.

LabelGrid supports DDEX ERN 3.8.2, 4.3.0, 4.3.1 and 4.3.2 on delivery, on every distribution plan. DDEX ERN import, as a one-time catalogue load or a continuous SFTP or S3 feed, runs on the API plans and on Custom Distribution, with a one-time setup fee wherever it is enabled. Revelator publish catalogue import and export “via DDEX, CSV, or XML”, and a 2026 newsroom post of theirs says they “upgraded all Spotify distribution feeds to the latest DDEX ERN 4.3 standard”.

The Engine meters

Published tiers

Starter, Growth and Scale carry their prices on the pricing page, and Custom API its starting price.

Royalty processing cap

Up to $35,000, $115,000 or $350,000 in royalties processed a month by tier, with no overage fee when you cross it.

Registered labels

5 on Starter, 25 on Growth and 100 on Scale, counting every registered label on the account.

Open-source tooling

An MIT MCP server on npm, listed on the public MCP registry, plus a CLI over the same API.

WHERE THEY WIN

Where Revelator is the better choice

All three of these are about what a company publishes, which is the currency the rest of this page is denominated in. Each one is a document of theirs you can read today, and on the first of them they beat us outright.

A published payout floor

Revelator’s Terms § 7.4 allow a withdrawal to PayPal “once your Revelator Credit Account balance has a minimum amount of five dollars ($5.00 U.S.)” plus any applicable PayPal transaction fees. That is their published floor on the PayPal route rather than on every payout method. LabelGrid’s Terms allow a minimum payout threshold; if one applies to your account we let you know, and no figure is published. Theirs is the figure you can read before you sign, and on this row they win.

Payout methods by country

Their help centre publishes a country-by-country table of supported payment methods, under the columns COUNTRY, WIRE TRANSFER, E-CHECK / LOCAL BANK TRANSFER, CHECK, PAYPAL and INTERCASH, with their own caption noting that “Thresholds change periodically, so use the following table as a general guideline.” Their global payments page names Tipalti, PayPal and Bamboo behind it. If how a collaborator in a particular country gets paid decides your choice, go and read that table before you commit to anyone.

A published integration roadmap

Their DSP help article carries sections headed “Upcoming DSPs - Integrations in Progress” and “Negotiating / Prospective DSPs”, so a prospect can see which platforms are being worked on and which are still under discussion. Their own headings say those are not live yet, which is the point: the roadmap is published as a roadmap. If that visibility matters to your planning, it is a reason to pick them.

We keep this section in every comparison we publish; a comparison you cannot trust is worth nothing.

WHICH ONE TO PICK

Choosing between the two

Choose Revelator for the three things their own documents settle before you sign. Their Terms § 7.4 put a $5.00 minimum balance on a PayPal withdrawal. Their help centre publishes a country-by-country table of payout methods, so you can check how a collaborator in a particular country gets paid. Their DSP article publishes which platform integrations are in progress and which are still being negotiated. Each of those is a published artefact you can read before you commit.

Choose them too if you want a parent-child account tree, where a label customer sits above a supervised tier of artists, rather than a flat set of workspaces.

Their product pages also cover more ground than this comparison does. Anything we have not sourced from them here is on their own site, and that is the place to read it.

Choose LabelGrid if

Price before contact

Every self-serve plan and every API tier carries its price on our pricing page.

You are integrating

The docs are public, the tiers are priced, and the sandbox opens once your plan is active.

Flat fee, published rate

From Custom Distribution up you keep 95% on our standard-DSP deals and 100% on your own.

Non-exclusive licence

You may distribute the same content elsewhere at the same time, during the term and after it.

ASK BOTH OF US

Seven questions for any platform here

Ask these of us as readily as of them. The answers are the comparison.

01Ask where the fee schedule lives, on a public page or in the dashboard after signup, and whether the company reserves the right to amend it without notice to you.

02Ask what the percentage is a percentage of: gross receipts, receipts net of third-party deductions, or revenue after a separately charged platform fee. Then ask for that definition in writing.

03Ask whether manual release review is included on every plan or sold as an add-on, and who does it, because a delivery rejected three weeks before release date costs more than the fee.

04Ask how you reach a test environment: is there a sandbox, does getting to it mean emailing a representative, and does it open before or after the plan is paid for?

05Ask which DDEX ERN versions are supported per feed rather than in general, whether catalogue import over DDEX costs extra, and which plans it is available on.

06Ask what happens to your catalogue if you leave: does ownership stay with you, is the licence non-exclusive, and may you use another distributor for the same stores at the same time?

07Ask what happens to your integration when the API changes: whether breaking changes are versioned, where the changelog is published, and whether the client libraries are open source or closed.

Questions people ask about both

Who runs Revelator, and who runs LabelGrid?
Revelator’s Terms and Conditions are published by “Revelator Enterprises, Inc.”, described there as a US entity, with a legal notice address at “1440 Central Ave, Suite 14, Albany, NY, 12205, USA”. The footer of every captured revelator.com HTML page reads “© 2026 Revelator, Ltd”, and both names are recorded here as they appear. Those Terms carry “Effective from June 6, 2026”, which is the version quoted throughout this page, and their about page says the company is “Led by Bruno Guez”. LabelGrid has been going since 2017, is based in Denver, Colorado, and every customer contracts with Label Grid LLC.

What does each company actually sell?
Revelator publish three named products plus a white-label configuration of the platform. Revelator Pro, which their page describes as “one platform to manage digital assets, supply chain, rights management, business intelligence, financial reporting, and royalty payment distribution”; the Revelator API; and Revelator Wallet. Their white-label page adds client features “like Feature FM Smart Links, AI mastering, Dolby Atmos, and our marketplace access”, and their help centre carries a White-label & Platform Admin section for operators, covering branding, custom email, Google login, client management and admin permissions. LabelGrid sells three products on one backend: self-serve distribution for labels and artists, Imprint the white-label portal, and Engine the API.

Where do I find Revelator’s pricing?
Their Terms say “Current fee schedules are available on the Site or in your Dashboard”, and the distribution appendix adds “These fees may be amended from time to time by us without notice to you”. Their 32 distinct captured pages, read 23 September 2026, state no price for Revelator Pro, the Revelator API or the white-label platform, and their own published site index at revelator.com/llms.txt, 83,481 characters of it, indexes their features, products, solutions, label services, blog, newsroom, glossary and webinars, with no pricing page among them. Currency figures do appear in their documents, including a payout threshold; none of them is a price for a Revelator product. At LabelGrid every self-serve distribution plan and every API tier is priced on our pricing page, including the Custom Distribution and API starting prices, while Imprint is by waiting list and scoped at onboarding.

Which company pays out more?
That depends on the plan and on whose DSP deals you deliver under, and each company defines the base itself. Revelator’s distribution terms pay “an amount equal to one hundred percent (100%) of our actual receipts in connection with the Digital Distribution of your Release(s) minus any applicable disbursements of funds fees as to be determined by us from time to time”, with their Service Fee charged separately. At LabelGrid you keep 85% on Solo, 85% on Basic and 90% on Pro; from Custom Distribution and the API tiers up you keep 95% of royalties earned through our own standard-DSP deals and 100% of what you earn on your own, and our Terms state accounting fees in a range between 0 and 20% of net payable revenue depending on the plan. On bank-side charges the two documents agree: their Terms say “You are always responsible for paying all applicable transaction fees, bank fees, or other charges related to your withdrawal of your funds”, and ours put the same bank-side charges on the customer.

Do both companies have a usable API?
Both publish API documentation without a login. Theirs is at api-docs.revelator.com and opens with “The Revelator API enables partners to provide Revelator functionality to artists or other collaborators directly from their own applications”, and their API product page lists “Monitor delivery status and DSP ingestion with webhook support”. The routes to a test environment differ. Their getting-started page says “All testing should be done in a production environment using a dedicated sandbox account. If you do not already have a sandbox account, please contact us at [email protected] to create one”, notes that a staging environment “is no longer supported”, and their API product page tells you to “contact your Revelator representative” for sandbox access and credentials. Engine’s documentation is public, its three tiers and the Custom API starting price are on our pricing page, and its sandbox is enabled as part of the API upgrade, so it opens once your plan is active.

Can I deliver on my own DSP deals?
Yes on both sides. Revelator’s API product page offers “Deliver to DSPs using your own deals or Revelator’s deal”. At LabelGrid, Custom Distribution and the API tiers carry the same choice: deliver on LabelGrid’s own standard-DSP deals and keep 95%, or on your own deals through SOBO and keep 100%. SOBO is available on Custom Distribution and the API tiers, not on Solo, Basic or Pro. On metadata standards, LabelGrid supports DDEX ERN 3.8.2, 4.3.0, 4.3.1 and 4.3.2, and a 2026 Revelator newsroom post says they “upgraded all Spotify distribution feeds to the latest DDEX ERN 4.3 standard”. Their catalogue pages offer import and export “via DDEX, CSV, or XML”; DDEX ERN import at LabelGrid runs on the API plans and on Custom Distribution, with a one-time setup fee.

What happens to my catalogue if I leave?
Ownership is settled on both sides. Revelator’s Terms say “nothing in these TOS shall constitute a transfer to us of ownership of any User Content”, and the licence they take is “non-exclusive, transferable, royalty free”. Their distribution terms then add, in the authorisation section, that “you agree not to use any other Digital Distribution service with respect to any DSPs except only to the extent that an Internet consumer store is no longer a DSP hereunder”. The LabelGrid licence is global and non-exclusive, the same content may be distributed elsewhere at the same time, and no exclusivity survives termination. Taking a release down with us is self-serve: deselect the outlets on the release and save, and full removal across platforms typically takes two to three weeks, with royalties earned before removal still paid.

How do the white-label account structures differ?
Revelator’s white-label page offers “Create a fully branded platform with custom domains, subdomains, and a personalized user interface” and a “Label and Artist Portals” section to “Manage labels and artists at any scale”. The structure is stated as parent-child: their Anti-Fraud Policy is written around “parent-child accounts” and a Client answering for “their end users/sub-accounts”, and their API documents an enterprise client model. Imprint puts your brand on your own domain and composes each end customer as a full workspace with identical capability, side by side rather than nested under a parent, so a label workspace and an artist workspace get the same surface and you are the one who sees across them. Both shapes work, and they suit different operations.

What are the payout minimums and methods?
Revelator’s Terms § 7.4 allow a PayPal withdrawal “once your Revelator Credit Account balance has a minimum amount of five dollars ($5.00 U.S.)” plus PayPal’s transaction fees, and restrict withdrawals to a PayPal account belonging to the authorised user of the Revelator Credit Account. That $5.00 is their published floor on the PayPal route rather than on every method. Their help centre publishes a country-by-country table of supported methods under the columns COUNTRY, WIRE TRANSFER, E-CHECK / LOCAL BANK TRANSFER, CHECK, PAYPAL and INTERCASH, which their own caption calls “a general guideline”, and their global payments page names Tipalti, PayPal and Bamboo as the providers. LabelGrid pays monthly: statements generate from the 21st, payments are initiated between the 3rd and the 14th of the following month, and funds arrive three to seven business days after that. Our Terms allow a minimum payout threshold; if one applies to your account we let you know, and no figure is published. On a floor you can read before you sign, though, theirs is the published figure and ours is not.

What can I check about LabelGrid before I talk to anyone?
The price of every self-serve distribution plan and every API tier, including the Custom Distribution and API starting prices, on our pricing page. The Engine REST documentation, readable without an account. Our MCP server on npm under the MIT licence, listed on the public MCP registry, and the CLI over the same endpoints. Our Terms of Service, including the 0 to 20% accounting-fee range and the non-exclusive licence. Our WordPress plugin in the plugin directory, free to every account and needing no API plan. What you cannot read in advance is an Imprint quotation or a custom-deal number, and a B2B account here starts with a conversation, onboarding screening and KYC or KYB checks, which is why the sandbox opens once the plan is active rather than before.

See the price before you talk to us

Every self-serve distribution plan and every API tier is priced on the pricing page, the Engine documentation is public, and Imprint is by waiting list and scoped at onboarding. Each Revelator value in the table above comes from one of the pages linked beneath it, read on 23 September 2026. If any of it is wrong, tell us and we will fix it.

See API Pricing