The platform
Five portals over one system of record
Each portal is shaped around a job somebody actually does — approving a channel, disputing a claim, signing off a payout — and every one of them reads and writes the same data under the same rules.
Admin & Operations
Used by
Network operations — ops managers and executives, and the super admins above them
The control surface for the whole network. Channel lifecycle from request to delink, with token health, monetisation state and genre held as independent signals rather than one blunt idea of health.
- Channel register with onboarding and evaluation queues, and a delink ledger where tracking freezes on the delink date
- Move and Transfer executed as different things: a move carries all history across, a transfer only from the effective date forward
- Novations on a seven-day clock that auto-reverts when it runs out
- Bulk import with row-level validation, committed in batches of 100, warned when it would exceed the day's API quota
- Multi-step approvals with per-step SLA, and an append-only activity log of every mutation
Screens
14 routes- Dashboard/admin
- Channels/admin/channels
- Delinked channels/admin/channels/delinked
- Partners/admin/partners
- Approvals/admin/approvals
- Ownership changes/admin/ownership
- Novations/admin/novations
- Claims & disputes/admin/claims
- Token health/admin/tokens
- Suspected reuse/admin/videos/reuse
- Bulk import/admin/bulk
- Activity log/admin/audit
- Users & roles/admin/users
- Service settings/admin/settings
Partner Portal
Used by
The network's content partners — their admins and their finance contacts
Everything a partner is entitled to see about themselves, and nothing about anybody else. The tenant boundary is structural, not a filter someone remembered to apply.
- Their channels, their assets and their reports, scoped to their own tenant throughout
- An add-channel flow that refuses a channel already mapped to another partner and routes it to a transfer request instead
- An onboarding mirror showing the exact stage a request sits at and the data operations is judging it on
- Agreements with every version, effective window and signatory; commercials with strict effective dating
- Payouts settled T+15, in USD with the INR value at the contracted rate
Screens
12 routes- Dashboard/partner
- My channels/partner/channels
- Add a channel/partner/channels/add
- Onboarding review/partner/onboarding
- Transfer requests/partner/transfers
- Novation/partner/novation
- Agreements/partner/agreements
- Commercials/partner/commercials
- Payouts/partner/payouts
- Company profile/partner/company
- Videos/partner/videos
- Reports/partner/reports
Creator Studio
Used by
Creators and channel managers working inside a partner
Upload, get checked against the network before publish, and see exactly what was decided and why. The gate runs before anything reaches YouTube, not after a claim arrives.
- Every upload fingerprinted against the whole network on video and audio — never on thumbnails or titles
- Blocked uploads shown with the matching segments, the source asset and the partner who owns it
- A soft-review queue with segment-diff comparison; decisions write to the audit log and notify by email, WhatsApp and in-app
- Performance and earnings for the creator's own catalogue, with format split by aspect ratio rather than duration
Finance & Billing
Used by
Finance managers and executives who own the network's books
The commercial side of the network: what was agreed, what was invoiced, what was paid, and whether those three agree.
- Invoice register carrying revenue share, TDS, GST and the OCR verification outcome on the document
- Payout register with batch reference, bank status and a named reason behind every hold or failure
- Agreements bound to the enterprise CLM record with e-signature envelopes and version history
- Commercials with asset-level splits between network-owned and partner-owned material
- Reconciliation across platform-computed, platform-reported, invoiced and paid
- IP valuation export: video-level monthly revenue from publish date to today, for catalogue valuation
Analytics & Copilot
Used by
Analysts and anyone who has to explain a number to somebody else
The intelligence layer. Built to answer why a number moved, which is the question that follows every dashboard.
- Click a point on any chart and drill through to the assets that caused it
- Diagnostics that decompose a metric's variance into channels, assets and events
- Anomaly detection that names the detector that fired and the root cause it found
- Network-wide reuse intelligence: how often an asset was re-uploaded and on whose channels
- A copilot that answers from platform records and cites the record behind each claim
- A report builder with live preview and full-set export
Royalties & Invoicing
Used by
The settlement desk: royalty operations, finance, and the CEO who signs
The engine underneath the five portals. Ingestion, rate resolution, period close, approval and the bank file — with the working kept for every line.
- Revenue share resolved with the arithmetic shown, not just the final percentage
- Studio API against CMS on every line, flagged once the negative variance passes ten dollars
- Two FX rates per period: one values the revenue, one prices the payout
- Advances that hold a payout at zero until they are recouped
- Finance approves, then the CEO signs. Neither stage can be skipped
- Payment runs that produce a bank file, then reconcile the UTRs that come back
Screens
15 routes- Overview/royalties
- Period close/royalties/period
- Variance/royalties/variance
- Entities/royalties/entities
- Contracts/royalties/contracts
- Revenue share/royalties/shares
- Incentive slabs/royalties/slabs
- Currency/royalties/fx
- Ingestion/royalties/ingestion
- Invoices/royalties/invoices
- Payment runs/royalties/runs
- Reconciliation/royalties/reconciliation
- Advances/royalties/advances
- Ad-hoc payments/royalties/adhoc
- Reports/royalties/reports
Underneath all six
The parts that are shared, so the portals cannot disagree
A portal is a view with permissions, not a separate application with its own copy of the truth.
One dataset
255 channels, 25.2K assets and 25.4K videos, held once. A channel's genre split, monetisation state and token state are separate signals on the same record.
One rules engine
Fingerprint bands at 90% and 50%, the 7-day novation window, the $250 tracking floor and the $50 payout minimum are policy values, configurable in service settings and applied identically everywhere.
One clock
YouTube's daily reporting runs a day or two behind and revenue is audited to T-15; the newest delivered day is 2026-09-26. Every revenue surface repeats the lag next to the number rather than presenting it as today.
One audit trail
Append-only, each entry carrying actor, role, action, entity, before and after, and whether it came through the UI, the API, a bulk import or the system itself.
One quota
The YouTube API allowance is finite and spent by bulk actions. A run that would exceed what is left has to check the remaining budget before it starts rather than failing halfway through.
One settlement engine
Rates, incentives, management fees, advances and FX are resolved in one place. Finance, the partner portal and the royalties back office all read the same resolution rather than each computing their own.
Counts are read from the platform’s dataset. Policy values are the seeded defaults and are editable per deployment in Admin → Service settings.
Open the portals and look
The platform hub lists every portal with a demo account for each, so you can walk in as ops, as a partner, as a creator or as finance.