Bigo Live Clone

You receive the full monorepo: a NestJS backend with over 200 endpoints, a Prisma schema of 74 models, a 44-route web app, a 15-route admin panel, an Expo mobile app, the Docker Compose stack and a ten-document technical suite. Everything is white-labeled under your brand with full source code ownership.

The ready-made build costs $4,299, one time. Rebranding and deployment to your server take 6 working days from our side. Anything that needs input from you, such as brand assets, hosting access, gift catalogs and Agora or Stripe accounts, can extend the calendar, and tailored work typically takes 2 to 8 weeks.

Viewers buy coins, and a gift costs coins. Sending one runs in a single database transaction that deducts the sender, splits the value across platform, agency and host, and credits the receiver in diamonds. Diamonds convert to beans, and beans withdraw to cash with a 5 percent fee after operator approval.

The defaults are 30 percent to the platform, 10 percent to the agency and 60 percent to the host. All three are operator settings, and configuration can be set per room type, gift category and region, so you can run different terms in different markets.

Agencies are talent organizations that recruit hosts, hold contracts by commission or salary, transfer hosts and take a configurable share. Families are social groups with leaders, member roles, contribution tracking and a treasury that exist mainly to retain viewers. Each has its own battle formats.

Not yet at full parity. The Expo SDK 50 app covers the core viewer and host flows today, while the web app has 44 routes. The remaining screens are completed to your scope during delivery, and we bring the app to full parity as tailored work, with scope confirmed with us.

Pre-launch items include removing demo credentials, registering the auth guard globally, moving the admin token to an HttpOnly cookie, verifying Stripe webhooks and replacing db push with migrations. We can set up an automated test suite for you. We plan this hardening alongside the launch.

Our initial targets are 100 concurrent rooms and 5,000 concurrent socket connections on a single instance. Agora carries the media, so video does not load your servers. Going beyond a single instance needs the Socket.IO Redis adapter, connection pooling and clustering, which we set up for you.

You need your own accounts for Agora, Stripe, Twilio, Firebase Cloud Messaging and an SMTP provider, plus MinIO or an S3-compatible store. Keys and billing stay with you, so there is no dependency on us for running the platform after handover.

Yes. Adding a feature means a Prisma model, a NestJS module and a route in the web app, and swapping a provider is an environment variable. The stack is mainstream, so your own engineers can extend it, or we can build custom modules for you.

The software does not decide that. Live streaming, virtual gifts, cash-out of earnings and data handling are regulated differently from market to market, and the operator is responsible for compliance where they operate. We supply tooling such as host approval, moderation and audit logs, and we do not give legal advice, so speak to a local adviser before launch.

Yes. Several of the fifteen room formats, including voice, karaoke and talk show, are audio-first and use the same seat management as video rooms. You can enable just those formats and leave the rest off, and the discovery filters will show only what you have switched on.

No. Agencies are a layer you can leave dormant while you recruit hosts directly. When you are ready, you approve agencies, share invite codes and set contracts. Because the data model already includes them, turning the layer on later does not require rebuilding anything.

Coin purchases flow through Stripe on your own merchant account, so the money lands with you first. Host withdrawals are requests that your staff approve, and the payout method is arranged with you during launch. We do not hold or route funds at any point.

The Expo mobile app covers core viewer and host flows, and we help with store submission. It is graded as a partial build next to the web app, so completing it to your scope is part of delivery, and we bring it to full parity if mobile is your main channel, with scope confirmed with us.

Yes. The stack is a Docker Compose definition over PostgreSQL, Redis and S3-compatible storage, so it runs on any provider that supports containers. Because you hold the repository, the database and the provider accounts, migration is an engineering task and not a vendor negotiation.

Your own provider accounts and their usage fees, servers, moderation staff and the hosts themselves are yours to bring. The hardening list, test suite, migrations, observability, multi-instance scaling and full mobile parity are all things we can set up for you, and we go through them before purchase so they are not a surprise.

Discovery already filters rooms by country and language, and revenue splits can differ by region. Translating the interface into additional languages is tailored work we set up with you, since the delivered interface is built for a single language by default.

No. We have no connection with Bigo Live. The name is used descriptively, the way the software industry refers to a platform with similar functionality. The code, design and graphics are written by our team, and nothing is taken from the Bigo Live website or apps. Third-party names remain the property of their owners.

The media layer runs on Agora, with publisher and subscriber tokens issued by the backend and a single account of yours behind it. Chat and presence use Socket.IO with Redis. The documentation describes provider changes as configuration for some services, but replacing the media SDK itself is tailored work we can set up, so ask before assuming another vendor is a drop-in.

Each gift is divided at the moment it is sent, using the shares you configured for platform, agency and host. The host collects diamonds, converts them to beans and raises a withdrawal request that an operator approves. How an agency settles with its own hosts depends on the contract type you enable, either commission or salary.

Yes, the split is configurable per room type, per gift category and per region, so one market can run different terms from another. Changing a share affects gifts sent afterward. Tell hosts before you alter terms, because payout trust is the thing that keeps them on the platform.

PK battles run in six formats, party rooms are one of the room types and games are part of the platform, with a catalog an operator can edit. Not every modeled game type is built into the web app, so check the demo for the ones you plan to promote and tell us about any others you need.

Through tools and your own staff. Hosts are approved before broadcasting, rooms can be age restricted, members report content into one queue, and operators can mute, ban, shadow ban, block keywords and force-close rooms. The software does not watch streams itself, so you still need people on the queue and a written policy.

Most operators start with a curated group instead of open registration, because host quality decides whether the first viewers stay. Approach agencies with a clear contract and share, invite a few strong performers directly and give them accurate payouts. Open registration comes later, once the review queue and policies are working.

Coin purchases and subscriptions run through Stripe on your own merchant account, and withdrawals leave through the cash-out method you configure. We can integrate local wallets or other processors for your build. Payment rules differ by country, so confirm that your processor supports the markets you plan to serve.

Yes, the mobile app is branded to you and published under your own developer accounts, and we can help with the process. Store approval is decided by the stores, and their rules on virtual currency and live content apply, so plan for a review period and do not promise a launch date to hosts.

A ready-made base costs far less than a custom project and is live much sooner, because the economy, seats, agencies and moderation already exist. A custom build makes sense only when your model differs from gifting at its core. In most cases it is cheaper to start ready-made and add specific extensions.