---
title: White Label Live Streaming App Features
description: "White label live streaming app features by role: fifteen room formats, a four-currency gift wallet, agencies, families, battles and a full operator panel."
url: https://miracuves.com/white-label-live-streaming-app/features
date_modified: 2026-10-20
author: miracuves
language: en_US
---

White Label Live Streaming App · Features
          
# White Label Live Streaming App Features: Rooms to Payouts

          
A video window and a gift button are the easy part of a broadcasting product. The weight sits underneath: a wallet that keeps what viewers bought apart from what hosts earned, a revenue split written into every gift, talent agencies that bring the hosts in, and moderation that holds up when a live room goes wrong. This is the platform underneath the live streaming clones, laid out by the person who touches each part.

          [Request a Live Demo →](https://miracuves.com/schedule-consultation/)[See Pricing](/white-label-live-streaming-app/development-cost/)
          
            **15** room formats
            **4** currencies, one ledger
            **6 days** to deploy
          
        
        
          Split writtenInside the gift
          
            Follow One Gift Through the Wallet
            
              01Coins leave the viewer's balance
              02Platform keeps its cut, 30% by default
              03Agency takes its cut, 10% by default
              04Diamonds credited to the host
              05Battle scores and rankings move
              06Family and agency points grow
            
          
        
      
    
  

  
    
      
        74Database Models on PostgreSQL 16
        200+Documented API Routes
        15Room Types in the Core Package
        6Battle Formats
      
    
  

  
    
      
        Roles Defined
        
## 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.

      
      
        
          01
          
### Viewers

          
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.

        
        
          02
          
### Broadcasters

          
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.

        
        
          03
          
### Agencies

          
Gets created and approved, invites hosts with a code, works with six member roles, signs hosts on commission or salary, moves talent between agencies, sets sub-agency rates and sees earnings host by host. Supply in this category arrives through recruiters, so the agency tools ship in the core product instead of waiting on a later release.

        
        
          04
          
### Family Groups

          
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.

        
        
          05
          
### Moderators

          
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.

        
        
          06
          
### Operators

          
Works across fifteen admin routes: host applications, withdrawal approvals, room monitoring, report queues, the gift and game catalogs, 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.

    
  

  
    
      
        Compare
        
## Miracuves Versus Renting a Platform or Buying a Single-Payment Script

        
Three ways to get a broadcasting product, compared on the parts that decide whether hosts get paid correctly and stay.

      
      
        
| What decides it | Rented / hosted platform | One-time script | Miracuves platform |
| --- | --- | --- | --- |
| How you pay | Usually a recurring fee that keeps running for as long as you operate | One-time listings run from under $10 on code marketplaces to roughly $250 to $1,500 from script vendors | $4,299 one time, fixed |
| Source code | Typically stays with the provider | Differs by vendor; a few keep it out of all their listed tiers | The full monorepo, handed over |
| Mobile apps | Depends on the provider's plan | Cheaper tiers often ship web-view apps instead of native ones | An Expo build covering the core flows, finished to your scope |
| Room formats | Whatever the provider has built | Often a single video room | Fifteen, each with its own seat defaults |
| Wallet and split | Set by the provider's model | Often one coin balance and a fixed percentage | Four currencies, splits tunable by room type, gift category and region |
| Agency layer | Often absent or a paid tier | Often left unbuilt | Six roles, plus contracts, transfers and sub-agency rates |
| Moderation | Whatever the provider ships | Frequently a basic report button | An action log, with reports, strikes, appeals and shadow bans |
| If you stop paying | The service and your host relationships may go with it | You keep what you bought, hosting aside | You keep everything, with hosting as the running cost |

      
      
The rented and script columns describe patterns we see across the market, not any one vendor, so check each seller against your own list. What sets our column apart is not price alone. It is that the economy, the agency layer and the source arrive together.

    
  

  
    
      
        End-to-End Journey
        
## 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.

      
      
        01
### 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.

        02
### 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.

        03
### 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.

        04
### 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.

        05
### 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.

        06
### 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.

        07
### The operator sees the whole loop

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

      
    
  

  
    
      
        Deliberate
        
## The Reason Every Module Ships in the Base Build

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

      
      
        
| Module | The reason it ships |
| --- | --- |
| Fifteen room formats | One format limits you to one audience. Voice rooms, karaoke and dating rooms draw people a solo video feed does not reach. |
| Four separate currencies | A single balance cannot say what was bought versus what was earned versus what may leave. Keeping them apart is what makes payouts explainable. |
| Split applied per gift | Hosts trust a platform that shows their share the moment a gift lands. Reconciling in bulk later invites disputes nobody can settle cleanly. |
| Agency contracts and roles | Recruiters place hosts where a share and a contract exist. Without them, the volume goes to whoever offers both. |
| Six battle formats | Competition turns watching into spending, and the family and agency formats extend that from single hosts to whole groups. |
| Family treasury and contribution | Gifts fund the business, while families give a viewer a specific community to come back to. |
| Strikes and shadow bans | A visible ban invites workarounds. A graded response, with appeals, lets moderators act in proportion. |
| Moderation action log | Live content disappears once a room closes, so each decision has to stay reviewable after the evidence is gone. |
| Withdrawal approval | Cash that leaves with no human decision in the path is how payout fraud becomes hard to reverse. |

      
      
Forty-five game types are modeled, seven of them built into the web app, beside daily check-in streaks, a lucky wheel, missions and timed platform events.

    
  

  
    
      
        Stack
        
## The Technology Underneath the Features

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

      
      
        **Backend**NestJS 10 on Node 20 in TypeScript, split into seventeen modules with forty-five services and more than two hundred documented endpoints, fronted by guards, interceptors and a global validation pipe, all inside a Turborepo monorepo.
        **Table design**PostgreSQL 16 behind a Prisma schema of 1,839 lines: seventy-four models and twenty-nine enums for rooms, gifts, agencies, families, moderation and the wallet, with JSONB and full-text search and seed data for gifts, games and demo accounts.
        **Web application**Next.js 14 with the App Router, forty-four routes and fifty components on React 18, Tailwind and Zustand, covering discovery, live rooms, the wallet, both feeds and the thirteen policy pages.
        **Pricing console**A second Next.js 14 application with fifteen routes for hosts, withdrawals, rooms, reports, catalogs, agencies, audit and revenue settings. Operator tooling is an application of its own and not a tab in the viewer app.
        **Media**Agora carries audio and video on your own account. The backend only issues publisher and subscriber tokens, so streams never pass through your servers.
        **Mobile**An Expo SDK 50 build for the core viewer and host journeys. The documentation calls it a stub instead of a peer of the web app, and we say the same here, then finish it to your scope during delivery.
      
      
        
### The wallet is where the years go

        
A streaming front end takes weeks to assemble. The slow work is beneath it: four currencies answering four different questions, a three-way split executed inside each gift, agency contracts with transfers and sub-agency rates, and a payout path that waits for an operator. Seventy-four models over 1,839 schema lines is simply what modeling all of that properly looks like, as opposed to squeezing it into one counter.

        
          **74**Database models
          **200+**API endpoints
          **4**Currencies, kept apart
          **$4,299**One-time, fixed
        
      
      
Everything is mainstream and easy to hire for, with ordinary PostgreSQL beneath it. A technical buyer running diligence can read all of it.

    
  

  
    
      
        Frank Readiness Audit
        
## Items Left Out of the Base Package

        
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 monitoring yet.** 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.

        
**Ten security fixes.** Demo credentials, the global guard, role alignment, admin cookies, secret rotation, HTTPS, upload limits and password hashing are listed as immediate work.

        
**No erasure or retention tooling,** and the mobile app is a stub, not a match for the web client. GDPR erasure, retention and consent are not built.

        
**Your accounts, not ours.** Agora, Stripe, Twilio, Firebase Cloud Messaging, SMTP and MinIO all need credentials you hold. No streams, gifts, music or effects come with the platform.

        
**Moderation and licensing are your job.** You are responsible for reviewing live rooms, confirming each host's age and identity, and complying with virtual currency and creator payout regulations in every market you enter.

      
      
It is a longer list than most sellers publish. Each item is scoped and quoted before work begins, so you can price it into the plan up front.

    
  

  
    
      
        
          Provider
          
### Weighing up who should supply this platform?

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

        
        [See the comparison →](/white-label-live-streaming-app/provider/)
      
    
  

  
    
      
        FAQ
        
## Feature Answers

      
      
        
          
            Why keep four currencies apart?
            Each one answers its own question. Coins are what a viewer bought, diamonds are what a host received, beans are what can be withdrawn and points drive family and agency rankings. Merge them and you can no longer tell a host's earnings from their spending, which is the figure any payout dispute hinges on.
          
          
            Can the revenue split be changed?
            Yes. The defaults are 30 percent platform, 10 percent agency and 60 percent host, and you can vary them by room type, gift category and region. They are applied as the gift is processed, so a host sees their share at once and there is no cycle-end reconciliation to argue over.
          
          
            Do agencies really need their own tools?
            In this category, yes. Recruiters bring hosts in bulk and move them between platforms, and they choose platforms that offer a contract structure and a configurable share. Agency creation and approval, invitation by code, six roles, commission or salary contracts, host transfers and sub-agency rates all ship in the base build.
          
        
        
          
            Is the mobile app ready to publish?
            Not as delivered. The Expo SDK 50 build handles the core viewer and host journeys and is graded a stub in the documentation. Lifting it to match the 44-route web client is the addition buyers ask for most, and we scope and quote it separately. If phones are your main surface, plan for it before purchase.
          
          
            Which outside accounts do I have to open?
            Agora for media, Stripe for coin purchases, Twilio for one-time passcodes, Firebase Cloud Messaging for push, an SMTP host for email and MinIO or another S3-compatible store for uploads. All of them run on credentials you own, and we connect them during setup.
          
          
            What is missing before a public launch?
            No test files exist, migrations are not in place, observability is absent, the multi-instance Redis adapter is not installed and the ten hardening items are open. Each is scoped and quoted before work starts. As a single instance the platform carries a launch audience, and the growth path is written down.
          
        
      
    
  

  
    
    
      
        
## Watch one gift split three ways

Ask for a demo and we will send a gift, trace the platform share, the agency share and the diamonds reaching the host, then run a battle scored on gift value.

        [See Pricing](/white-label-live-streaming-app/development-cost/)[Full Overview](/white-label-live-streaming-app/)
      
    
  

  
    
      
        Explore
        
## Explore the White Label Live Streaming App

      
      
        [Overview](/white-label-live-streaming-app/)
        [Features](/white-label-live-streaming-app/features/)
        [Development Cost](/white-label-live-streaming-app/development-cost/)
        [Provider](/white-label-live-streaming-app/provider/)
        [Business Model](/white-label-live-streaming-app/business-model/)
      
    
  

  
    
    
      
        
## Ready to run a broadcasting platform you own?

        
Go live in six working days with fifteen room formats, the four-currency wallet, agencies and families and the operator panel, your splits set with you and the whole monorepo on infrastructure you control.

        [Talk to Us →](https://miracuves.com/schedule-consultation/)
      
      
        
          **Created by the Miracuves Product Team**·
          Reviewed against the build·
          Revised **September 29, 2026**
        
        
          Miracuves.com · White Label Live Streaming App
          Features, stack and the pre-launch list were checked against the hub page on 2026-09-29
        
      
    
  

				
				
				
		
				
				
					

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

        
          
            Topic overview
            
“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.

          
          
            Authors
            
The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from any third-party live streaming website or application.

          
          
            Licensing and moderation fall to you
            
No streams, gifts, music or effects are supplied with the platform. Moderating live rooms, verifying the age and identity of hosts, and meeting the rules that apply to virtual currency and creator payouts in each market you operate in are your responsibility. All third-party names and marks are the property of their respective owners.

          
        
        [Read our full Legal Notice & Disclaimer →](/disclaimer/)
