Your releases, delivered to every store — from the platform that already runs your royalties.
Royalti generates ERN, MEAD, and PIE messages and ships them over SFTP, FTP, API, or HTTP — direct to ten DSPs, or through FUGA.
30 minutes · your catalog, not a canned demo
The release workflow is included for every tenant — DDEX delivery is included with every paid plan.
Two layers. No surprises.
Release workflow
Build releases with metadata, tracks, artwork, and splits. Submit, review, approve, and send feedback — all in the core platform.
DDEX delivery
Switch on delivery when you have stores to ship to. Royalti turns approved releases into DDEX-conformant messages and delivers them.
The release workflow stands on its own — delivery switches on when your plan includes it.
From approved release to live in store
Build the release
Metadata, tracks, artwork, and splits — pulled from the catalog you already keep in Royalti.
Submit and approve
Your team reviews, leaves feedback, and approves. Nothing ships by accident.
Generate the messages
ERN 4.3 release notifications, MEAD enrichment, and PIE party data — validated before they leave.
Deliver over your transport
SFTP, FTP, API, or HTTP. Store credentials stay encrypted at rest.
[Product screenshot — deliver over your transport]
Track every store
Per-store delivery status, with retries when a store hiccups.
[Product screenshot — track every store]
Built for catalogs, not one-off uploads
One catalog, no re-keying
Releases reuse the catalog and splits you already manage. Enter data once, deliver everywhere.
Direct deals and FUGA in one pipeline
Deliver direct where you hold DSP deals. Route through FUGA where you don't.
Know where every release stands
Delivery status per store, per release — not a black box.
Standards-conformant by default
Every message validates against DDEX schemas before delivery.
Credentials secured
Store credentials are encrypted at rest. Your keys stay yours.
Built on the standards your stores speak
DDEX-conformant message generation, validation, and delivery.
Already on FUGA? Keep it.
Royalti delivers to FUGA over FTP — metadata, artwork, and audio in FUGA's spec. From there, FUGA's network reaches 200+ stores. Direct deals and aggregator routing live in the same pipeline.
Delivery is half the story.
Most distribution tools stop at the store door. Royalti also ingests the royalties your releases earn — delivery, statements, and payouts in one system.
Common questions
Is DDEX delivery included in my plan?
The release workflow is included for every tenant. DDEX delivery is included with every paid plan (Starter and up) — no separate purchase.
Do I need my own DSP deals?
Deliver direct where you hold deals — your credentials, your terms. No direct deals? Route through FUGA instead.
Which standards and versions?
ERN 4.3 for releases, MEAD 1.1 for enrichment, PIE 1.0 for party data. Transports: SFTP, FTP, API, HTTP.
Can you deliver to Merlin?
No — Merlin isn't a delivery target. Royalti's Merlin integration ingests your deal and reporting data into royalty processing.
Put your next release in every store
Book a delivery walkthrough — 30 minutes, on your catalog. We'll map your stores, transports, and FUGA routing live.