Bigo Live Clone Features: What a Streaming Platform Includes
This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product; counts are specification inventory from the supplied materials, not implemented or verified by this preview.
The currency model is the number that matters on a streaming platform. Trace one gift below, from card payment to host withdrawal.
Feature Set by Role
Three surfaces from one monorepo: a 44-route web app for viewers and hosts, a 15-section admin panel for operators, and an Expo mobile build covering the core flows. All proposed scope.
The viewer
Discovers rooms by type, country and language, joins live chat, sends gifts across categories including combo and luxury, watches short videos and a square feed, follows hosts and holds a multi-currency wallet. Follow, block and mutual followers, profile visitors, top fans ranked by gift value, search by username and hashtag, and nearby rooms by distance.
The host
Goes live in any of fifteen 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. Manages seats and co-hosts, runs PK battles, watches diamonds accrue and follows the conversion through to a withdrawal request.
The agency
Creation and approval, host invitation by code, six member roles, contracts by commission or salary, host transfers and sub-agency rates, with earnings tracked per host. In this category the agency layer is what brings supply, and here it is native rather than bolted on afterwards.
The family
One family per leader with three join policies, four member roles across leader, co-leader, elder and member, contribution tracking, a treasury and family-versus-family PK battles with ranking and leaderboards. This is the retention layer sitting under the gifting layer.
The moderator
Reports across seven content types, strikes with violation types and appeals, ban, mute and shadow ban records, blocked keywords and a full moderation action log. Live room monitoring sits alongside, because in streaming the incident happens while the room is open rather than afterwards.
The operator
Fifteen admin routes covering host applications, withdrawal approval, live room monitoring, report resolution, the gift and game catalogs, agency approval, audit logs and revenue settings, with eight KPI cards and revenue charts on the dashboard. Six notification categories with quiet hours, support tickets with attachments and an SLA, and thirteen legal and policy pages sit alongside.
Proposed Build vs Building From Scratch
What each route gives you on the parts that decide whether a streaming platform can actually pay its hosts. The Omnistu column is proposed scope, agreed in writing per project - not an implemented product. No prices or timelines are published for either route.
| What decides it | Omnistu proposed build | From scratch - what to ask |
|---|---|---|
| Room formats | Fifteen, from solo video to PK arenas | Ask how many formats ship first, and what each later one costs to add |
| Currency model | Coins, diamonds, beans and points modelled separately | Ask whether earnings and spend share one balance - if so, payouts cannot be audited |
| Revenue split | Applied at transaction time across platform, agency and host | Ask whether the split is applied at transaction time or reconciled afterwards, which is where disputes start |
| Agency layer | Native, with contracts, roles and sub-agency rates | Ask how professional recruiters are contracted - that layer is what brings the hosts |
| PK battles | Six formats with live scoring on gift value | Ask to see one running with live scoring, because PK is an easy feature to promise and a hard one to finish |
| Moderation | Reports, strikes, appeals, shadow bans and an action log | Ask what moderation exists beyond a support inbox, and whether actions are logged |
| Source code | Proposed: the full Turborepo monorepo, yours to redeploy - confirmed in your written quote | Ask what you own at the end, and at what total cost |
Bigo Live itself is the reference for what this category looks like at scale; it is not a product you can buy or self-host.
One Gift, Traced End to End
From a card payment through to a host withdrawal, with every split and every balance change written down. Proposed flow.
1 - A host goes live in a chosen format
The host picks one of fifteen room formats and the platform generates an Agora publisher token, so the path from a click to a broadcast is a real sequence. Voice rooms carry seats, multi-guest and co-host formats carry additional publishers, and scheduled events exist as their own type.
2 - Viewers find the room
Discovery works by room type, country and language, with nearby rooms by distance alongside. Inside, live chat, follows and the top-fans ranking by gift value all run against the same session, so the room is a social surface rather than a video element with a comment box.
3 - Coins enter the economy
A viewer buys coins through Stripe on your own merchant account. This is the only point at which real money enters, which is why coins are modelled separately from everything a host can earn. Confusing the two is what makes a streaming economy impossible to audit.
4 - The gift splits at transaction time
A gift is sent and the split is applied immediately: thirty percent platform and ten percent agency by default, leaving sixty percent to the host - defaults recorded in the supplied specification, all configurable per room type, gift category and region. Applying the split at transaction time rather than reconciling later is what keeps host earnings defensible.
5 - Competition turns viewing into participation
PK battles run in six formats - one-versus-one, team, room, family, agency and tournament - scored on gift value received during the battle, with live updates, winner determination and revenge battles. Leaderboards aggregate by gift value, and family and agency battles roll up to their own rankings.
6 - Diamonds become beans become cash
Received gifts land as diamonds, diamonds convert to beans, and beans withdraw to fiat with a configurable fee, with the operator approving each request. Four currencies exist because each answers a different question: what was bought, what was earned, what is withdrawable, and what drives ranking.
The operator sees all of it: host applications, withdrawal approval, live room monitoring, report resolution, gift and game catalogs, agency approval and audit logs across fifteen admin routes.
Every Feature Earns Its Place
Each module exists because a live-streaming platform stops working without it, not because a competitor lists it.
| Module | Why it is in the proposed base |
|---|---|
| Fifteen room formats | A platform with one format competes on nothing. Voice rooms, karaoke and dating rooms bring audiences that a solo video feed never will. |
| Four separate currencies | One balance cannot express what was bought, what was earned, what is withdrawable and what drives ranking. Collapsing them makes payouts unauditable. |
| Split at transaction time | A host who cannot see their share the moment a gift lands will not trust the platform, and reconciliation disputes at scale are unwinnable. |
| Agency contracts and roles | Professional recruiters bring the hosts. Without a configurable share and real contracts they have no reason to bring them to you. |
| PK battles in six formats | Competition is what converts passive viewing into gifting, and family and agency formats extend that from individuals to groups. |
| Family treasury and contribution | Gifting is the revenue layer; families are the retention layer that makes a viewer come back to a specific community. |
| Shadow bans and strikes | A ban that announces itself invites evasion. Strikes, appeals and shadow bans give moderation a proportionate response. |
| Moderation action log | In a live medium a decision has to be reviewable afterwards, because the content that prompted it is already gone. |
| Withdrawal approval | Money leaving the platform without an operator decision in the path is how fraud becomes irreversible. |
Forty-five game types are modelled with seven built into the web app, alongside daily check-in streaks, a lucky wheel, missions and platform events.
The Technology Behind the Features
What the platform is proposed to be built on, and what that means for the team who inherits it. Counts are specification inventory, not implemented or verified by this preview.
Backend
A NestJS application on Node across seventeen modules with forty-five services and over two hundred documented endpoints, with guards, interceptors and a global validation pipe, in a Turborepo monorepo with npm workspaces.
Data model
74 Prisma models and 29 enums across 1,839 schema lines on PostgreSQL, using JSONB and full-text search, covering rooms, gifts, agencies, families, moderation and the wallet, with seed data for gifts, games and demo accounts.
Web application
A Next.js App Router build across 44 routes with 50 components on React, Tailwind and Zustand, carrying discovery, live rooms, wallet, feeds and thirteen legal and policy pages.
Admin panel
A separate Next.js application across fifteen routes covering hosts, withdrawals, rooms, reports, catalogs, agencies, audit and revenue settings, so operator tooling is a real application rather than a page inside the consumer app.
Streaming
Agora for real-time video and audio, with server-side publisher token generation, so the broadcast path is authenticated rather than open - a proposed external dependency, not a verified integration.
Mobile
An Expo build covering the core viewer and host flows. The supplied documentation grades this a stub rather than parity with the web app, and we repeat that here rather than describing it as a finished app.
A streaming front end is the visible part. The economy underneath it is where the real effort sits: four currencies that each answer a different question, a split applied at transaction time across three parties, an agency layer with contracts and sub-agency rates, and a withdrawal path an operator has to approve. The stack is NestJS, Next.js and TypeScript on standard PostgreSQL, which matters when you hire against it.
Named Pre-Launch Work, Not Surprises
The supplied documentation for this build grades itself and names a pre-production list. We repeat it here rather than let it surface during your security review. This preview does not implement or verify any of it; each item is scoped, tested and quoted with you.
Reported gap: no test suite
The supplied documentation records zero test files in the build. A unit, integration and end-to-end suite is scoped work, and the documentation includes a testing roadmap to follow. This is the item most worth budgeting for before you take real traffic.
Reported gap: schema applied with db push
Not migrations. That is unsafe once production data exists. Converting to a Prisma migration history is early, cheap and important, and it should happen before your first real user rather than after.
Reported gap: no observability
The supplied documentation records no structured logging, APM, metrics or alerting. Without it, incident response on a live streaming platform is guesswork at exactly the moment guesswork is most expensive.
Reported gap: single-instance only
The Socket.IO Redis adapter needed for multi-instance deployment is not installed, so horizontal scaling requires that work first. Connection pooling and clustering sit alongside it.
The ten-item hardening list
The supplied documentation names a ten-item immediate list, including demo credentials, a global guard, RBAC alignment, admin cookies, secret rotation, HTTPS, upload limits and password hashing. GDPR erasure and retention are also recorded as not implemented, and the Expo mobile app is graded a stub rather than at parity.
Every external provider is your own account
Recorded in the supplied documentation: Agora, Stripe, Twilio, Firebase Cloud Messaging, SMTP and MinIO all require credentials you hold - proposed external dependencies, not verified integrations.
This is a longer list than most platforms publish. We would rather you price the hardening into your plan than discover it after launch.
Frequently Asked Questions
Why are there four currencies instead of one balance?
Because each answers a different question. Coins are what a viewer bought with money, diamonds are what a host received from gifts, beans are what converts to withdrawable cash, and points drive family and agency ranking. Collapsing them into one balance makes it impossible to say what a host actually earned, and that is the number a payout dispute turns on.
Can I change the revenue split?
Yes, in the proposed configuration. The defaults recorded in the supplied specification are thirty percent platform, ten percent agency and sixty percent host - proposed configurable defaults, not a price - and behind those sit per-room-type, per-gift-category and per-region configuration. The split is applied at transaction time rather than reconciled afterwards, so a host sees their share the moment a gift lands rather than at the end of a cycle.
Why does the agency layer matter so much?
Because in this category agencies are what bring the supply. Professional recruiters sign hosts and move them between platforms, and they will only do that where there is a configurable share and a real contract structure behind it. Creation and approval, invitation by code, six member roles, contracts by commission or salary, host transfers and sub-agency rates are all proposed base scope.
Is the mobile app ready to ship?
No, and we will not describe it as though it is. The Expo build covers the core viewer and host flows and the supplied documentation grades it a stub. Bringing it to parity with the 44-route web application is proposed additional scope. If mobile is your primary surface, plan for that before you buy.
Is there a test suite?
No. The supplied documentation records zero test files in the build, and we state that plainly because it is the kind of thing that should change what you plan rather than surprise you later. The documentation includes a testing roadmap, and a unit, integration and end-to-end suite is scoped work we quote before starting.
Can it run across multiple servers?
Not without work first. The Socket.IO Redis adapter needed for multi-instance deployment is recorded as not installed, so it runs as a single instance. Installing that adapter, along with connection pooling and clustering, is what takes the platform past one server, and it is named pre-launch work rather than a hidden limitation.
Independence and third-party names
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Bigo Live or BIGO Technology. "Bigo Live clone" is used descriptively - it is how the software industry refers to building a platform with similar functionality, and how buyers search for it. Bigo Live and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.
Discuss your scope by message
Tell us which surfaces you would switch on at launch - live rooms, gifting, games, VIP tiers - and where your first hosts come from. We reply by email with a scoped proposal - no calls required, no phone numbers collected.
