Bigo Live Clone Features: Fifteen Room Formats, One Economy
Most live-streaming clones ship one room type and a gift button. The engineering that actually decides whether a streaming platform works is the layer underneath: four separate currencies that have to reconcile, a revenue split applied at transaction time across platform, agency and host, an agency layer that brings the hosts in the first place, and a moderation stack that survives its first real incident. Here is what ships, grouped by who touches it.
Request a Live Demo →See PricingFeature 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.
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 ship alongside these.
Bigo Live vs Miracuves Clone vs Building From Scratch
What each route gives you on the parts that decide whether a streaming platform can actually pay its hosts.
| What decides it | Miracuves Bigo Live Clone | Building from scratch |
|---|---|---|
| Time to a working platform | Six working days | A multi-year programme with a senior team |
| Room formats | Fifteen, from solo video to PK arenas | One, and the rest arrive as rewrites |
| Currency model | Coins, diamonds, beans and points modelled separately | Usually one balance, which cannot express earnings versus spend |
| Revenue split | Applied at transaction time across platform, agency and host | Reconciled afterwards, which is where the disputes start |
| Agency layer | Native, with contracts, roles and sub-agency rates | Rarely built, and it is what brings the hosts |
| PK battles | Six formats with live scoring on gift value | The feature most often promised and least often finished |
| Moderation | Reports, strikes, appeals, shadow bans and an action log | A support inbox until the first serious incident |
| Source code | Full Turborepo monorepo, yours to redeploy | Yours, at the cost of building all of it |
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. The comparison that matters commercially is the second column against the third.
How It Works, End to End
One gift, traced from a card payment through to a host withdrawal, with every split and every balance change written down.
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 rather than an assertion. Voice rooms carry seats, multi-guest and co-host formats carry additional publishers, and scheduled events exist as their own type.
Viewers find the room
Discovery works by room type, country and language, with nearby rooms by distance alongside. Once 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.
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 the single most common way a streaming economy becomes impossible to audit.
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, with per-room-type, per-gift-category and per-region configuration behind those defaults. Applying the split at transaction time rather than reconciling later is what keeps host earnings defensible.
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.
Diamonds become beans become cash
Received gifts land as diamonds, diamonds convert to beans, and beans withdraw to fiat with a five percent 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 sit across fifteen admin routes, with eight KPI cards and revenue charts on the dashboard.
Every Feature Earns Its Place
Each module below exists because a live-streaming platform stops working without it, not because a competitor lists it.
| Module | Why it is in the base build |
|---|---|
| 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 actually built on, and what that means for the team who inherits it.
Why the currency model is the number that matters
A streaming front end can be built in weeks. What takes years is the economy underneath it: 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. Seventy-four models across 1,839 schema lines is not a boast, it is the consequence of modelling those things properly instead of collapsing them into one balance.
The stack is NestJS, Next.js and TypeScript on standard PostgreSQL, which matters when you hire against it and when a technical buyer runs due diligence on what you own.
What Is Not Included in the Base Package
The 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.
Named pre-launch work, not surprises
There is no test suite. There are zero test files in the build today. 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.
Schema is 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.
No observability. No structured logging, APM, metrics or alerting exists today. Without it, incident response on a live streaming platform is guesswork at exactly the moment guesswork is most expensive.
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.
Ten hardening items. Demo credentials, a global guard, RBAC alignment, admin cookies, secret rotation, HTTPS, upload limits and password hashing are named as immediate work in the documentation.
GDPR erasure and retention are not implemented, and the Expo mobile app is graded a stub rather than at parity with the web application.
Every external provider is your own account. Agora, Stripe, Twilio, Firebase Cloud Messaging, SMTP and MinIO all require credentials you hold.
This is a longer list than most platforms publish. We would rather you price the hardening into your plan than discover it after launch, and we scope and quote each item before any work starts.
See how Miracuves compares to agencies and freelancers
The deployment process, the pre-production list in full, and what to check on the currency model and moderation stack before you hire anyone - on the Development Company page.
Frequently Asked Questions
Why are there four currencies instead of one balance?
Can I change the revenue split?
Why does the agency layer matter so much?
Is the mobile app ready to ship?
Is there a test suite?
Can it run across multiple servers?
See a gift split three ways, live
Ask for the demo and we will send a gift, follow the platform share, the agency share and the diamonds landing on the host, then run a PK battle scored on gift value in front of you.
Explore the Bigo Live Clone
Ready to run a streaming platform you actually own?
Deploy in six working days with fifteen room formats, the four-currency economy, the agency and family layers and the operator panel included, your splits configured with you, and the full monorepo on infrastructure you own.
Talk to Us →Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by Bigo Live.
“Bigo Live Clone” is used descriptively. It is how the software industry refers to building a platform with functionality similar to Bigo Live, and how clients search for it.
The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from the Bigo Live website or applications.
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.
