White Label Live Streaming App - Rooms, Gifting, Agencies & Creator Payouts
A feature-complete live-streaming platform covering the whole entertainment loop: fifteen room formats from solo video to voice rooms and PK arenas, a four-currency coin economy with configurable revenue splits, talent agencies and families, short videos and a square feed, and a moderation stack with reports, strikes and appeals.
Three surfaces from one monorepo. Viewers and hosts use a 44-route web app, operators run a 15-section admin panel, and an Expo mobile app covers the core flows, all against a NestJS backend of 200 endpoints over 74 database models.
Go Live in 6 Days with Agency-NativeGift-EconomyLow-LatencyRoom-FlexibleWhite-LabelDocker-Deployed
⚡ Platform at a Glance
Fifteen Room Formats
Solo video, solo audio, voice rooms with seats, multi-guest, co-host, panel, party, karaoke, gaming, talent, talk show, dating, private, subscriber-only and scheduled events. Most clones ship one.
Agencies Are the Growth Engine
Talent agencies recruit hosts, set contracts, track earnings and take a configurable share. In this category the agency layer is what brings supply, and it is native rather than bolted on.
Four-Currency Economy
Coins bought with money, diamonds earned from gifts, beans that convert to cash, and points that drive family and agency ranking. Each is modelled separately so operators can tune one without breaking another.
Six PK Formats, Six Formats
One-versus-one, team, room, family, agency and tournament, scored on gift value with live scoring, winner determination and revenge battles.
Families and Community
Leaders, co-leaders and elders, join policies, contribution tracking, a treasury and family-versus-family battles. This is the retention layer under the gifting layer.
Honest About Readiness
The documentation grades this build itself and names a pre-production list. Testing, observability, migrations and several security items are open work, stated on this page rather than discovered later.
🚀 Ready to launch your own live streaming platform?
Live in Action
Live Demo - Viewer, Host, Operator Console & Android Build
Rather than take our word for it, open the platform yourself. Every role has a working login and nothing needs installing. Join a room, send a gift, watch the coin balance move, then find that same activity waiting in the operator console.
VIEWER EXPERIENCE
Viewer Experience & Wallet
What the audience sees. Rooms discovered by type, country and language, live chat, gifting, short video, the square feed, follows, and a wallet holding all four currencies.
-
Open the web app in your browser
-
Login with the demo credentials below
-
Explore: Discover, Rooms, Gifts, Wallet
-
Try: user1@mxbligo.live | password123
HOST EXPERIENCE
Going Live, Seats, PK And Earnings
What the creator sees. Go live in any of fifteen formats, run seats and co-hosts, start PK battles, watch diamonds accumulate, then follow the conversion all the way to a withdrawal request.
-
Open the web app in your browser
-
Login with the demo credentials below
-
Explore: Go Live, Seats, Six PK Formats, Earnings
-
Try: host1@mxbligo.live | password123
OPERATOR CONSOLE
Moderation, Payouts And Settings
Governance across fifteen operator routes: host applications, withdrawal approval, room monitoring, report resolution, both catalogues, agency approval and the audit trail.
-
Open the admin panel in your browser
-
Login with the demo credentials below
-
Explore: Hosts, Withdrawals, Reports, Settings
-
Try: admin@mxbligo.live | password123
ANDROID APP
Branded Android Build
A branded Android build of the Expo SDK 50 application. It covers the core viewer and host journeys, carries Firebase push and the same Agora media layer, and talks to exactly the same API and socket layer as the web client. The documentation grades it a stub rather than a peer of the forty-four-route web app, and we finish it to your scope during delivery.
-
Download the app to your Android device
-
Login with the viewer credentials below
-
Explore: Discover, Rooms, Gifts, Wallet
-
Try: user1@mxbligo.live | password123
Watch It Work
Platform Walkthrough: Go Live, Gifting, PK & Payouts
A walkthrough of the platform as an operator sees it, rather than a feature reel. It opens on a host going live, choosing a room format and generating the Agora publisher token, so the path from a click to a broadcast is visible rather than asserted. A viewer joins, buys coins, and sends a gift, and the same transaction is followed through the split: the platform share, the agency share and the diamonds landing on the host. A PK battle runs between two hosts with live scoring on gift value. The host then converts diamonds to beans and raises a withdrawal request, which is picked up in the operator console alongside the host application queue, the report queue and the settings that control the split itself. If a specific flow matters more than the tour, ask and we will open it live with data in it.
Every Screen Mapped
Platform Flows - Viewer, Host, Agency & Operator Screens
The interface across the surfaces that matter: room discovery by type, country and language, the live room with seats and chat and the gift drawer, the go-live flow with room format selection, PK battle screens with live scoring, the wallet with coins and diamonds and beans, short videos and the square feed, the agency and family dashboards, and the operator console with its host application, withdrawal, report and audit queues.
Follow a viewer from discovery through a first gift, a host from application and approval to going live and requesting a payout, an agency manager from inviting a host to tracking earnings, and an operator from a filed report to a resolved appeal. Web carries the full experience and the Expo mobile app covers the core viewer and host flows. Want a guided walkthrough of a specific flow? Book a call and we will open the surface you care about with live data in it.
Straight Answers
Deployment References - What the Platform Actually Does
There is no live-streaming deployment in the Miracuves portfolio yet, so rather than dress this platform in borrowed proof, the statements below are properties of the build, each demonstrable in the live demo above.
Illustrative Scenario
Modelled Reference - Live Streaming and Gifting Deployment
An illustrative configuration showing how this platform would be set up for a live entertainment operator. It describes no client engagement, and every figure is a property of the software rather than a result any customer has reported.
Emerging Market
Live Streaming and Gifting Platform
How this platform is configured for an operator whose revenue depends on hosts staying, where talent agencies recruit the hosts and a coin economy carries the monetization.
- Hosts leaving because earnings are opaque and payouts are slow
- Agencies managing talent on spreadsheets because the platform gives them no surface
- A gift economy that cannot be reconciled once volume arrives
- Fifteen room formats so hosts pick the one that suits their content
- An agency and family layer that makes recruitment the platform growth engine
- A four-currency economy with configurable revenue splits and withdrawals
- Agora low-latency audio and video across web and mobile
- Coins, diamonds, beans and points with a 30/10/60 default split
- PK battles in six formats including family and agency
- Short videos, a square feed, and 45 modelled game types
- Moderation with reports, strikes, appeals and an audit trail
This is a modelled reference deployment, not a client engagement. Every capability listed above ships in the base build and is demonstrable in the live demo. The figures are properties of the platform, not results reported by a customer.
The Basics
What Is a White Label Live Streaming App?
It is a finished social broadcasting product you put your own name on. Hosts go live with audio or video, viewers watch and send virtual gifts, talent agencies recruit and manage those hosts, and a coin economy converts attention into money. What it takes off your hands are the genuinely hard parts of this category: keeping media low-latency at volume, running a gift ledger that reconciles, and giving professional recruiters an agency layer worth working inside.
More Than A Video Player
The value is in the gift ledger, the agency contracts and the moderation queue. An SDK hands you a video feed and leaves the entire economy beneath it as your problem to solve.
Owned, Not Rented
The monorepo, the Prisma schema and the Compose stack all transfer to you. No per-seat charge, no waiting on a vendor roadmap, and ordinary PostgreSQL underneath it all.
A Production Candidate, Graded Openly
The build grades itself in the open: nine out of ten on feature completeness, one out of ten on testing. No test suite, no migrations, no observability layer yet. Closing that is scoped pre-launch work, quoted rather than assumed.
Built for Web, Mobile & Admin
What a Live Streaming Script Has to Solve
Nobody struggles with the video player. What is hard is a revenue split configurable by room type and by region, an agency structure carrying contracts and host transfers, and moderation strong enough to survive live user-generated content. Those are precisely the parts already built.
-
Fifteen room formats with seat management
-
Four-currency economy with configurable splits
-
Agencies, families and PK battles
-
Short videos, square feed and 45 game types
-
Moderation with strikes, appeals and audit logs
Shipped: seventy-four Prisma models over 1,839 schema lines, more than two hundred endpoints across seventeen NestJS modules, forty-four web routes, fifteen operator routes, an Expo mobile build and a seven-service Compose deployment.
Everything Included
Platform Features - Rooms, Gifting, Agencies, Games & Moderation
Everything listed here exists in the running demo and can be shown to you on request. Where something depends on a provider account, a deployment choice, or hardening work before it is safe in production, that is written against the item rather than glossed over.
Fifteen Room Formats
Fifteen formats ship pre-configured: solo video, solo audio, voice room, multi-guest, co-host, panel, party, karaoke, gaming, talent, talk show, dating, private, subscriber-only and events, each carrying its own seat defaults.
- Email and phone registration with OTP verification
- JWT auth with refresh token rotation and bcrypt
- Guest onboarding for browsing without an account
- Device binding for push and session tracking
Seats You Can Control
Occupants can be requested, approved, locked or removed, and their microphone and camera toggled. That is what makes a six-seat audio room something you can actually run rather than a static grid.
- Fifteen room formats with per-type seat defaults
- Seat request, approval, lock and kick
- Mic and camera control for seat occupants
- Private rooms, age restriction and language tags
Media On Your Own Agora
Low-latency audio and video on your own Agora account, with publisher and subscriber tokens issued server-side, working across both the web and mobile clients.
- Agora low-latency audio and video
- Server-issued publisher and subscriber tokens
- Room chat over Socket.IO with rate limits
- One-to-one audio and video calls with call history
One Transactional Gift Ledger
Eight gift categories write into a single transactional record that debits the sender coins, credits the recipient diamonds and updates the room total together, or not at all.
- Coins, diamonds, beans and points
- Recharge packages with bonus coins
- Eight gift categories including combo and luxury
- Configurable split across platform, agency and host
Splits You Set
Ships at 30 percent platform, 10 percent agency and 60 percent host, and can be varied by room type, by gift category and by region.
- PK battles in six formats with live scoring
- Winner determination and revenge battles
- Leaderboards by gift value
- Family and agency battle aggregation
Diamonds to Beans to Cash
Gifts land as diamonds, diamonds convert to beans, beans leave as currency less a five percent fee, and every withdrawal waits on operator approval.
- Agency creation, approval and host invitations
- Six agency member roles with contracts
- Host transfers and sub-agency rates
- Agency earnings tracking
The Agency Layer
Agencies are created and approved, invite hosts by code, carry six member roles, sign contracts on commission or salary, move hosts between them and set sub-agency rates.
- Family creation with three join policies
- Leader, co-leader, elder and member roles
- Contribution tracking and family treasury
- Family ranking and leaderboards
The Family Layer
A leader runs one family, picks between three join policies, assigns four member roles, tracks contribution, holds a treasury and takes the group into family-versus-family battles.
- Short video upload up to 200MB
- Captions, hashtags and music metadata
- Discover and following feeds with trending
- Square feed with text, image, video and polls
Six PK Formats
Six battle formats run one-versus-one, team, room, family, agency and tournament, scored live on the gift value each side attracts.
- Forty-five game types modelled
- Seven games built into the web app
- Daily check-in with streak rewards
- Lucky wheel, missions and platform events
Short Video And Square Feed
Clips up to 200MB carry captions and hashtags into discover and following feeds, alongside a square feed that takes text, image, video and poll posts.
- Reports across seven content types
- Strikes, violation types and appeals
- Ban, mute and shadow ban records
- Blocked keywords and moderation action log
Games And Retention Loops
Forty-five game types are modelled and seven are built into the web client, sitting beside daily check-in streaks, a lucky wheel, missions and timed events.
- Follow, block and mutual followers
- Profile visitors and top fans by gift value
- Search by username and hashtag
- Nearby rooms by distance
Moderation And Trust
Seven content types can be reported, producing strikes, violation records and appeals, with bans, mutes, shadow bans, a keyword blocklist and a complete moderation log behind them.
- Six notification categories with quiet hours
- Support tickets with attachments and SLA
- Thirteen legal and policy pages
- Fifteen-route operator admin panel
Note for buyers: The platform ships complete as software. Agora, Stripe, Twilio, Firebase Cloud Messaging, SMTP and MinIO all require your own accounts and credentials. The documentation is also candid that there is no test suite, no Prisma migrations, no structured logging or APM, no GDPR erasure or retention, and that the Socket.IO Redis adapter needed for multi-instance deployment is not installed. Those are named pre-launch work, not surprises.
How Operators Earn
Revenue Models - Gifts, Subscriptions, Agencies & Games
A live-streaming platform earns from several places at once, and this platform models each separately so an operator can tune one lever without disturbing the others.
Coin Sales
Viewers buy coins through Stripe on your own merchant account. This is the top of the revenue funnel and the point at which real money enters the economy.
Gift Commission
The platform keeps a configurable share of every gift, 30 percent by default, applied at transaction time rather than reconciled afterwards.
Agency Share
Agencies take a configurable cut, 10 percent by default, which is what makes professional recruiters willing to bring hosts onto your platform at all.
Withdrawal Fees
Bean-to-cash withdrawals carry a 5 percent fee, so the cash-out path itself contributes rather than costing the platform.
VIP Subscriptions
Free, Bronze, Silver, Gold and Diamond tiers with badges and benefits, giving predictable recurring revenue beside the transactional gift income.
Game Participation
Forty-five modelled game types with coin wagering, turning the time between streams into another reason coins get spent.
The one that moves the numbers most is gifting. Everything else in the product exists to increase how often a viewer feels like sending one.
Run It Without a Dev Team
Admin Panel - Hosts, Withdrawals, Moderation & Settings
Fifteen routes put users, hosts, money, content and policy behind a single operator surface. It is the part of a broadcasting build most teams postpone and then never come back to.
Admin Panel Sections
Dashboard
Revenue charts, user growth, a breakdown by room type and the top gifts across eight KPI cards. This is the screen an operator opens first each morning.
Users And Roles
Search the user base, ban and unban, verify accounts and assign roles, with every one of those actions written to the audit log.
Host Approvals
The queue standing between an ordinary account and the right to broadcast, carrying legal name, identity document, biography and specialities for review.
Withdrawals
Every bean-to-cash request lands here for an operator to approve or refuse. This is the control that keeps payout fraud off the platform.
Room Monitoring
Observe rooms while they run, close the ones breaking policy, and promote the ones worth surfacing in discovery.
The Report Queue
One queue resolves or dismisses reports raised against users, rooms, streams, messages, videos, posts and comments.
Gift Catalogue
Gift items are created and retired across eight categories, with price and animation type deciding what a viewer can actually send.
Game Catalogue
Complete CRUD across all forty-five modelled game types, which puts the game mix under operator control rather than ours.
Agencies
Agencies are approved and suspended here, the gate deciding who may recruit hosts and draw a share of their earnings.
- Eight KPI cards and revenue charting
- Ban, unban, verify and role assignment
- An approval queue for host applications
- Approve or refuse each withdrawal
Settings And Audit
Share percentages, withdrawal ceilings, streaming limits and feature toggles, sitting beside a paginated trail of operator actions.
- Watch rooms, force-close them, feature them
- Resolve reports and moderate short video
- Manage both the gift and game catalogues
- Agency approval, audit trail, revenue settings
Before you go live: JavaScript can currently read the admin token, the demo accounts on this instance use passwords anyone can see, and role names in the code have drifted from the database enum. All three appear in the documentation and all three are closed during deployment. Tell us your security requirements and we will scope whatever else you need.
Transparent Pricing
How Much Does a White Label Live Streaming App Cost in 2026?
Building a live-streaming and gifting platform with Miracuves typically starts from around $3,399 for a launch-ready white-label white label live streaming platform and increases based on the pre-launch hardening scope, media and payment integrations, mobile depth and infrastructure complexity.
Not sure which option
is right for you?
Talk to us - we'll understand your goals, timeline, and budget, and point you to exactly what you need. No upselling, just honest advice.
The Full Package
What's Included - Full Source Code, Apps & Deployment
What transfers is a complete, deployable platform: application source, the schema underneath it, and the documentation any technical buyer will ask to see. Ownership is outright. No runtime licence, no per-seat charge, and no dependency on what we decide to build next.
Backend
NestJS 10 on Node 20: seventeen modules, forty-five services and more than two hundred endpoints, with guards, interceptors and a global validation pipe in front of them.
- npm workspaces inside a Turborepo monorepo
- Seventeen NestJS 10 backend modules
- Two hundred-plus documented endpoints
- Free to modify, extend and redeploy
The Data Model
PostgreSQL 16 behind 1,839 lines of Prisma schema: seventy-four models and twenty-nine enums spanning rooms, gifts, agencies, families, moderation and the wallet.
- Seventy-four models over 1,839 schema lines
- Twenty-nine enums for every lifecycle state
- JSONB and full-text search on PostgreSQL 16
- Seeded gifts, games and demo accounts
The Web Client
Forty-four routes and fifty components on the Next.js 14 App Router, covering discovery, live rooms, the wallet, both feeds and thirteen policy pages.
- Forty-four routes on Next.js 14
- React 18 paired with Tailwind and Zustand
- Discovery, live rooms, wallet and feeds
- Thirteen legal and policy pages
Admin Panel
A second Next.js 14 application across fifteen routes, handling hosts, withdrawals, rooms, reports, catalogues, agencies, audit and settings.
- Fifteen operator routes on Next.js 14
- Applications, withdrawals and moderation queues
- Catalogue management for gifts and games
- Revenue settings and the audit log
The Mobile Build
Expo SDK 50 covering the core viewer and host journeys. The documentation calls it a stub, and we build it out to your scope rather than pretending it is at parity.
- Mobile built on Expo SDK 50
- Covers the core viewer and host journeys
- Documented as a stub, not as parity
- Finished to your scope during delivery
The Real-Time Layer
Agora RTC carrying media on your own account, Socket.IO carrying chat and presence, and Redis 7 sitting behind both for cache and rate limiting.
- Agora RTC wired into web and mobile
- Socket.IO rooms and presence
- Cache, presence and rate limits on Redis 7
- S3-compatible storage through MinIO
The Deployment Stack
Seven services in one Compose stack, Nginx in front, PostgreSQL, Redis and MinIO behind it, with a GitHub Actions pipeline and a runbook alongside.
- A Compose stack of seven services
- Reverse proxy configuration for Nginx
- Continuous integration via GitHub Actions
- Runbook for deployment and operations
The Documentation Set
Ten documents spanning architecture, schema, API, web, admin, integrations, security, deployment and the testing roadmap.
- Ten technical documents
- Entity diagram, schema and API reference
- Assessment of security and compliance
- Pre-production checklist and testing roadmap
Want to see it running first? Use any of the three role logins above, or book a walkthrough and we will show you a host going live, a gift splitting across platform and agency, and a withdrawal landing in the operator queue, run against your own commercial model.
Know Your Buyer
Who Is This White Label Live Streaming Platform Built For?
It fits operators moving into live entertainment in markets where gifting, talent agencies and social gaming are what actually carry monetisation.
Live Streaming Startups
Talent Agency Networks
Regional Entertainment Operators
Creator Platform Builders
Voice and Audio Social Apps
Systems Integrators
If your business depends on recruiting hosts and keeping them, and on an economy that pays them accurately enough that they stay, an owned platform becomes a long-term asset rather than a channel you rent from somebody else.
Where It Fits
Use Cases - Live, Voice, Agency & Regional
Which room formats lead determines what kind of operator this becomes. A video-first product leans on solo and multi-guest rooms; a voice social app on seats and karaoke; an agency network on contracts and earnings. Every one of those is configuration, not a fork you then maintain.
Video-First Live Streaming
A video-led platform where hosts broadcast alone or with guests, viewers send gifts, and PK battles create the competitive spikes that make gifting worth doing at all.
Voice Rooms & Audio Social
An audio-led social product built on seat-based rooms, karaoke and talk shows, where the formats and seat management carry the whole experience without video anywhere.
Agency-Led Talent Networks
A network led by agencies, where talent managers recruit, contract and take their share, and the agency dashboard with its host transfer flows is the product itself.
Social Gaming Platforms
A social gaming product where forty-five modelled game types and the lucky wheel sit alongside live rooms, converting idle time into coin spend.
Regional Market Expansion
A regional expansion using country, language and region targeting across discovery, with revenue splits configured separately per region.
Systems Integrator Delivery
An integrator delivery, extending a documented NestJS backend of more than two hundred endpoints instead of opening an empty repository.
One platform, many configurations. Every scenario above runs on one schema and the same three surfaces. What varies is which formats you switch on, the split percentages, the gift catalogue and the game mix. None of it requires a separate branch to maintain.
Market Timing
Why Launch a Live Streaming Platform in 2026?
Gifting rather than advertising pays for live entertainment, so income arrives immediately instead of waiting on scale. The operators pulling ahead are the ones whose hosts stay put, and hosts stay where agency support is genuine and payouts land accurately.
Supply Is The Real Constraint
Audiences follow hosts, and whether hosts arrive and remain comes down to how clearly they can see their earnings and how well their agency is supported. That makes the host experience your growth engine, not the marketing budget.
Gifting Pays Immediately
Where ad-funded video waits for an audience, a gift economy earns on the very first broadcast. That single difference reshapes how the business needs funding.
Agencies Deliver Supply In Bulk
One agency can deliver dozens of hosts at once. Without a native layer carrying contracts and earnings, professional recruiters have no reason to pick you over anyone else.
Seat Logic Is Deceptively Hard
Requesting, approving, locking and removing occupants, with microphone and camera control, across fifteen formats, is exactly the engineering most streaming templates leave out.
Moderation Cannot Wait
Live user-generated content needs reporting, strikes, appeals, bans and keyword blocking from launch day, not retrofitted after the first incident.
Buy Versus Build Is Settled
Building the equivalent yourself spans media, economy, agencies, games and moderation across several years. A white-label deployment is running on your own server inside six days.
Platform by the Numbers
It is this layer that eats the years. Fifteen room formats with working seat logic, a four-currency ledger, agency contracts with transfers, PK scoring and moderation built for live user content are each unglamorous, non-negotiable and slow to get right.
Under the Hood
Tech Stack - NestJS, Next.js, Agora & PostgreSQL
Three things decide whether a broadcasting platform holds up: media that stays low-latency, a socket layer that survives thousands of simultaneous viewers, and a gift ledger an auditor can actually follow. This is what sits behind each of them.
Backend
NestJS 10 · Node 20 · TypeScript 5
- Dependency injection across seventeen modules
- A global validation pipe, guards and interceptors
- Swagger generated over 200-plus endpoints
- Passport and JWT, refresh tokens rotated
Data Layer
PostgreSQL 16 · Prisma 5 · 74 Models
- Twenty-nine enums over 1,839 schema lines
- Full-text search and JSONB both available
- Every gift wrapped in a database transaction
- Applied via db push; migrations remain pre-launch work
Web & Admin
Next.js 14 · React 18 · Tailwind
- App Router emitting standalone Docker output
- Forty-four public routes, fifteen operator routes
- State handled by Zustand, little ceremony
- Thirteen legal and policy pages ready
Real-Time Media
Agora RTC · Socket.IO 4 · Redis 7
- Audio and video carried by Agora
- Publisher and subscriber tokens issued server-side
- Chat, gifts and presence over Socket.IO rooms
- Redis holding cache, presence and rate limits
Payments & Messaging
Stripe · Twilio · FCM · SMTP
- Coin recharge and subscriptions through Stripe
- One-time passcodes over Twilio SMS
- Push delivered by Firebase Cloud Messaging
- Nodemailer sending via your own SMTP
Deployment
Docker Compose · Nginx · MinIO
- One seven-service stack, local and production
- Rate limiting at the Nginx reverse proxy
- Object storage on S3-compatible MinIO
- Builds driven by GitHub Actions
Note for Tech Buyers: every third-party provider runs on an account you own, Agora, Stripe, Twilio, Firebase Cloud Messaging, SMTP and MinIO or any S3 equivalent among them. The documentation does not hide what is unfinished and neither will we: there is no test suite whatsoever, the schema is applied through prisma db push instead of migrations, nothing provides structured logging, APM, metrics or alerting, GDPR erasure and retention are unimplemented, and the Socket.IO Redis adapter required to run more than one backend instance is absent. Mobile is graded a stub rather than a peer of web. Everything above is mainstream and straightforward to hire for, with no proprietary framework anywhere and a schema that ports to any PostgreSQL instance.
End to End
How the Platform Works - Register, Go Live, Gift, Split & Withdraw
A live-streaming platform looks like a video grid from the outside and runs on a tightly sequenced identity, media, ledger and payout pipeline underneath. Here is the path from a signup to a host withdrawal.
Platform Journey - From Signup to Settled Payout
Registration & Onboarding
Registration accepts email or phone with a one-time passcode, and guests can browse before committing to an account at all.
- Email or phone registration with OTP
- Guest onboarding with limited features
- Device binding for push and security
- Profile with username, avatar and birthday
Host Application & Approval
Nobody broadcasts before an operator approves them. The application carries identity and specialty detail for review.
- Application with real name, ID and bio
- Operator review queue in the admin panel
- Approval notification to the applicant
- Agency invitation by host code where relevant
Going Live
The host picks one of fifteen room formats, and the backend creates the room, the participant and seat records, and the Agora publisher token.
- Room format selected from fifteen options
- Room, participant and seat zero created
- Agora publisher token generated
- Room added to the active set for discovery
Discovery & Interaction
Viewers find rooms by type, country and language, join over Socket.IO, and interact through chat and seat requests.
- Discovery by room type, country and language
- Socket.IO join with presence in Redis
- Room chat with rate limiting
- Seat request, approval and mic control
Gifting & Revenue Split
A gift is a financial event, not an animation. Cost, split and balances all move inside one database transaction.
- Sender coins decremented by quantity times price
- Split applied across platform, agency and host
- Receiver diamonds incremented and totals updated
- Gift event broadcast to the room in real time
Conversion & Withdrawal
The commercial tail runs after the stream: diamonds become beans, beans become a withdrawal request, and an operator approves it.
- Diamonds converted to beans at the configured rate
- Withdrawal request raised by the host
- Operator review in the admin withdrawal queue
- Five percent fee applied on payout
Visual Flow Diagram
Register → Apply → Go Live → Gift → Split → Withdraw
How It's Built
Platform Architecture & Backend Flow
Monorepo, Four Apps
A Turborepo workspace holding the NestJS backend, the Next.js web app, the Next.js admin panel and the Expo mobile app, with shared config, types and utils packages.
Nginx In Front
A reverse proxy routing /api to the backend, /admin to the admin panel and everything else to web, handling rate limiting and SSL termination in one place.
Guarded Request Pipeline
Helmet, CORS, compression, a global validation pipe, a throttler guard and a JWT guard run before any controller sees a request.
Media Outside the App
Agora carries the audio and video, so the backend issues tokens rather than relaying streams, which is what keeps the server tier stateless and cheap.
Sockets for Everything Live
Socket.IO handles chat, gifts, seats and presence with Redis behind it, keeping the real-time surface separate from the REST API.
Gifts as Transactions
A gift decrements the sender, splits the value, credits the receiver and writes the record inside one Prisma transaction, so balances reconcile rather than drift.
Performance Targets
Built to Scale - Stateless Media, Indexed Reads & a Documented Path
Where the architecture can be ordinary it is, and where broadcasting forces a choice it specialises: video handed to Agora, a relational schema indexed around discovery, and sockets kept clear of the API. What has not been built yet is written down as a path rather than presented as finished.
Video Never Touches Your Servers
Agora carries every stream. Your backend issues a token and then leaves the path entirely, which is the single decision that keeps a broadcasting platform affordable to run.
What the media layer gives you:
- Server-issued publisher and subscriber tokens
- Low-latency delivery worldwide via Agora
- The backend holds no media state at all
- One token flow shared by web and mobile
The Busiest Read Path
Finding a room is what users do most, and that query filters on type, country and language before anything else is fetched.
That path rests on:
- A Redis set holding every active room
- Filters on type, country and language
- Per-room viewer counts kept current
- Distance calculation for nearby rooms
Where The Socket Layer Actually Stands
Chat, gifts, seat changes and presence all travel over Socket.IO, with Redis holding presence and the rate-limit counters.
True today, and not yet true:
- Rooms, authentication and auto-reconnect all work
- Presence and rate limiting sit in Redis
- Runs single-instance out of the box
- The multi-instance Redis adapter is not installed
The Path Is Named, Not Hidden
Documented opening targets are 100 concurrent rooms and 5,000 open sockets. The growth figures sit ten times above that.
Closing that gap takes:
- The Socket.IO Redis adapter installed
- PostgreSQL connection pooling
- A CDN ahead of media and static assets
- Clustering across Redis, PostgreSQL and MinIO
Media Lives Elsewhere
Because Agora carries the streams, your hosting bill tracks API calls rather than concurrent video minutes.
Presence Held In Redis
Redis holds active rooms, online presence and rate-limit counters, none of it in application memory.
Gifting Is Transactional
Gifting runs inside a transaction, so a failure cannot leave a sender debited and a host uncredited.
One Compose Definition
One seven-service Compose definition runs the same way on a laptop and in production.
The Ceiling Is Stated
The opening ceiling is stated at 100 rooms and 5,000 sockets, together with exactly what changes to pass it.
The Gap We Name
Going multi-instance requires the Socket.IO Redis adapter, which today is absent from the build. We would rather say so here.
Built for Customization & Long-Term Growth
No two markets want the same product. The stack stays deliberately mainstream so that changing it is ordinary engineering rather than archaeology.
A new capability is a Prisma model, a NestJS module and a route. A new provider is an environment variable. And every framework in that list, from NestJS and Next.js through to Prisma, PostgreSQL and Redis, is one you can hire for without difficulty.
Note for founders and operators: Better you read this now than meet it during a load test. As a single instance the build carries a launch audience comfortably. Going beyond that needs the Redis adapter, connection pooling and clustering, and we scope that work into deployment rather than assuming it away.
Built to Be Audited
Platform Security - Documented, Graded & Candidly Open
A dedicated assessment covers the security posture, and the notable thing about it is how openly it scores itself: 5 out of 10, with ten named items to finish before anything goes public. Handing you that list up front is more useful than letting you discover it later.
Credential and Secret Rotation
Authorization Hardening
Session and Token Safety
Payment Integrity
Data Protection
Operational Readiness
Authentication Is The Strong Point
Refresh-token rotation on JWT, bcrypt hashing and device binding. The assessment singles out authentication as the strongest area of the codebase.
Guards Run Before Controllers
Every request passes Helmet, CORS, a global validation pipe and a throttler before it reaches a controller, and protected routes carry their own JWT guard.
Staff Actions Are Logged
Two separate logs record what staff do, one for operator actions and one for moderation decisions, both queryable from the panel itself.
Seeded Logins Come Out First
Seeded admin, host and viewer logins ship with known passwords printed on the sign-in screens. Stripping them and rotating those accounts is the first job before launch.
Global Guard And Role Alignment
The JWT guard is applied per controller rather than globally, and a handful of role strings drift from the database enum. Both get corrected so any route added later is protected by default.
The Rest Of The List
Plaintext room passwords, an admin token JavaScript can read, unverified Stripe webhooks, absent migrations, absent tests, no observability layer and no GDPR erasure path.
What exists is genuine: refresh-token rotation on JWT, bcrypt hashing, device binding, Helmet headers, CORS, a global validation pipe, a throttler, per-controller JWT guards, a CSRF header check on mutating calls, and an audit log sitting behind operator actions. What is missing is equally genuine and set out below. We close those items as scoped hardening before you launch, rather than leaving them for you to find.
Go Further
Add-Ons - Hardening, Testing, Mobile & Scale
As delivered the platform is feature-complete and demonstrable. What follows is what operators most often add on top, either because a third-party account is involved or because the documentation flags it as outstanding before production.
Pre-Production Hardening
The ten immediate items named in the documentation: demo credentials, the global guard, RBAC alignment, admin cookies, secret rotation, HTTPS, upload limits and password hashing.
Test Suite
The build contains no test files whatsoever today. Unit, integration and end-to-end coverage is scoped work, and a testing roadmap already exists to follow.
Mobile Parity
The Expo build covers core viewer and host journeys and is graded a stub. Lifting it to parity with the forty-four-route web client is the single most requested addition.
Observability Stack
Nothing provides structured logging, APM, metrics or alerting today. Adding that layer is the difference between incident response and guesswork.
Prisma Migrations
Schema is applied through db push, which stops being safe the moment production data exists. Converting to a proper migration history is cheap, early work and it matters.
Multi-Instance Scale
Installing the Socket.IO Redis adapter, adding connection pooling and clustering is what carries the platform past one backend instance.
GDPR & Compliance
The policy pages exist; erasure, retention and consent mechanisms do not. For the EU and comparable jurisdictions this is required work.
CDN & Media Delivery
MinIO is self-hosted and S3-compatible. Once upload volume climbs, putting a CDN in front of short video and static assets is the next step.
Building in Creator Platforms? We Have the Whole Market Covered.
The white label live streaming platform is one platform in a complete creator suite. If your roadmap extends beyond live streaming and gifting, these connect naturally.
TikTok Clone
Short-form video platform with algorithmic discovery, creator monetization and a full moderation stack.
OnlyFans Clone
Creator subscription platform with paywalled content, tipping and direct fan messaging.
ChillChat Clone
Social feed platform with stories, reels, direct messaging and a discovery surface.
LoyalFans Clone
Text-first social network with real-time feeds, follows and conversation threading.
The Commercial Case
Marketability, Revenue Potential & Business Prospects
What makes this category unusual commercially is that income begins immediately. A gift is a purchase rather than an impression, which means a hundred active hosts are already generating transactions while an advertising-funded rival is still assembling inventory.
Six Revenue Levers
Six independent levers: coin sales, commission on gifts, the agency share, withdrawal fees, VIP subscriptions and game participation.
Earning From The First Stream
The first broadcast can earn. Nothing waits on the audience threshold that advertising economics demand.
The Agency Network Is The Moat
An agency network delivering hosts in volume is genuinely hard to copy, and it is payout accuracy that keeps those agencies from taking their talent elsewhere.
Optionality At Exit
You hold the monorepo and the schema on ordinary PostgreSQL. In diligence, seventy-four documented models read as an asset rather than a black box someone has to explain.
Most operators launch with a recruited set of hosts rather than open registration, because host quality is what makes the first viewers stay. Coin sales and gift commission are collectible from the first stream. Agencies usually form once there are enough hosts to make recruiting worthwhile, and subscriptions follow once there is a reason to want a badge. All of it is in the schema already, so switching each on is configuration rather than development. What is not optional is the pre-production hardening, and we scope that alongside the launch rather than after it.
Defensibility comes from supply and from the agency network, not from features. Hosts who have built a following, joined an agency and accumulated a payout history do not casually move, and the agencies that recruited them have their own reason to stay. The platform contribution is making onboarding fast enough to build that supply, the economy accurate enough to keep it, and the whole record yours rather than a third party who can change the revenue split on you.
Example Revenue Scenarios
The case for owning the stack is simple. In live entertainment the durable asset is the host relationship and the agency network, and both belong to whoever runs the infrastructure. That is precisely why renting someone else platform has a ceiling built into it.
Focused Launch
Active Hosts
Gifts carry the revenue while the agency layer is still forming.
A curated launch in which recruiting hosts and paying them correctly matter far more than raw scale, and the portal finally replaces the spreadsheet.
Growth Stage
Active Hosts
Agencies compound recruitment while subscriptions add a recurring line.
An operation at market scale where recruitment is delegated to agencies and the competitive spikes come from PK battles.
Regional Platform
Active Hosts
Per-region splits, game revenue and subscriptions all pull together.
A multi-market platform where regional revenue configuration and the game catalogue turn a single deployment into several national businesses.
Why Miracuves
Miracuves vs Other White Label Live Streaming Vendors
Several routes lead to a live streaming platform: off-the-shelf scripts, freelancers, agencies, or owning the infrastructure outright.
Why Founders Choose Miracuves
The Agency Layer Is Built In
Contracts, invitations, host transfers, sub-agency rates and earnings all modelled. Off-the-shelf scripts hand you rooms and leave professional recruitment entirely unbuilt.
Fifteen Room Formats
Solo, voice, multi-guest, karaoke, dating, subscriber-only and the rest, each arriving with its own seat defaults. Most templates ship a single video room and stop there.
An Economy, Not A Counter
Four currencies with splits configurable by room type, gift category and region, instead of one coin balance and a percentage frozen in the code.
You Own The Source
The whole Turborepo monorepo, TypeScript on PostgreSQL, yours to change and deploy. No per-seat charge and no provider in a position to alter the terms later.
Written For Diligence
Ten documents covering architecture, schema, API, security and the testing roadmap. Enough to survive an investor review, not just a demo.
We Publish The Gaps
No test suite, no migrations, no observability, security items still open. Graded in the documentation and repeated here on this page, so nothing surprises you afterwards.
Compare & Discover Why Clients Choose Us as
#1 Ready-Made Clone Solution Partner
| Criteria | Miracuves white label live streaming platform | Generic Clone Script | Custom Dev Agency |
|---|---|---|---|
| Time to Launch | 6 days (Production) | Unknown / DIY | 6-9+ months |
| Source-Code Ownership | ✔ Full | Often limited / encrypted | Usually yes |
| Feature Depth (Category Leader Parity) | High (feed, live, monetization) | Basic (upload & feed only) | Depends on budget |
| Security & Compliance | Strong (ISO mindset, GDPR-ready) | Minimal | Varies widely |
| Scalability & Performance | Cloud & CDN-optimized | Rarely considered | Depends on architecture |
| Monetization Options | Multiple (ads, gifts, subs) | Limited / needs custom work | Custom (more time & cost) |
| Admin & Analytics | Full-fledged dashboard | Very basic or missing | Custom build (extra cost) |
| Cost vs Speed vs Quality | Balanced | Cheap but risky | High cost, slow |
| Ongoing Support & Updates | Available with clear plans | Usually none | Depends on contract |
Not every route to a live streaming platform survives its first thousand hosts. This is where ours diverges.
Industries
Industries We Serve
The white label live streaming platform suits any operator building live social entertainment. Live streaming startups use the full stack from room engine through payouts. Talent agency networks lean on contracts, transfers and earnings tracking. Voice social operators use the seat model and audio formats. Karaoke and music platforms use the dedicated room type. Social gaming operators use the forty-five modelled game types beside live rooms. Dating platforms use the dating room format and one-to-one calls. Creator platforms combine short videos and the square feed with live. Regional entertainment groups use country, language and per-region revenue configuration. Systems integrators deliver client builds on a documented NestJS backend.
- 🎥 Live Streaming
- 🎙️ Voice & Audio Social
- 🏢 Talent Agencies
- 🎤 Karaoke & Music
- 🎮 Social Gaming
- 💬 Dating & Social
- 📱 Creator Platforms
- 🌍 Regional Entertainment
- 🎁 Gifting Economies
- 📺 Talk Shows & Panels
- 🏆 Events & Competitions
- 🚀 Agencies & Builders
Miracuves’ white label live streaming platform is built as an agency-aware live entertainment platform adaptable to any gifting-led social business, multi-region where your footprint requires it, and white-labelled entirely under your brand.
Changelog
Platform Release Log - Version History & Updates
| Version | Date | What's New |
|---|---|---|
| v2026.1 | Aug 2026 | Initial release. Live streaming platform with 15 room formats, four-currency economy, agencies, families, PK battles and moderation. |
Blog & Resources
Live Streaming Software - Latest Insights & Guides
Stay updated with the latest trends, guides and case studies on live streaming, creator monetization, gifting economies and talent agency operations.
Why Startups Choose a Ready-Made Live Streaming Entertainment Platform Over Custom Development
Last Updated on September 3, 2026 by Ashish Khan For startups entering the live entertainment…
Last Updated on August 13, 2026 by Yash Narayan Key Takeaways A modern content creation…
Live Streaming Monetization: How Video Platforms Use Gifts, Subscriptions, and Creator Rewards
Last Updated on May 25, 2026 by Rutuja Gaikwad Key Takeaways Live streaming monetization helps…
How Coins and Virtual Gifts Help Creator Apps Increase Engagement and Earnings
Last Updated on May 25, 2026 by Yash Narayan Key Takeaways What You’ll Learn A…
Periscope Revenue Model: How Periscope Makes Money in 2026
Last Updated on April 28, 2026 by vaideki Live streaming transformed social media by turning…
FAQ
White Label Live Streaming FAQ - Pricing, Rooms, Economy & Readiness
Everything you need to know about the Miracuves white label live streaming platform.
It is a complete social broadcasting product that you brand as your own. Fifteen room formats cover everything from single-host video through to multi-guest audio; viewers buy coins and spend them on virtual gifts; talent agencies sign hosts and earn a share of what those hosts generate; and family groups give regulars somewhere to belong. Underneath sit a NestJS backend of more than 200 endpoints, 74 Prisma models, a 44-route web client, a 15-route operator panel and an Expo mobile build.
Yes. What you run carries your name, your host contracts and your commercial terms from the first day. The software implements patterns common across the entire category rather than anything proprietary to one operator, and every policy that matters is yours to set: revenue splits, moderation thresholds, payout rules and agency agreements.
Pricing opens at $3,399 for a deployment that is branded and live. What moves that figure is the hardening you want finished before launch, how deep the mobile build needs to go, which media and payment providers you connect, and the infrastructure you choose to run it on.
Six working days on our side to rebrand, configure and deploy onto your infrastructure. The calendar usually stretches on your side rather than ours: brand assets, server access, your gift and game catalogues, and provider accounts for Agora, Stripe and messaging all need to arrive before we can finish. Pre-production hardening is quoted separately and we will be straight about how long it adds.
It is feature-complete and fully demonstrable, but the documentation grades it a production candidate rather than a finished system, and we would rather you heard that now. Feature depth scores 9 out of 10. Testing scores 1, because the repository contains no test files at all. Before opening to the public you will want demo credentials removed and seeded secrets rotated, the JWT guard registered globally, RBAC role names reconciled with the database enum, the admin token moved into an HttpOnly cookie, real certificates on HTTPS, Stripe webhook signatures verified, and Prisma migrations in place of db push.
Money enters as coins, purchased through Stripe. Spending coins on a gift executes as one database transaction: the sender balance drops, the value splits across platform, agency and host, and the recipient receives diamonds. Diamonds become beans, beans convert to withdrawable cash less a five percent fee, and an operator signs off every withdrawal. The default split is 30 percent platform, 10 percent agency and 60 percent host, adjustable per room type, per gift category and per region.
An agency is a talent organisation: it recruits hosts, holds their contracts and takes an agreed percentage of their earnings. It matters because supply here arrives in bulk through recruiters, and a platform without an agency layer gives them no reason to bring anyone at all. Families are the retention counterpart, social groups with leaders, ranks, contribution tracking and a shared treasury, built to hold viewers rather than to sign talent.
There is an Expo SDK 50 build covering the main viewer and host journeys. The documentation grades it a stub rather than a peer of the 44-route web client, and we raise that early because mobile depth is the gap buyers most often discover late. Taking it to parity is scoped and quoted alongside the build.
Documented starting targets are 100 simultaneous rooms, 500 viewers in each and 5,000 open socket connections, all comfortably within one deployment. The stated growth targets sit an order of magnitude above that and need work the current build does not contain: the Socket.IO Redis adapter for multi-instance, PostgreSQL connection pooling, a CDN in front of media, and clustering. Video itself travels through Agora, so streaming load never lands on your own servers.
Ten items are listed as immediate. In order of priority: strip the hardcoded demo credentials and rotate every seeded account, register the JWT guard globally so no unguarded route can ship, reconcile RBAC role names with the database enum, move the admin token into an HttpOnly cookie, rotate all default secrets, put real certificates behind HTTPS, and hash room passwords, which the build currently stores in plaintext. Stripe webhook verification and a proper Prisma migration history follow directly after.
All of it. The Turborepo monorepo transfers in full: a NestJS backend of 17 modules, a Next.js client across 44 routes, a Next.js operator panel across 15, the Expo mobile build, a Prisma schema of 74 models, the seven-service Docker Compose stack, the Nginx configuration and the GitHub Actions pipeline. Yours to modify, extend and relicense as you see fit.
No test suite, no Prisma migration history, no structured logging or APM, and no GDPR erasure, retention or consent tooling. The Socket.IO Redis adapter required for multi-instance is not installed. Every external provider runs on your own account, including Agora, Stripe, Twilio, Firebase and your SMTP host. Mobile covers core journeys rather than full parity. We would rather set that out here than let it surface after you have paid.
Let's turn your idea into
a live platform.
Get a free consultation, a clear timeline, and honest answers. We'd rather earn your trust than rush a sale.
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.
“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.
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.
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.
