MirxAI
AI you own, from day one. Ready-made AI platforms live in 6 working days, or custom AI built by our engineers.
Explore MirxAINot sure where AI fits? Talk it through with an engineer, free.
Talk to an AI engineerFrom a first assistant to agents that run whole workflows. Full source code on every build.
Machine learning, computer vision and language models, on data pipelines built to last.
Production-ready AI products with apps, admin and full source code, branded as yours.
Where AI earns its keep in your market, with the platforms we have already built there.
Bring in AI engineers by the month, or hand us the whole build.
What we have learned shipping AI products, from our blog.
Prompt-to-app generation, credits and an admin console, with the full source code.
Explore the Bolt.new clone
8 ready-made AI platforms24 AI and data services100% source code ownership6 working days to launch
Meet the leadership+60
Ready-Made AppsHow to Build and Manage a Live-Streaming Agency NetworkRead the article AI MVP DevelopmentWhy Most Enterprise RAG Projects Fail in Production: How to Build Clean Knowledge Retrieval Without HallucinationsRead FinTech AppWhy Startups Choose a Ready-Made Multi-Asset Investment Platform Over Custom DevelopmentRead One deployment, one admin panel, and a language list you grow from the panel.
Your language list is served from the backend, and every entry points at a translations file you upload in the admin panel. Add a market, mark its default, switch one off, and the apps follow without a new release. Those files carry interface copy, so posts stay in the language their author typed.
Be live in 6 Days, backed by
Settings activity
What Changes Per Market
counted across limits, commissions, live and media, safety, integrations and branding
every language row points at a translations file you upload and edit in admin
one flag decides which locale a fresh install opens in before anyone chooses
the documented build runs as one instance, so a tenant per brand is scoped work
The translation files hold interface copy: labels, menus and onboarding text. Captions and comments stay in the language they were written in, and a right-to-left layout is not described anywhere in the product documentation. Both are work to scope, not something waiting in the box.
For 6,000+ clients worldwide since 2010
Relied on by 6,000+ companies the world over
01See it live
Live in Action
Open the admin panel first and find Settings, then Languages. That screen is where a market is created, a translations file is attached and a default is marked. The apps and the web build read that list, so whatever you change there is what a new user meets on first run.
The Flutter build: onboarding slides that finish on a language choice, discover and following feeds, search, live rooms, the coin wallet, the shop and a settings screen where the language can be changed again.
miracuves@yopmail.com | User_321
Everything configurable sits here: the language list and its files, onboarding slides, report reasons, daily limits, commission rates, payout gateways, user levels and reserved usernames.
admin | Admin_$321
The Laravel web build covers home, explore, search, profiles, upload, live, shop, wallet and settings, so a visitor can watch and publish without installing anything.
Demo Video Tour
Prefer a guided tour? Book a 30-minute call and we will open the language list, a translations upload and the onboarding editor on a running install.
Schedule a live walkthrough call.Swipe Journeys
These are screens from the running build rather than mockups. Two reward a close look: the create sheet a creator publishes from, and the admin settings area, which is where the language list and its translation files live.
02Proof
Client Reviews
Real feedback from founders and brands who launched their short-video platforms with Miracuves.
“Miracuves didn’t just build an app, they helped us shape a product. The short video platform they delivered was incredibly stable from day one, which is rare. Features like reels, filters, and real-time engagement worked seamlessly. Their team was responsive, detail-oriented, and actually cared about long-term scalability - not just delivery.”
“We were initially skeptical about building a TikTok clone, but Miracuves exceeded expectations. The UI/UX feels premium, and users immediately connected with the platform. What stood out was their backend architecture - it handled traffic spikes effortlessly during our launch campaign. They clearly understand both tech and business.”
“Working with Miracuves was smooth from start to finish. They delivered exactly what we envisioned - a scalable, feature-rich short video app with strong performance. The customization flexibility they offered helped us differentiate in a competitive market. Even post-launch, their support team has been proactive and reliable.”
“We evaluated multiple vendors before choosing Miracuves, and honestly, it turned out to be the best decision. Their TikTok-style app was not just visually polished but technically solid - smooth video playback, fast uploads, and a clean admin panel. What impressed me most was how quickly they adapted to our custom monetization needs. Within 3 months, we had a fully functional platform with real user engagement.”
Case Studies
See how founders and brands have used the Miracuves short-video platform to build real, revenue-generating short-video platforms across industries and regions.
A scalable short-video app built for multi-language audiences and low-bandwidth regional markets.
“Fast, scalable, and built for real users - Miracuves gave us a strong market entry.”Omar Yassa · Co-founder, QifQif Media Pvt. Ltd.
03The product
What Is It
A Moj clone is a short-video platform you deploy once and present in several languages, built on the same vertical-feed pattern people already know from TikTok, Instagram Reels and YouTube Shorts. The feed, the camera, live rooms, coins and the shop are the same build in every market. What changes per market is the language row, its translations file, the onboarding slides, the display currency and the policy text you wrote.
Vertical video is the surface. The locale layer underneath it is the reason one deployment can serve more than one audience.
With Miracuves, your Moj clone arrives:
Flutter covers Android and iOS, Blade and JavaScript cover the browser, and one Laravel API answers all three.
App name, logo, palette, splash screens and the display currency are all yours to set. No Miracuves mark ships in the build.
Interface labels and onboarding text change in the panel, so a wording fix never waits on a store review.
The Engine
A short-video clone script is the source code underneath the apps: Laravel 10 on PHP 8.1 or newer, one MySQL schema, a Flutter project and a Blade web build. All of it is handed over, so the locale layer can be extended rather than worked around.
Buying the Miracuves Moj clone script means you:
Put plainly: a Moj clone app is one short-video build, deployed once, presented in as many languages as you load into the panel, with the source code sitting in your own account.
Features
Twelve groups, read in the order a locale travels through the product: it is created as a row, given a file of translations, served to the clients, chosen at the end of onboarding and changed again later from settings. The last group names the two things the product documentation does not cover, so you can budget for them instead of discovering them.
Six fields describe a locale: a code, a title, a title in its own script, a file, a status and a default flag.
Interface copy lives in one file per language, uploaded and edited from the panel.
Clients ask the API which languages exist rather than shipping a list of their own.
A single flag decides which language a fresh install opens in before anyone picks.
First-run slides introduce the app, then hand over to the language step.
Anyone who chose wrongly at install can change it later without reinstalling.
Listing, adding, updating, deleting, defaulting, toggling and editing the file are all panel screens.
Display name and default currency are settings, so one build reads as a local product.
Coin packages and payout gateways are set per deployment, which is how a market gets a method it trusts.
Report reasons, reserved usernames and legal pages are authored by you, not fixed in code.
Beyond language, the feed can be read by location as well as by hashtag.
Two capabilities the documentation does not describe, stated here rather than implied.
Each group above is a table or a setting, and the code is yours, so any of this behavior can be widened, narrowed or rebuilt in your own repository. One caveat is worth repeating: a translated interface is not translated content.
Need something the list does not name, such as per-market content rules or a stricter age gate?
Control Center
The panel is where a deployment stops being generic. Languages and their translation files, onboarding slides, daily limits, commission rates, payout gateways, report reasons, user levels and reserved usernames are all edited here, and the three clients read the result.
Add, update, delete, enable or default a locale, and attach its translations file.
Add, edit, reorder or remove the first-run slides that end on the language step.
List, edit, freeze, verify and credit accounts, and review manager permissions.
Reach any post, story, comment or reply from one place, and remove it from there.
Work post and user reports against a reason list you authored for your own market.
Define coin packages and gifts, choose payout gateways, and clear withdrawal requests.
Set the platform share on tips, unlocks, plans and sales, plus the per-account caps.
Approve products and businesses, work orders and refunds, and run the fund pool.
Home, explore, search, profiles, upload, live, shop, wallet and settings all exist in the browser.
One codebase produces both store builds, and both talk to the same API as the web.
04Inclusions and what you pay
Deliverables
Choosing the Miracuves Moj Clone gets you more than one build artifact. You receive the whole short-video stack: two store apps, the web build, the admin panel, the API and the database schema, all wearing your brand.
A branded Android build produced from the shared Flutter project.
The same feature set, compiled for Apple devices from the same project.
A browser build for visitors who will not install anything first.
The screen your operators work in every day, and where every market setting lives.
One REST API serves the apps, the web build and the panel, with the integrations named up front.
Name, logo, palette and the starting locale set for the market you open in.
Server setup, configuration and store submission handled alongside your own team.
Bug fixes and configuration help after launch, with longer maintenance as an option.
Pricing
A launch-ready white-label Moj Clone starts from around $3,999, and the figure moves with platforms, integrations, scale and how much work sits on top of the base build.
What moves your total: support tier · integrations · infrastructure and scale · branding work · platforms (Android/iOS/Web) · feature depth · custom modules.
Professional
Pre-Built Launch PackageRight choice for: Funded startups, regional operators and multi-language launches
What you receive is the build the demo shows, wearing your branding and hosted in your own account.
Get StartedEnterprise
Scoped, Extended and Large-ScaleRight choice for: Large brands, media houses, telcos, enterprises & agencies
Or have the locale layer, the schema and the clients extended to fit a mandate you already hold.
Request a Quote05Who it is for
Who It’s For
This build suits anyone whose next market speaks a different language from the last one, and who would rather add a row in a panel than carry a fork per country.
The product is identical in every market, so your creators, your reviewers and your finance team learn one system instead of several.
You already run in one language, and the next audience needs the interface in words of their own.
A publisher whose audience is defined by the language it reads rather than by a border.
Audiences where one app has to open in more than one language from the first day.
A delivery team that wants the client wording held in a panel rather than in a pull request.
A brand that already pays for translated marketing and wants the app to read the same way.
An engineering team tired of cutting a release every time a label needs fixing.
If your growth plan reads as a list of languages rather than a list of features, one build with a locale layer costs less to run than a branch per market.
Book a Free Strategy CallWhere Teams Use It
The build does not change between any of these. What changes is the language list, the onboarding copy, the display currency and the policy text behind it.
Take a running deployment into one more language without branching the codebase to do it.
Build the entire product around one language that the global feeds treat as an afterthought.
Pair the locale with place, so what gets discovered reflects where the viewer actually is.
Several locales live at once, each with its own display currency and its own payout methods.
A short run where the crowd arrives in two or three languages and the copy has to be right immediately.
Lessons in short form, with every surrounding label sitting in the language the learner reads.
A locale here is a row and a file, not a branch. That is the entire argument for running one build across every market on your list.
Book a Free Strategy CallIndustries
Twelve sectors where the next audience speaks a different language from the last one.
The Moj clone is a short-video build whose per-market surface is configuration rather than code. A language row carries a code, a title, a title in its own script, a translations file, a status and a default flag, and the clients read that list from the backend instead of shipping one of their own.
Around it sit the settings that make a deployment feel local: the app name and display currency, the onboarding slides, the report reasons your reviewers work from, the reserved username list, the deeplink scheme and the store URLs. Each of those is edited in the panel, which is why a wording change never queues behind a store review.
Underneath, the stack is deliberately plain. Laravel 10 on PHP 8.1 or newer, one MySQL schema, a Flutter project covering Android and iOS, a Blade and JavaScript web build, and object storage on local disk, AWS S3 or DigitalOcean Spaces. The API holds no session state, so app servers are added sideways behind a load balancer.
Two limits are stated rather than glossed over. The translation files carry interface copy, so captions and comments stay in the language their author used, and a right-to-left layout appears nowhere in the product documentation. The documented build is also one app instance per deployment, so running several brands from a shared core is scoped work rather than a switch to flip.
06Under the hood
Process Overview
The surface is a vertical feed. Underneath runs a predictable order: the client asks which languages exist, the user settles on one, and everything after that is drawn from the file behind that choice.
The app arrives from a store, or the web build is opened in a browser.
Slides you wrote run once, then hand over to the language step at the end.
The chosen locale decides which translations file supplies every label.
The feed opens and the usual ways of finding things are all present.
A post is recorded or uploaded, captioned and sent to the feed.
The panel is where the deployment gets tuned once real people are on it.
Behind The Scenes
A Flutter app, a Blade web build and a Blade admin panel all speak to the same REST endpoints under one prefix.
Laravel 10 on PHP 8.1 or newer holds the business rules, and Eloquent models map onto a single schema.
Users, posts, comments, wallets, orders and settings share one database, indexed on the columns the feeds sort by.
One row per language, onboarding slides in a table of their own, and a settings record holding the app name and currency.
Uploads land on local disk, AWS S3 or DigitalOcean Spaces, decided per deployment by one configuration value.
Story expiry, notification cleanup, the daily active user count and the creator-fund calculation run on cron. The current design ships no queue worker.
Technology
Nothing exotic here. Laravel, MySQL, Flutter and object storage, with every integration named rather than hinted at, so your team can read the stack before buying it.
Flutter 3.10+ · Laravel BladeLaravel 10 (PHP 8.1+)MySQL 8 / MariaDBZego · FFmpegAWS / GCP / DigitalOceanFirebase · FCM · Stripe · PayPalThe API collection, the schema and the entity map all ship with the code, so your team can price the locale work it wants before the first sprint. One thing to note: the API key in the build is a placeholder and has to be changed per deployment.
Build to Scale
Growth here means more markets and more traffic against one build. A stateless API, one schema and storage you choose is the shape that keeps both affordable.
What the documentation supports is stated plainly below. What it does not support is named rather than implied, because a missing capability found after a launch date is set costs far more than one found here.
Read it as an engineering brief rather than a promise. Throughput follows the infrastructure you provision, and the provisioning is yours.
The Laravel API keeps no session state, so app servers sit behind a load balancer and are added or removed as traffic moves.
Uploads are written to local disk, AWS S3 or DigitalOcean Spaces, selected by one configuration value rather than a code change.
A single MySQL database carries users, posts, wallets and orders, indexed on the columns the feeds and the searches actually sort by.
Story expiry, notification cleanup, the daily active user count and the creator-fund calculation are all scheduled tasks, not background workers.
Every account carries its own per-day limit on how much it can post, tell or say back, each one a figure you type into the panel, so load is capped before it reaches the servers.
The documented product is a single app instance. Running several brands from a shared core is listed as out of scope, so treat it as work to quote rather than a setting to flip.
Starting in one language does not close the door on five. The locale layer is configuration, and the parts that are not, such as a tenant per brand or a quality ladder for playback, are named on this page so they can be budgeted instead of discovered.
07Security and trust
Security
A short-video platform running in several markets holds accounts, uploads, wallets and payout details. The documentation describes what the code already does and lists what you close before launch. Both halves are below, in that order.
Client traffic runs over HTTPS in production, and every API call carries a deployment key alongside the per-user token. The key shipped in the build is a placeholder: rotating it per environment and keeping it on the server is the first item on the hardening list, not an optional nicety.
An account can be deleted by its owner from the app or the browser. The privacy policy and terms are HTML you author and edit in the panel, retention for logs and backups is yours to define, stories expire on a schedule and notifications can be cleaned the same way.
Auth tokens are stored per device in a table of their own and checked on every request. Admin access is a server session with an encrypted password and CSRF tokens on the forms, and browser sign-in runs through Firebase Auth.
Viewer, creator, seller, business, manager, moderator and admin are separate roles. A manager acts for a creator under permission bits, and a moderator freezes an account or removes a post without holding full admin rights.
Uploads are written to the configured disk and served from a stored path, never executed. The security document names the checks to apply: allowlists for MIME type and extension, generated filenames, and size and dimension validation.
Card details never touch your server: Stripe and PayPal hold them. Coin spends, gift sends and unlocks are balance-checked debits recorded against a payment log, and every creator or business withdrawal waits on an admin decision.
Trust and Content Review
You are buying software. No reviewers arrive with it and none of it is a legal opinion. Miracuves builds the layer your trust-and-safety work runs on and hands it over; the rules, the people and the law stay yours in every market you open.
What ships: reports on posts, users and comments raised against reasons you wrote; report lists an operator accepts or rejects; a moderator role that freezes accounts and removes posts and stories; a banned-word check run against each new comment; blocking and a reserved username list; daily ceilings per account; an optional age gate through a provider or manual review; account deletion; and legal pages you author. Automated image and video screening is an optional integration on your own keys rather than a bundled service. None of this is a certification, and Miracuves holds no audit or store approval on your behalf.
Reports arrive against your own reason list and are worked from the panel. A moderator freezes accounts and removes posts and stories; an admin reaches comments and replies as well. New comments are screened against a word list you maintain, daily ceilings cap each account, and blocking plus reserved usernames close the obvious gaps. It arrives as source code, so any of it can be extended.
Takedown notices and law-enforcement requests, the reviewers working the list and the time they answer in, and rights clearance for the video, images and audio people publish. Your own community guidelines, privacy policy and terms of service too. The software routes a report to a person; it cannot decide one.
The age gate is optional and runs through a verification provider or manual review, with a minimum age and a separate creator minimum you set. Parental controls are not in the documented build. If minors will reach your platform, scope that work before the first market opens, because those rules are the strictest ones you will meet.
Adding a locale adds a jurisdiction. Transparency, reporting and response duties arrive from the EU Digital Services Act and GDPR, the UK Online Safety Act, India IT Rules 2021, and US COPPA where children are involved. Have counsel read every market on your list before you enable it. Regulatory and legal advice is not something Miracuves provides.
08Grow the platform
How add-ons work
Take one at launch or later. Either way the core is not rebuilt around it.
You get a written scope and a number before anything starts.
It lands as source code in the repository you already own.
Advance Add-Ons
The base build carries the locale layer. These eight are the modules buyers ask for next, and each one is scoped and priced on its own, at launch or whenever it becomes worth paying for.
Speech-to-text and subtitle packs sit in the codebase switched off and unproven, and the local transcriber writes in the spoken language only, so translating output is new work.
RTL appears nowhere in the product documentation, so mirroring the Flutter and browser layouts is a scoped engineering task rather than a setting.
The documented build is one app instance per deployment. Running several brands from one core is listed as out of scope and is quoted as custom work.
In-app AR filters run through a provider you register with yourself; filters are then added and edited from the panel like any other asset.
The sound tables arrive without rows. Pulling in a licensed catalog depends on a client ID registered in your own name, so the rights relationship stays yours.
Image and video screening is an optional integration on your own account, and what happens to a flagged item is a policy you write.
The quality-ladder and live-replay packs are switched off and unproven in the current build, so adaptive playback and saved streams are scoped rather than shipped.
GIFs reach chat and comments once a provider key is registered, which keeps that usage bill on your account instead of a bundled one.
More Entertainment Products
This build is one product in a wider video and creator catalog. If the plan reaches past a vertical feed, each of these already exists as its own product.
01A YouTube clone is a video platform for uploading, organizing, streaming and discovering content across channels and categories.
Explore Solution
02A Netflix clone is a subscription streaming platform for watching films, series and premium video on demand.
Explore Solution
03A Cameo clone is a marketplace for personalized video, where a fan pays a creator, athlete or actor for a recorded message.
Explore Solution
04An OnlyFans clone is a creator monetization platform where fans pay for private content and direct interaction.
Explore Solution09The business case
Monetization Machinery
Eleven earning lines are documented in the product, and every rate attached to them is a number you set in the panel rather than one we fixed in advance.
Coin package prices, payout gateways and the display currency are per-deployment settings, which starts to matter the moment your second market pays in a different unit.
Coins, gifts, plans and unlocks all land in one balance a creator can read and request against.
Viewers buy packages you priced, then spend them on gifts, with your commission applied on the way through.
A creator publishes plans priced in coins, and the platform keeps the share you configured.
A single post can be priced in coins, and unlocking it splits between creator and platform.
A pool pays out on qualified views, and creators pay you to promote their own posts.
Product sales, registered business sales and rewarded ad views each carry a rate of their own.
| Revenue stream | How it is charged | Take rateTypical range | What sets the ceiling |
|---|---|---|---|
| In-App Coins & Virtual Gifts | A viewer buys coins inside the app, so the store takes its share before anything reaches your ledger. | Apple: 15% up to $1M proceeds, else 30%. Instagram pays creators $0.01 per Star. | Apple publishes 30% as standard and 15% for developers under $1M in proceeds. Crossing the threshold mid-year applies the standard rate to later sales, and requalifying waits until the following year. |
| Subscriptions & Fan Clubs | A recurring fee buys premium access, and creator and platform divide whatever the store has left behind. | YouTube pays creators 70% of net membership revenue. | Net basis. YouTube's 70% applies to revenue after taxes and fees, and Apple's own cut on an iOS subscription is 30% in year one and 15% from year two. |
| Sponsored Content & Brand Collaborations | A brand and a creator settle the price privately; a platform only publishes a share for the ads it serves itself. | No published rate for private deals. YouTube pays 45% on Shorts feed ads. | Negotiation. For platform-served ads, YouTube lists 55% of net revenue on watch-page ads and 45% of allocated revenue on Shorts, a published split to price a rival program against. |
| Live & Premium Events | A viewer pays to be seen in a live room or to get in at all, and the platform keeps its cut of each payment. | YouTube pays 70% of the Super Chat revenue Google confirms. | Tax and iOS fees. YouTube computes its 70% after local sales tax and App Store fees on iOS and absorbs card costs, so a creator's cut of a viewer's gross payment is lower. |
| Creator Wallet & Earnings | Moving a balance out to a bank or wallet account can carry a fee on the rail that carries it. | PayPal Payouts: 2% of the payment, capped at $1.00 on US sends. | Rail cost. PayPal also offers a 0.25 USD flat fee through its API and caps international sends at 20.00 USD, so payout fees stay small against typical balances. |
How to read this. App-store rates are Apple's own published policy: the Small Business Program page and subscription terms, with the 30% standard rate in its newsroom release. Creator splits come from YouTube's earnings overview and its Super Chat page, the gift payout from Instagram Help, and the withdrawal fee from PayPal's fee table. Everything cited is a published rate. Brand-deal pricing has no public benchmark, so it is described rather than quoted. Keep these numbers as modeling inputs only, never as a quote or a statement of expected earnings.
Market Benchmarks
The rates above are ours to model with. The four figures below are not ours at all: YouTube, Meta, DataReportal and Pew Research published them, and they are reproduced here unchanged. Use them to size how much attention the short-video format already holds, against sources you can open and read yourself.
YouTube CEO Neal Mohan announced on 18 June 2025 that YouTube Shorts were averaging over 200 billion daily views, and YouTube's 2026 CEO letter, published on 21 January 2026, repeats that Shorts now averages 200 billion daily views. It is a publisher-reported measure of how much of a major platform's viewing now happens in the short-form vertical feed.
On its third-quarter 2025 earnings call on 29 October 2025, Meta said Reels now has an annual run rate of over US$50 billion. In the same remarks it reported that video time spent on Instagram was up more than 30 percent year on year. A run rate is Meta's own extrapolation of current revenue, not realized annual revenue.
DataReportal's Digital 2026 Global Overview Report, published in October 2025, uses Similarweb App Intelligence data for August 2025 to report that the typical TikTok user spends 1 hour and 37 minutes per day using the platform's Android app. That is the highest daily average among the leading social apps the report compares, and it is for Android usage only.
Pew Research Center reports in a short read published on 2 March 2026 that about four-in-ten US adults (37 percent) say they use TikTok, up from 21 percent in 2021, based on a survey of US adults conducted from 5 February to 18 June 2025. About six-in-ten adults under 30 (63 percent) are on the platform, and 68 percent of teens aged 13 to 17 use it.
YouTube Blog, Neal Mohan at Cannes Lions 2025: What 20 years of YouTube reveals about creativity’s future, 18 June 2025 - blog.youtube
YouTube Blog, YouTube CEO Neal Mohan’s 2026 Letter: The Future of YouTube, 21 January 2026 - blog.youtube
Meta Platforms, Inc., Third Quarter 2025 Results Conference Call transcript, 29 October 2025 - s21.q4cdn.com
DataReportal (Kepios), Digital 2026 Global Overview Report, October 2025, citing Similarweb App Intelligence data for August 2025 - datareportal.com
Pew Research Center, 8 facts about Americans and TikTok, 2 March 2026 - pewresearch.org
Every figure is a publisher’s own estimate, survey result or company statement, shown unaltered. Meta defines the Reels figure as a run rate rather than reported annual revenue. The TikTok time figure covers only the Android app. These describe the market and say nothing about how any Miracuves-built platform performs; none of it projects revenue for your business.
2026 Opportunity
Vertical video is where discovery happens now, and the audiences still badly served are usually served badly because of language rather than because of format.
A build you can present in a new language from a panel is the cheapest way to reach one of them.
Audiences cluster by language at least as much as by border. One deployment with a locale list follows them without a fork per market.
Your own build means you hold the accounts, the content rules and the earning lines instead of borrowing a feed that belongs to somebody else.
Interface text and onboarding slides live in the panel, so fixing a phrase in a new market never queues behind a store review.
Coins, gifts, tips, plans, unlocks, a creator fund and creator ads all arrive with the build, at rates you decide rather than inherit.
One language on day one, another when it earns its place. Neither the schema nor the API changes between them.
One Laravel API, one MySQL schema and storage you chose yourself means the monthly bill is yours to read and yours to cut.
Users watch short-form video every month across TikTok, Reels & Shorts
Minutes per day average users spend on vertical video on mobile devices
Global ad spend on short-form & creator-led video campaigns, growing every year
Brands shifting budgets from static ads to creator content & live shopping
Short-form video is no longer an experiment – it’s where your customers already spend their time. A TikTok clone app gives you the fastest, lowest-risk route to own your own platform.
Commercial Upside Here
A short-video build is a media surface, a creator economy and a shop at the same time. Which language it speaks decides how many of those it can actually serve, and here that is a setting rather than a rebuild.
Global feeds under-serve plenty of languages, and a focused app is more relevant by default.
Your library grows from the people using the app rather than from an in-house production budget.
Short vertical video earns repeat visits and long watch loops, which every earning line depends on.
Products, plans and paid posts sit inside the same surface people are already scrolling through.
Run well, a localized short-video platform can become:
These are patterns rather than forecasts, and no figure here is a projection. What a deployment earns depends on audience size, how many people publish, which earning lines you switch on and the rates you set behind them.
At this size the lines that actually move are coin gifts, a handful of subscription plans and the odd paid post.
It fits a first market, a language-first community, or an early test of whether the audience you picked will publish at all.
With two locales live, coin volume, subscriptions, rewarded ad credits and shop orders all start to register, and your commission settings begin to matter.
It fits funded operators, regional media and brands that already have translated marketing to point at the app.
At this scale the creator fund and creator ads are worth running, payout volume justifies more than one gateway, and pricing coins per market earns its keep.
It fits media groups, telcos and large creator networks with dependable creator supply in more than one language.
10Why Miracuves
Why Miracuves
A short-video build can come from a script vendor, an agency, a freelancer or your own team. What the comparison below is really about is how much you can still change afterward, because that is what decides whether a second market is cheap or expensive.
What Sets Miracuves Apart for Founders
A production build wearing your branding, not a prototype you are left to finish.
Source for the apps, the browser build, the panel and the API, with no per-seat charge.
A schema, an entity map, an API collection and a security checklist arrive with the code.
Locales, limits, commissions and gateways are panel settings, so markets never branch the code.
Every add-on carries a written scope and its own number, at launch or long afterward.
Delivery help through launch, then bug fixes and product updates on a stated clock.
| Criteria | MiracuvesMiracuves Moj Clone | 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 |
| Locale Controls | Table, file, default and panel actions | Hard-coded interface strings | Built to whatever brief you wrote |
| Security Documentation | A written VAPT readiness checklist | Rarely provided at all | Varies by the team you hire |
| Scaling Shape | Stateless API over one schema | Rarely thought about | Down to the architecture chosen |
| Monetization Options | Eleven streams, rates you set | Limited / needs custom work | Custom (more time & cost) |
| Admin Panel | Full panel, languages included | Very thin, or absent | Custom build (extra cost) |
| Cost vs Speed vs Quality | Balanced on all three | Cheap, and risky with it | Expensive and slow |
| Ongoing Support & Updates | Stated periods, in writing | Usually nothing | Whatever the contract says |
Changelog
| Version | Date | What’s New |
|---|---|---|
| v2026.1 | Jan 2026 | Updated UI, smarter AI feed, new monetization & live streaming modules |
| v2025.3 | Oct 2025 | Multi-host live rooms, AR lens pack support, referral module added |
| v2024.2 | Jun 2024 | GDPR compliance updates, 2FA for admin, geo-based content controls |
| v2024.1 | Feb 2024 | Creator analytics dashboard, in-app affiliate module, PWA support |
Let’s build together
Your next market can open without a second codebase.
The call costs nothing and the answers are direct: a timeline, a number, and the parts that are scoped work rather than settings. We would rather be right than quick.
11Learn more
Blog & Resources
Stay updated with the latest trends, guides and case studies on short-video platform development.
Product4 questions
A Moj Clone App is a ready-made white-label short-video platform you deploy once and present in several languages. It arrives as Android and iOS apps built from one Flutter project, a browser build, an admin panel and a single Laravel API over one MySQL schema. The language list is served from the backend, each locale points at its own translations file, and a new user chooses one at the end of onboarding.
Every locale is one row in a languages table carrying a code, a title, a title in its own script, a translations file, a status and a default flag. The panel lists, adds, updates, deletes, enables and defaults those rows, and lets you upload or edit the file behind each one. The clients ask the backend for the list rather than shipping their own, so adding a market does not need a new build.
No, and we will not imply otherwise. The translation files carry interface copy: labels, menus, buttons and onboarding text. Captions, comments and chat stay in whatever language their author typed. The speech-to-text pack that exists in the codebase is switched off and writes only in the language spoken, so translated content is work to scope rather than a switch to flip.
No. A right-to-left layout is not described anywhere in the product documentation, so we do not claim it. Mirroring the Flutter and browser layouts is a scoped engineering task, quoted on its own like any other module. We would rather say that now than after a launch date has been set for a market that reads right to left.
Price and launch4 questions
The Moj Clone starts from around $3,999 for the launch-ready white-label build: the Professional tier, paid once, live in 6 working days. The final number moves with branding, platforms, integrations, the modules you add and how much custom work sits on top. Enterprise scope for large brands, media groups and telcos is quoted after a written brief.
Six working days for the ready-made build with your branding on it, store submission help included. Custom work extends that, and anything custom gets a written scope and a price before it starts rather than after.
Yes. It runs on AWS, GCP or DigitalOcean inside your own account, and the disk the uploads land on is one configuration value: local storage, AWS S3 or DigitalOcean Spaces. Nothing in the stack pins you to a single provider.
Since 2010, Miracuves has completed 9,000+ projects for 6,000+ clients, and the catalog holds 90+ ready-made solutions. This build already runs as QifQif, a short-video platform operating regionally in the UAE. You get complete rebranding, source-code ownership, store publishing help, 60 days of platform guidance, 6 months of priority bug fixes and 12 months of product updates.
Creators and revenue2 questions
Eleven earning lines are documented: coin purchases, coin packages, gifts, real-money tips, subscription plans, pay-per-view unlocks, the creator fund, creator ads, shop commission, registered business sales and rewarded ad credits. Each commission rate is a panel setting, and every withdrawal waits on an admin decision before any money moves.
Building a short-video app with a familiar feature set is ordinary practice. What matters is that your platform carries its own name, branding, assets and content, and that you follow the law and the store rules in every market you open, moderation, privacy and the rules covering minors included. This build was written by our own team and carries no code, design or content from any other platform. Confirm your own obligations with counsel; Miracuves gives no legal advice.
Ownership, security and support3 questions
Yes. The Flutter project, the browser build, the admin panel, the API and the database schema are all yours, with no per-seat fee and no revenue share. The locale layer can be extended in your own repository without asking us first.
Traffic runs over HTTPS, every API call carries a deployment key alongside a per-user token, admin access is a server session with an encrypted password and CSRF-protected forms, seven roles are kept apart, and card details stay with the payment providers. The documentation also ships a hardening list: rotate the shipped key, add route-level rate limiting, restrict CORS and the cron endpoints, and consider two-factor for admin accounts. Those are items to close rather than claims we make for you, and no certification is held on your behalf.
Yes. Every launch carries 60 days of dedicated platform guidance, 6 months of priority bug fixes and 12 months of product updates, with a first response in under 2 hours, Monday to Saturday, 10:00 to 19:00 IST. Longer maintenance is available as an option.
An engineering service, a delivered project, helpful articles, one-time pricing and a market overview.
Disclaimer
Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by Moj.
Read our full Legal Notice & Disclaimer →“Moj Clone” is used descriptively. It is how the software industry refers to building a platform with functionality similar to Moj, 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 Moj website or applications.
Moj 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.
Got an app in mind? Let's talk on WhatsApp.
Hi! What are you building? Pick one and a real person replies in under 2 hrs.
Hi Miracuves! I am interested in a ready-made app.
Leaving already? Take this with you.
Pick any of our 90+ ready-made solutions. We brand it, launch it and hand over 100% of the source code.
"We had a hard regulator date for a cross-border neobank. Accounts ledger, KYC and card issuing came off their shelf; we added the corridor FX engine and our partner bank's settlement layer. We hit the milestone with room to spare, which would not have happened from a standing start."
Peter Lu · Managing Director, Apex Vertex Capital Holdings Ltd
Tell us what you are building. A real person replies in under 2 hrs, Mon-Sat.
Or claim it on WhatsAppA real person replies in under 2 hrs, Mon-Sat, with your launch plan. Want it sooner? Pick a 15-minute slot.
"We had a hard regulator date for a cross-border neobank. Accounts ledger, KYC and card issuing came off their shelf; we added the corridor FX engine and our partner bank's settlement layer. We hit the milestone with room to spare, which would not have happened from a standing start."
Peter Lu · Managing Director, Apex Vertex Capital Holdings LtdOptional. Paying in full works too.
25% off the published price of any ready-made solution ordered by 30 October 2026. The extras are included with every ready-made solution order. We submit to your own Google Play and Apple developer accounts and fix any technical rejection until the apps are approved. Rejections over store listing details (descriptions, screenshots, policy links and other metadata) are yours to update; review times are set by Apple and Google. The 6 working days start once your branding, hosting and accounts are ready. We reply in under 2 hours, Mon-Sat.