Media software development for streaming, catalogue and rights

Two estates that have to agree with each other. One delivers the content: ingest, transcode, package, encrypt, ship it to a player. The other decides who may be paid for it: the catalogue, the deals, the usage that comes back, the statement at the end. We build the operator's side of both. The subscriber facing app is its own build, with its own page, linked below.

  • OTT delivery and multi-DRM
  • Asset management and metadata
  • DDEX, ISRC and CWR aware
  • Module hours published
What this covers

Tell us what you are building

By submitting this form, I authorize Zyneto to collect and process my personal data in accordance with theZyneto Privacy Policy.

We reply to every enquiry within one business day.

What does media software development cover?

Media software development covers two different jobs. One is the streaming product: transcoding, DRM, players and apps. The other is the back office: who owns the recording, which territory the deal covers, and what the platform reported back. Streaming standards decide playback. DDEX and the identifiers decide whether a royalty statement is defensible.

Phase one hours
1,480 in the worked example
Timeline
14 to 22 weeks
Realistic band
1,200 to 2,100 hours
Modules scoped
7, each with its own range

Scope of the field

The six things media software development covers

Most buyers arrive wanting one of these six and find they need three. We build the operator's side of all six: the systems a media business runs on, not the app a viewer installs.

Audience

Which media operation are you running?

Six positions we are called from, and the system each is missing. Not a fit if what you want is the subscriber facing app itself.

02

Broadcaster or sports rights team

Live windows, blackouts, short lived rights. Missing: availability by territory and window held as data, not settled by phone.

03

Independent label or distributor

Statements arrive from a dozen platforms in a dozen shapes. Missing: reconciliation against what you delivered.

04

Music publisher or administrator

Works registered, shares split. Missing: money that comes back matched, because the identifiers never travelled with it.

05

Catalogue owner or rights fund

You bought on a model. Missing: actual earnings by track, territory and platform, the only test of that model.

06

Studio, podcast or creator network

Participations, residuals and per episode splits live in contracts as prose. Missing: one view of what each party is owed.

Delivery

The video pipeline, and why it is built before the app

An app in front of a pipeline that does not work yet is a demo. Prove one title end to end on the devices you support.

Ingest and transcode

One mezzanine in, a ladder out. Decide the ladder per title, because bandwidth goes on rungs nobody watches.

Packaging

CMAF so one set of segments serves both HLS and DASH. Two pipelines over one catalogue is deletable cost.

Encryption and DRM

Common encryption lets several DRM systems read one encrypted file, per ISO/IEC 23001-7:2023, which does not define a DRM system itself.

One licence service, not three

Widevine, PlayReady and FairPlay are the three major systems. Answered in three places they give three answers.

CDN and egress

Egress is usually the largest infrastructure line and the one with no owner. Attribute it per title.

Identifiers

The identifiers and formats your catalogue has to speak

Where money arrives unmatched, this is almost always why. Tested against the full HTML of the three top ranking pages on 2026-11-13, none contains DDEX, ISRC, ISWC or CWR.

ISRC, for a recording

Twelve characters for one recording, never a product or a composition: a five character agency prefix, two for the year, five the registrant cannot reuse that year (ISO 3901:2019).

ISWC, for the work

The identifier for a musical work, as distinct from ISRC which identifies a recording. One work, a hundred recordings, different payees.

UPC, for the release

The product a shop or platform sells. A release is neither a recording nor a work.

CWR, for publishing registration

Registers works and shares with societies, and is where claim conflicts surface. The build is the queue and the unmatched report.

DDEX ERN, to deliver a release

The current published version is ERN 4.3.2, and DDEX advises using the latest (DDEX knowledge base, read 2026-11-13).

DDEX DSR, to read what came back

There is no single DSR version: each profile is versioned on its own (DDEX knowledge base, read 2026-11-13). Ingest is per profile.

Rights and royalties

Why the back office decides everything downstream

The half of this subject none of the three top ranked pages we read on 14 November 2026 writes about, and the half that decides whether a media business can be audited. Six decisions, all taken early and all expensive to revisit.

Shares that do not sum

A split summing to 99.9 passes every screen and fails later against money already received. Validate on entry.

Controlled, non-controlled and black box

A share you do not control is a known gap, not an absence. Left absent it silently becomes yours.

The usage row is not the money row

Between a stream and a payment sit rate cards, thresholds, territory splits, conversion and recoupment. Store those lines.

Recoupment and advances

An advance is money already paid and recoupment earns it back, often at a different rate. Model all three first.

Currency, rate source and date

Name the source, name the date, store the rate on the line. Without that, two runs of one period disagree.

Identifiers are write once

Reassigning an ISRC breaks every historic match, with no repair that is not somebody's memory. Keep a mapping table.

Failure modes

What goes wrong, and the practice that prevents it

Six failure modes named plainly. Naming them is more useful than a list of reasons to pick us.

The first milestone is a screen

A dashboard renders months before anyone can send a statement. Make the first milestone a royalty run instead.

Availability decided by reading a contract

Territory and window rights live as prose, so a person answers whether a title is licensed. Hold them as data.

Unmatched revenue that nobody counts

Money that cannot be attributed shows up only when somebody asks. Report the unallocated balance and its age.

Claims kept in an inbox

A dispute with no status cannot be aged, so nobody can say how old the oldest one is.

One encoding ladder for everything

Bandwidth goes on rungs nobody watches and egress becomes the largest line with no owner. Decide per title.

Captions treated as files

A caption sitting beside a title rather than versioned with it means the wrong one ships, unprovably.

Decision

When to build a media platform and when to license one

The boundary between what you buy and what you build is the decision the project inherits.

License a packaged platform

Fastest to a first stream or a first statement, and right when your deals look like everybody else's.

Build custom

Right when the deals are the business: unusual splits, short windows, a calculation nobody sells off the shelf.

Hybrid, which is most of them

Packaged underneath, custom where your terms are unusual. We have no media client yet, so scope the custom half small.

Integration

The estate we expect to meet

Three families of system, and the constraint that decides the plan in each. A media build is a data modelling problem with integration around it.

What you already runWhat it isThe constraint that decides the plan
Collecting societies and registriesIn India, IPRS on the works side and PPL and Novex on the recording side. Internationally it is one society per territory and per right.Registration is a queue with an acknowledgement, not a file drop, so the build is the tracking and the unmatched report.
The moneyA payment provider for payouts, withholding and tax residency by payee, currency conversion with a stated rate source and date, and recoupment against advances.Payouts run through a licensed institution contracted in your name. We are not one and we do not hold the money.
Where the catalogue currently livesUsually a spreadsheet, sometimes several, occasionally a system nobody has admin access to any more.Expect inconsistent territory codes, artist names differing by punctuation, and more share columns summing to 99.9 than anyone admits.

The work and the recording are two different objects, and a system that stores one cannot pay the other. At ingest a platform report looks like it is about a track, which is why this gets collapsed, and the repair afterwards is a migration of every statement issued. On licensing, see how music licensing works for a streaming catalogue.

Standards

Which standards and rules will we be asked for?

Standards are what a platform or a rights holder asks you to hold. Statutes bind you whether anyone asks or not. Every row below was read at its primary source on 2026-11-13.

InstrumentWhat it forces the software to doWhen
DDEX ERN, version 4.3.2Deliver a release as one structured message instead of a bespoke CSV per partner. DDEX strongly advises implementers to use the latest version. Source: DDEX knowledge base.Ongoing. No release dates are published against ERN versions
DDEX DSR, versioned per profileConsume the usage and revenue a platform returns. There is no single current version: Architecture 1.4, Basic Audio 1.4, User Generated Content 1.4.1, Audio-visual 1.3 and Royalty Reporting 1.2 are versioned separately, so ingest is per profile, not one parser. Source: DDEX knowledge base.Ongoing. No dates are published for any part
ISO 3901:2019, the ISRCIdentify one sound recording and nothing else: not a product, a carrier, a composition or a performer. Twelve characters: a five character prefix from the International ISRC Agency, two for the year of reference, and five the registrant must not repeat inside one calendar year. Source: ISO catalogue and the ISRC Agency.February 2019, edition 3. Reviewed and confirmed in 2024, so it remains current
ISO/IEC 23001-7:2023, common encryptionSpecify common encryption for files based on the ISO base media file format, with the metadata that lets several rights management systems read one encrypted file or stream. AES-128, with counter mode and cipher block chaining as separate schemes. It explicitly does not define a DRM system. Source: ISO catalogue.August 2023, edition 4
RFC 8216, HTTP Live StreamingDefine the playlist and segment format Apple devices expect, at protocol version 7. It is an Informational document on the Independent Submission stream, not an IETF standard, which is why your device matrix rather than the specification is the real constraint. Source: RFC Editor.August 2017. No successor or update noted in the document
Directive (EU) 2019/790, Article 19Give authors and performers up to date, relevant and comprehensive information on the exploitation of their works at least once a year, covering modes of exploitation, all revenues generated and remuneration due, with a right to request further information from sub-licensees. Source: EUR-Lex.Member States had to implement by 7 June 2021, reaching earlier contracts from 7 June 2022
India IT Rules 2021, for OTT publishersClassify every programme as U, U/A 7+, U/A 13+, U/A 16+ or A, and show the rating with a content descriptor at its start. Parental locks from U/A 13+ upwards, a reliable age verification mechanism for A, three levels of oversight, and access services such as captions and audio description where feasible. Source: the Rules as updated to 6 April 2023, MeitY.Notified by G.S.R. 139(E) dated 25 February 2021

We hold no security certification or attestation of our own, and we will not imply otherwise. We are not a collecting society and not a licensed payments institution, so registration runs through a society and remittance through a licensed institution, both in your name. We build the record that lets you pass. For the metadata layer, see media asset management, metadata and storage in detail.

Transparency

The scope of a phase one, and the hours behind every module

We publish the hours: seven modules, each with its own range, and the arithmetic that adds them up. Delivery and encoding are scoped separately, and the fixed number follows discovery.

Phase one hours

1,480

The worked example, seven modules, each inside its own published range.

Typical timeline

14 to 22 weeks

To a royalty run somebody is willing to send, not to a screen that renders.

Useful hours

1,200 to 2,100

The realistic band across the scopes we see. Every module range is above.

What moves the hours, ranked
DriverHours
Whether works and recordings are already separateSplitting them later means reinterpreting every statement already issued, not adding a table. It moves the number more than any feature.Highest impact
Number of platform report formats to ingestHigh
Rate card and contract term complexityHigh
Whether advances and recoupment existHigh
Territories, currencies and societies in scopeMedium
Whether delivery and encoding are in scope at allVariable
Historic catalogue migration and its identifier qualityVariable
Hours by module
ModuleHours
Rights, party and share model180 to 380
Catalogue and identifier registry160 to 340
Deals, rate cards and territory windows200 to 440
Usage ingest and normalisation200 to 420
Royalty calculation engine240 to 520
Statements, recoupment and payouts180 to 400
Reporting, admin and integrations160 to 360

Phase one, added up

  • Rights and party model 200 plus catalogue and identifiers 180 plus deals and rate cards 240 plus usage ingest 220 plus royalty calculation 260 plus statements and payouts 200 plus reporting and admin 180 equals 1,480 hours. Every one of the seven sits inside its own published range above, so you can move any line and see what it does to the total.
  • The seven module ranges above span 1,320 hours with every module at its minimum and 2,860 with every module at its maximum. The realistic phase-one band across the scopes we actually see is narrower, 1,200 to 2,100 hours, because almost nobody takes every module at once.
  • Deliberately not in those hours, each its own decision: encoding, packaging and delivery, a subscriber facing app, and any migration beyond two years of historic usage.
  • Recurring rather than build: hosting, CDN egress, DRM licence fees and the payment provider's charges, which scale with catalogue and audience rather than headcount. No fixed price before discovery, but an hour band on the first call.

Delivery

How we deliver media software development

Five phases, each named by the artifact it hands you, so you can ask to see one.

  1. Phase 01

    Deal and rights inventory

    A written record of every deal term that affects a payment, which rights it covers, in which territories and for how long, read out of the contracts.

  2. Phase 02

    Identifier quality report

    How much of the catalogue carries a valid ISRC, ISWC and UPC, how much is duplicated, and how much of last year's usage can be matched.

  3. Phase 03

    One period, calculated twice

    A closed period run through the new engine alongside whatever produced the last statement, with the differences explained line by line. This is the first thing anyone trusts.

  4. Phase 04

    Statement pack

    Statements generated from stored calculation lines, with recoupment applied, an unallocated balance reported, and every figure traceable to the usage rows behind it.

  5. Phase 05

    Handover pack

    Runbooks, the rate source and conversion policy documented, source in your repositories from day one, and the society and payment relationships in your name.

Frequently Asked Questions

What is media software development?

It is the building of the systems a media business runs on, not the content itself. Six areas cover almost all of it: streaming and OTT delivery, content and asset management, production workflow, monetisation and adtech, audience analytics, and rights and royalty reporting. The first four are what a viewer touches. The last two decide whether you can say who is owed what.

What types of software do media and entertainment companies use?

A delivery stack that transcodes, packages, encrypts and ships video or audio to players. An asset management system holding masters, proxies, versions, captions and artwork with searchable metadata. Production and review tools. A monetisation layer for subscription, advertising and transactional windows. Analytics. And underneath it a catalogue, rights and royalty back office, bought last and needed first.

Should we license a streaming platform or build one?

License when your deals look like everybody else's and speed matters more than fit, remembering you inherit the product's data model with it. Build when the deals are the business: unusual splits, short windows, a calculation nobody sells off the shelf. Most operators end up hybrid. Settle that boundary before either side is built: moving it later rewrites both.

Which DRM systems do we need, and can one encrypted file serve all of them?

Widevine, PlayReady and FairPlay are the three major systems. One encrypted file can serve several of them: ISO/IEC 23001-7:2023 specifies common encryption for files based on the ISO base media file format, with the metadata that lets multiple rights management systems read the same encrypted stream, and it explicitly does not define a DRM system. So the work is one encode and one licence service, not three of each.

What is DDEX, and do we have to support it?

DDEX is the set of message standards the music supply chain trades on. ERN delivers a release, and the current published version is 4.3.2, which DDEX advises implementers to use. DSR brings usage and revenue back and has no single version: each profile is versioned on its own, so ingest is per profile. None of it is law. It is the price of trading at scale.

What information does the law require a royalty statement to contain?

In the EU, Article 19 of Directive (EU) 2019/790 requires authors and performers to receive up to date, relevant and comprehensive information on the exploitation of their works at least once a year, covering modes of exploitation, all revenues generated and remuneration due. Where rights were sub-licensed they can request further information from sub-licensees. Member States had to implement it by 7 June 2021, reaching earlier contracts from 7 June 2022.

How long does phase one of a media platform build take?

For the catalogue, rights and reporting estate: seven modules, a worked example of 1,480 hours on this page, module ranges spanning 1,320 to 2,860, and real scopes landing between 1,200 and 2,100. Calendar is 14 to 22 weeks to a first royalty run somebody is willing to send, not to a screen that renders. Delivery is scoped separately.

What happens next

Four steps with a time attached, so a call has a known shape.

  1. A 30 minute technical call

    Bring one platform report, one deal, and the last statement you had to explain to a rights holder. Those three beat an hour of description.

  2. A written read within three working days

    At no charge. One page on whether your works and recordings are separable, where your identifiers are weakest, and an hour band for phase one.

  3. A paid discovery

    Two to three weeks, fixed fee, reading the deals and profiling identifier quality. Output is the inventory, the quality report and a costed plan.

  4. One period, calculated twice

    Phase one starts by running a closed period through the new engine alongside whatever produced the last statement.

Start with the deals, not the dashboard

Paid discovery runs two to three weeks and produces the deal and rights inventory, the identifier quality report and a costed phase-one plan. It is credited against phase one if you proceed.

  • No fixed quote before discovery
  • A written read within three working days
  • Module hours published, every range shown

Our Success Stories

Real feedback from the people we've proudly partnered with.

Brooklyn Foster profile

Brooklyn Foster

Sales Director |Cintas

United States

GoodFirms
"

Zyneto Global Technologies provided excellent project management and technical expertise throughout the engagement. The team was responsive, collaborative, and adaptive, ensuring the project met our expectations and set a strong foundation for future growth.

"
Verified Review
Rating: 5 out of 5
Krystian Chlebek profile

Krystian Chlebek

Founder & CEO |Moneteo

TechBehemoths
"

We engaged Zyneto to design and develop a custom web platform for Moneteo, aimed at improving project management, data tracking, and collaboration across internal teams and external partners. Their work included full-stack web development, custom modules for workflow automation, API integration, and comprehensive testing.

"
Verified Review
Rating: 5 out of 5
Kevin Scott profile

Kevin Scott

CEO |E-Commerce Platform

Clutch
"

Overall, their responsiveness and timely deliveries contributed positively to the project's success. The client achieved better data management and quality. The service provider delivered the project on time and ensured prompt responsiveness throughout the engagement. Their innovative approach was outstanding.

"
Verified Review
Rating: 5 out of 5

Explore further

Go deeper

Build the system

Data and decisions

Adjacent builds

Worth reading next

WhatsApp
Email
Book a Meeting