PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project

Feature scope - proposed scope

White Label Live Streaming App Features: Rooms to Payouts

This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.

Scope areas for this kind of build

White Label Live Streaming App Features by Role

One monorepo, three surfaces: a 44-route web app that viewers and hosts share, a 15-section operator panel, and an Expo mobile build that handles the core journeys.

The Viewer

  • Finds rooms by format, country and language, chats live, sends gifts from eight categories including combo and luxury, scrolls short videos and a square feed, and keeps coins and other balances in one wallet. Following, blocking, mutual followers, profile visitors, a top-fans list ranked by gift value, search by username or hashtag and a nearby-rooms view come with it.

The Host

  • Starts a broadcast in any of fifteen formats, from solo video and solo audio to voice rooms, multi-guest, co-host, panel, party, karaoke, gaming, talent, talk show, dating, private, subscriber-only and events. Runs seats and co-hosts, starts PK battles, watches diamonds build up and follows them all the way to a withdrawal request.

The Family

  • A leader runs one family, chooses among three join policies and hands out leader, co-leader, elder and member roles. Contribution is tracked, a treasury accumulates and the group enters family-versus-family battles with rankings. Where gifting earns the money, families give people a reason to return to the same community.

The Moderator

  • Handles reports on seven kinds of content, issues strikes with violation types, processes appeals, records bans, mutes and shadow bans, maintains a keyword blocklist and reads a full action log. Rooms can be watched while they run, because on a live platform the trouble starts before anyone files a report.

The Operator

  • Works across fifteen admin routes: host applications, withdrawal approvals, room monitoring, report queues, the gift and game catalogues, agency approvals, the audit trail and revenue settings. The dashboard opens on eight KPI cards and revenue charts, so the morning check takes minutes.
  • Six notification categories with quiet hours, support tickets that take attachments and carry an SLA, and thirteen legal and policy pages are part of the same build.

How a Gift Travels From Signup to Payout

One transaction followed from the first broadcast to a cash withdrawal, showing who gets what along the way.

A host picks a format and goes live

  • After choosing from the fifteen formats, the host receives a publisher token issued by the server for your own Agora account, so the step from tapping a button to being on air is a real, authenticated sequence. Voice rooms bring seats, multi-guest and co-host formats add more publishers, and events have their own type.

Viewers arrive through discovery

  • Rooms surface by format, country and language, with nearby rooms sorted by distance. Inside, chat, follows and the top-fans list all share one session, which makes the room a place to belong rather than a stream with a comment box beside it.

Money becomes coins

  • Viewers buy coins through Stripe, on a merchant account that belongs to you. That is the one place real currency enters the system, and it is why coins are kept apart from anything a host earns. Mixing the two is how many virtual economies end up impossible to audit.

The split happens inside the gift

  • When a gift is sent, one database transaction debits the viewer, divides the value and credits the host. The defaults are 30 percent to the platform, 10 percent to the agency and 60 percent to the host, and each can be varied by room type, gift category and region. Because nothing waits for a month-end reconciliation, a host's share is visible immediately.

Battles give gifting a reason

  • PK battles come in six formats: one-versus-one, team, room, family, agency and tournament. Each is scored live on the gift value a side attracts, with winner determination and revenge matches. Leaderboards rank by gift value, and family and agency contests feed their own tables.

Diamonds turn into beans, then into cash

  • Gifts land as diamonds, diamonds convert to beans, and beans leave as currency less a 5 percent fee once an operator has approved the request. Four balances exist because each answers a separate question: what was bought, what was earned, what can be withdrawn and what drives ranking.

The operator sees the whole loop

  • Host applications, withdrawals, room monitoring, reports, both catalogues, agency approvals and the audit trail sit behind fifteen routes, topped by a dashboard of eight KPI cards and revenue charts.

Why Each Module Is in the Base Build

Every line below is there because a broadcasting business struggles without it, and not because a feature checklist demanded it.

The Technology Underneath the Features

What the platform runs on, and what that means for whoever maintains it once it is yours.

The wallet is where the years go

  • Everything is mainstream and easy to hire for, with ordinary PostgreSQL beneath it. A technical buyer running diligence can read all of it.

Boundaries we state in writing for your build

The build's own documentation grades it and lists work to finish before public launch. We put that list here so it reaches you before your security review does.

Pre-launch work, named in advance

  • No test suite. The repository holds no test files today. Unit, integration and end-to-end coverage is scoped work, with a testing roadmap already written. Budget for it before real traffic arrives.
  • No migration history. The schema is applied with a direct push, which stops being safe as soon as production data exists. A proper migration history is small, early work and belongs before your first real user.
  • No observability. There is no structured logging, APM, metrics or alerting. On a live platform that means guessing during the exact incident where guessing costs the most.
  • One instance only. The Socket.IO Redis adapter that multi-instance running requires is not installed. Connection pooling and clustering come with it, and all three are needed before you scale sideways.

Weighing up who should supply this platform?

  • Rented services, script vendors, custom agencies and Omnistu, side by side, with questions to put to each and what our delivery days cover, on the Provider page.

Ready to run a broadcasting platform you own?

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Bigo Live , ChillChat , or any other live streaming or social audio service.

White label live streaming app describes a category of product, not any one company. Brand names appear elsewhere on this site only to describe the kind of platform being built and the terms buyers search for.

Discuss this scope by message

Tell us your market and audience, and we will respond with a practical read on scope.

team@omnistu.com