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 Own the thread under the video, and the controls that keep it usable.
A short-video app where the discussion carries the product. Comments can be replied to, liked, pinned by the post owner and deleted, mentions reach the person named, the server caps how much any account posts in a day, a banned-word list screens each new comment, and a moderator can freeze an account. Shipped as source code under your brand.
Be live in 6 Days, backed by
Comment and report activity
Conversation Controls Overview
add, reply, like, unlike, pin, unpin, delete and the fetch calls behind them
daily uploads, stories, comments and replies, plus pin, image and profile-link caps
a platform-appointed account that freezes users and removes any post or story
GIFs reach chat and comments only once you add your own Giphy key
The code answers what those frameworks ask for. A certificate, if you need one, is issued to your own operating entity and is not claimed on this page.
6,000+ clients in 16 years of building
Chosen by 6,000+ client companies since 2010
01See it live
See It Running
Post a comment, reply to it, pin it, report it, then watch the same record surface in the admin panel. Every layer below is a running build, so nothing needs installing before you try it.
The mobile build: comment threads with replies and likes, pins the post owner controls, mentions, a block list, report sheets on posts, users and comments, and the activity list that carries the alerts.
miracuves@yopmail.com | User_321
Where the reports land: post, user and comment report tables, accept or reject on each one, the reason list you maintain, comment and reply deletion, the banned-word list, freeze and unfreeze, and moderator assignment.
admin | Admin_$321
The same comment thread on a desktop page, with the report sheet, the inbox built on Firestore, and video pages a search engine can read.
Demo Video Tour
Prefer a guided pass? Take 30 minutes with the product team and we will walk the thread, the caps and the report queue against your own policy.
Schedule a live walkthrough call.Screen By Screen
These are screens from the running build, not mock-ups. Step through what a viewer sees, what a creator manages, what an admin works through, and what the web build serves, so nothing about the thread or the queue is a surprise after you buy.
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 Clapper Clone App is a ready-made short-video platform in which the thread under the video is treated as a first-class surface rather than something bolted onto a feed like TikTok or Instagram Reels. Comments carry replies, likes, owner pins and mentions, and any one of them can be reported, screened against a word list, or removed by someone you appoint.
It runs on MXTok, the same codebase as our other short-video hubs, so one deployment is never presented to you as two products. What differs here is the argument: this page is for operators whose product depends on the discussion staying readable.
What Miracuves hands over:
The Flutter app, the Laravel web build and the admin panel all read the same comment tables through the same API.
App name, currency, languages, onboarding slides, reserved usernames and the legal pages are operator fields, not code edits.
Report reasons, daily ceilings, the banned-word list and the moderator role are configuration on day one, not a roadmap promise.
The Engine
The script is the Laravel API, the MySQL schema and the Flutter and Blade clients built on top of it. A TikTok Clone Script of this kind hands you the comment, report and settings tables directly, so your developers change a ceiling, add a report reason or widen a moderator permission inside code you own.
What the purchase settles:
Put plainly: a Clapper clone app is a working short-video product whose comment thread, report queue and per-account ceilings are already built, handed to you as source code you can reshape around your own policy.
Features
Twelve features, each one listed because the documentation describes it and the build carries it. They cover the comment thread itself, the reports it generates, the people who work those reports, and the ceilings that keep one account from drowning the rest. Nothing here is a roadmap item dressed up as a capability.
A comment can be added, replied to, liked, unliked and deleted by the person who wrote it.
Pinning a comment is reserved for the owner of the post, and the number of pins is capped.
A comment carries the users it names, so the mention becomes a notification rather than plain text.
Every new comment is checked against a word list you maintain, and a match is refused rather than queued.
Three report targets, each with its own table and each tied to a reason you defined in advance.
Reports arrive in lists an operator works through, one decision per row.
A platform-appointed account that enforces your rules without holding full admin access.
How much any one account can publish in a day is a number you set, and the backend holds the line.
Posts, stories, comments and replies are all reachable and removable from one panel.
An optional feature pack that parks an upload in a pending state until someone clears it.
Interactions are stored as an activity list and pushed to the device, with the user holding the switches.
An optional integration: GIFs appear only once you supply your own key, so the running cost stays yours to decide.
Most of what you see above is a pack or a setting, which means it can be switched off for a market or widened in code you own. It is not a fixed template.
Need something the list does not name, such as parental controls or a stricter age gate?
The Operator Side
A discussion-led app is only as good as the panel behind it. The admin build is a browser application covering seven roles, the report tables they work, the comment and reply records they can remove, and the settings form that holds every ceiling and every key.
List and edit accounts, freeze or unfreeze one, and promote a user into the moderator role.
Open the comment list for any post, the reply list under any comment, and delete either one.
Post, account and comment reports each get a list; accept to act, reject to dismiss.
Turn the age gate on, set the minimum age and the method, and require documents from creators.
Maintain the word list that refuses comments, and set every daily and pin ceiling.
Key metrics and charts on the landing page, with daily active users counted by a scheduled job.
Write an announcement with a title, text and image, send it to a device topic, and resend it later.
Clear or refuse pending posts, mark one featured or trending, and curate the hashtag list.
The same thread and the same report sheet, on pages a search engine can index.
One Flutter codebase for both stores, with the operator-facing details held in settings.
04Inclusions and what you pay
Deliverables
Eight deliverables, not one binary. Two store builds, a web build, the admin panel that works the reports, the API layer under all of them, your branding applied, publishing help, and a support window that is written down rather than implied.
Your branded Android build, with the comment thread, report sheets and block list in place.
The same build for Apple devices, off the same Flutter source.
A Laravel and Blade front end with the same thread, inbox and report sheet.
Where reports are cleared, comments removed, ceilings set and accounts frozen.
Every client talks to the same documented Laravel endpoints, token-authenticated per user.
App name, currency, colors, splash, onboarding and legal pages carry your identity.
Your cloud, your accounts, our hands on the setup and the listings.
A written window after go-live, with longer maintenance offered separately.
Pricing
A launch-ready white-label Clapper Clone starts at $3,999, paid once. That figure buys the same MXTok codebase our other short-video hubs ship from, so you are not paying twice for one product; what moves the number is scope you add on top.
What changes the figure: how many clients you ship · bespoke report workflows · a stricter age gate · extra moderator permissions · third-party keys and gateways · media storage and hosting · branding work · support level.
Professional
Pre-Built Launch PackageRight choice for: operators launching with the documented comment and report set as it stands
What the demo does is what you receive, under your brand, on infrastructure you control.
Get StartedEnterprise
Custom, Compliant & Large-ScaleRight choice for: teams needing their own policy encoded, or review rules that differ by market
Scoped and quoted against what you actually want changed, in writing, before work starts.
Request a Quote05Who it is for
Fits Best Where
This build suits operators for whom the reply is the point: the clip starts the exchange and the thread underneath is what people come back for.
Which means the same operators carry the harder obligation, because a busy thread is where spam, pile-ons and takedown requests show up first. Everything below is chosen for that: who has to read the thread, and what the panel gives them to act with.
Publishers whose clips exist to provoke a reply, and whose readers judge the product by whether that reply is worth reading.
Desks publishing short clips about a place, where a thread can turn hostile faster than a small team can read it.
Teaching channels where the question in the thread, and the answer under it, carry more value than the clip itself.
Brands that want short video of their own and cannot afford an unread comment sitting under it.
Operators whose audience skews young, where the gate at the front door matters as much as the thread behind it.
Studios and agencies shipping a branded short-video app for someone else, repeatedly, off one codebase they already know.
If your product lives in the replies, the thread stops being a feature and becomes the thing you operate. That is the case this build is written for.
Book a Free Strategy CallHow Operators Run It
Six ways operators actually run this build. Each one turns on a different part of the same control set, which is why they can share a codebase without sharing a product.
The clip is the prompt and the thread is the product. Pins decide what a new reader sees first, and the word list decides what never appears at all.
Nothing publishes until a person clears it. The uploader is told their post is pending, and the panel holds the queue.
A creator who cannot read every reply hands the account to someone who can, without handing over the login.
For audiences where who gets in matters as much as what gets said. The gate sits before full access, and the creator bar sits higher again.
The same discussion problem at speed. In-room chat runs live, and the host can silence or remove a viewer while the stream continues.
One-to-one chat is a pack, not a fixture. Run it, run it without GIFs, or leave it off and keep the conversation public.
Each of these runs on the one codebase, with different packs and ceilings switched on. What you choose at setup is what your operators live with every day after launch.
Book a Free Strategy CallIndustries
Twelve sectors where a watched clip turns into a thread somebody has to read.
The Miracuves Clapper clone is a short-video product whose comment layer is specified rather than assumed. A comment can be added with the accounts it mentions, replied to, liked and unliked, deleted by its author, and pinned or unpinned by whoever owns the post. Comments and their replies are paged, so a thread that runs to hundreds of entries stays readable on a phone.
Around that thread sits the control set. Readers report a post, an account or a single comment, choosing from reasons you wrote yourself; each report type lands in its own table with the reporter attached, and an operator either acts on it or dismisses it. A word list refuses matching comments outright. Daily ceilings cover uploads, stories, comments and replies, and a moderator role freezes accounts and removes posts and stories without being handed full administrative access.
Underneath, a stateless Laravel API serves a Flutter app, a Blade web build and the admin panel from one MySQL database, with media on local disk, Amazon S3 or DigitalOcean Spaces as you configure it. Chat and the live room state run through Firestore for latency, push goes out over Firebase Cloud Messaging, and housekeeping such as expiring stories, clearing old notifications and counting daily active users runs on scheduled cron endpoints. Each deployment is a single instance, not a shared tenancy.
Automated screening of images and video is available as an optional third-party integration, and an age gate with a minimum age and a checking method can be required before full access. None of this is a certification: the software supports the controls, while the policy, the people reading reports and compliance in each market remain yours. It ships white-label with the full source code, so a ceiling, a report reason or a moderator permission is something your own developers change.
06Under the hood
End To End
Follow one comment from the moment somebody types it to the moment an operator decides what happens to it. Six steps on the surface, six layers underneath.
A reader installs the app or opens the web build, then registers before anything else.
They watch something, then tap through to the comment sheet under it.
Readers who become posters run into the daily limits you set, enforced in the backend.
A new comment carries the accounts it names, and it is checked before it is stored.
Interactions become records, and records become pushes, unless the recipient said otherwise.
Whatever got reported lands in the panel, where somebody accepts it or dismisses it.
Behind The Scenes
Upload paths are validated and nothing stored is executed as code. The storage target is yours to pick: local disk, Amazon S3 or DigitalOcean Spaces.
Media is served through a storage link or a CDN you put in front of it, with paths issued by the backend rather than guessed by the client.
Comments, their likes and their replies each have their own table, with the pin state held on the comment row itself. Your developers read and extend those tables directly.
One master list of reasons feeds three report tables, one each for posts, accounts and comments. Every row keeps the reporter, and every row ends in an accept or a reject.
One settings row carries every daily ceiling, pin cap and integration key. Requests arrive with an API key and a per-user token, and moderator or admin actions are checked against the role before they run.
Activity notifications and admin broadcasts sit in their own tables and go out over Firebase Cloud Messaging. Scheduled endpoints expire stories, clear old notifications and count daily active users.
Technology
Nothing exotic, and nothing hidden. Every component below is named in the product documentation, with the optional ones marked optional so you can price the running cost before you commit.
Flutter (Mobile) · Php-Laravel (Web)LaravelMySQL / MariaDB · RedisZego · Agora · FFmpeg · HLSAWS · DigitalOcean · FirebaseGiphy · Sight Engine · Yoti · CloudflareEvery optional service above is a key in one settings row, so your team can swap a provider, drop one entirely, or point the build at a different cloud without waiting on us.
Growing Into It
A thread is cheaper to serve than a video and far harder to keep clean. This section is about both halves of that, described as the architecture actually is rather than as a slide would have it.
Growth in a discussion app shows up in three places at once: write volume on the comment tables, push volume on the notification path, and reading volume in the report queue your own staff have to clear.
The first two are infrastructure you can buy more of. The third is staffing, which is why the ceilings and the word list matter more than the server count.
The Laravel API holds no session state, so adding app servers behind a load balancer is the growth path. Heavy work runs off a Redis-backed queue worker rather than blocking a request.
Deployment goes onto an account you own, with the storage target set at install: local disk, Amazon S3 or DigitalOcean Spaces. Nothing routes through Miracuves after handover.
Media is served through a storage link, and a CDN in front of it is an operator choice rather than a bundled dependency. Paths are issued by the backend, never assembled by the client.
Renditions are generated after a post publishes, and the web player reads an adaptive manifest, so a reader on a weak connection still reaches the thread.
Comments, likes and replies are separate tables with indexes on the user, post and timestamp columns, and every list is paged. The daily ceilings are a capacity control as much as a civility one.
Said plainly, because it decides architecture: this is a single-instance product. Shared tenancy is not in scope, so a second brand means a second deployment of the same codebase.
Launch on one modest server if that is where you are. What stays fixed is the shape: stateless API, one database, object storage, a queue worker, each scaled on its own when the thread volume says so.
07Security and trust
Security
A thread app holds names, messages, reports and payment records. What follows is what the build does today and, where the product documentation calls something a recommendation rather than a shipped control, it is listed as work for your team.
The admin panel sits behind its own login and session, separate from the public app. Provider secrets for payments, live, push and GIFs are held in the settings table or the environment file, never in client code, and uploaded files are stored on a disk that does not execute them.
The data a thread app holds is identity, content, messages and report records. A reader can delete their own account from the app, your privacy policy and terms are served from the panel as your own text, and stories and old notifications are cleared by scheduled jobs.
Every API call carries a deployment-wide key plus a per-user token issued at sign-in and checked on each request. Web sign-in runs through Firebase, and a manager signs in on a token scoped to one creator.
Seven roles are defined: viewer, creator, seller, business, manager, moderator and admin. The split that matters for a thread app is moderator against admin, because a moderator enforces your rules without reaching settings or payouts.
The product ships two real defenses against a flooded thread: per-account daily ceilings held in the backend, and a word list that refuses a comment outright. Network-level throttling is not in the shipped route configuration.
A report is a row, not a notification that disappears. It keeps the reporter, the target and the reason you defined, and it stays until an operator accepts or rejects it.
Who Does What
You are buying software. No reviewers come with it and nothing here is legal advice. The build gives your safety work somewhere to happen: queues to read, reasons to pick from, ceilings to set and a role to hand out. The policy, the people and the law in each market stay yours.
Specifically, in the code: reports on posts, accounts and single comments, each against a reason you wrote; three report tables an operator accepts or rejects row by row; a banned-word list that refuses a comment on submit; daily ceilings on uploads, stories, comments and replies; a moderator role that freezes accounts and removes posts and stories; comment and reply deletion from the panel; a reader-managed block list; account deletion on request; an age gate with a minimum age you set; and optional third-party integrations for automated media screening and automated age checks. That list is readiness, not certification. Miracuves holds no audit, certificate or store approval for you.
Printed plainly, because the gaps shape your launch plan. There is no strike counter and no graduated warnings workflow: an operator deletes content or freezes an account. There is no audit trail of moderation decisions, no subject-access data export, no per-region content rules, and no parental controls. Each of those is scoped work on a codebase you own, and none of them should be discovered after you go live.
Writing the rules, wording the report reasons, staffing the queue and answering within whatever time you promised. Takedown notices and requests from law enforcement. Rights clearance for anything published. Your privacy policy, your terms, your published guidelines. The panel will hand an operator the row; deciding it is a person's job.
An age gate does ship: switch it on and it stands between sign-up and full access, with the minimum age and the checking method as operator settings, manual or through an optional third-party provider. Creators can face a higher bar again, with document checks you require. What does not ship is parental controls. If children will use your platform, scope that before launch, because the rules covering minors are the strictest you will meet.
What a thread obliges you to do depends entirely on where your readers are. The EU Digital Services Act and GDPR, the UK Online Safety Act, India's IT Rules 2021, and US COPPA where children are involved, each set their own duties on reporting, response times and transparency. Put the markets you are targeting in front of your own counsel. Miracuves is not your counsel and offers no regulatory opinion.
08Grow the platform
How add-ons work
At launch or later. The core is extended, never rewritten.
You get the scope and the figure in writing before anything starts.
It lands in the repository you already own, like the rest of it.
Advance Add-Ons
These are the gaps named earlier in this page, offered as work rather than hidden. Each one is a scoped module, quoted on request, and none of them is in the standard build today.
Graduated enforcement instead of delete-or-freeze: counted strikes, timed restrictions and a warning a reader actually sees.
An append-only record of who removed what, when, and under which reason, for the cases where you have to show your working.
A reader asks for everything you hold on them and gets a machine-readable file, rather than your team assembling one by hand.
Supervised accounts, restricted interaction for younger readers, and a guardian view of what a minor can reach.
Per-route limits on sign-in, upload and comment traffic, above the per-account daily ceilings the build already enforces.
Counts of reports received, actions taken and time to decision, exportable for the disclosures some regimes now require.
Different rules by country or city: what is visible, what needs review first, and which reasons a reader is offered.
The standard build is one instance per deployment. This module is the custom work that puts several brands on one core, each with its own domain and listings.
Elsewhere In The Catalog
This page argues for the comment layer. If your product is really about long-form channels, a paid catalog, booked videos or creator subscriptions, these are separate builds that already exist.
01A YouTube clone is a video-sharing platform built for uploading, managing, streaming, and discovering content across channels and categories.
Explore Solution
02A Netflix clone is a subscription-based streaming platform designed for watching movies, series, and premium video content on demand.
Explore Solution
03A Cameo clone is a platform for personalized celebrity video, on which users pay to request shoutouts from influencers, athletes, creators and actors.
Explore Solution
04An OnlyFans clone is a creator monetization platform where fans subscribe to access exclusive content, private interactions, and premium media.
Explore Solution09The business case
Where The Money Comes From
A thread people actually read is the asset; these are the five lines that turn attention on it into revenue, for the creator and for you.
Commission rates and platform shares are administrator settings, so the economics are yours to tune per market. The table below holds published third-party rates, not our projections.
One place a creator sees coins in, balance held and withdrawals requested.
Coin packs you price, spent on gifts under a post or inside a live room.
A monthly plan a creator sets, with your commission percentage on top.
Creator-run ad campaigns with a goal and a budget, plus rewarded ad units.
Gifts during a broadcast, pay-per-view unlocks, and replays where enabled.
A creator analytics pack, so earning decisions rest on their own numbers.
| Revenue stream | How it is charged | Take rateTypical range | What sets the ceiling |
|---|---|---|---|
| In-App Coins & Virtual Gifts | Viewers buy coin packs through the store, and its commission is settled before revenue reaches you. | 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 monthly fee gives fans premium access, and the creator and platform divide what the store leaves. | 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 | Brand deals are priced between brand and creator, and a platform takes a published share only on ads it serves. | 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 | Viewers pay to pin messages or join a live session, and the platform keeps its share 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 | A fee can apply when a creator moves a balance out to a bank or PayPal account. | 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
Our own revenue models appear earlier; the statistics below have other origins. YouTube, Meta, DataReportal and Pew Research released them, and we show them unaltered. From these, operators can gauge how much attention short-form video already commands, the advertising volume it supports at scale and how many users it has, which lets you check the business case against sources anyone can verify.
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.
Why Now
A vertical feed is no longer a differentiator; everyone has one. What is still hard, and getting harder, is a comment thread a stranger is willing to read to the bottom of.
Owning that thread means owning the rules on it, the staff reading it, and the record of what was decided. None of which you get on somebody else's platform.
A feed is a solved problem and a cheap one. The reason a reader comes back is the exchange underneath, and that is built out of pins, replies and the ceilings that keep the whole thing readable.
On a rented platform, the reasons a reader can report under, the words that get a comment removed and who counts as a moderator are all set elsewhere. Here they are rows in your own database.
The EU Digital Services Act, the UK Online Safety Act and India's IT Rules all put obligations on whoever hosts the discussion. Starting from a build that already has report tables and a moderator role is cheaper than retrofitting them.
The standard build goes live in 6 working days with publishing support. You spend the time you saved on writing the policy and hiring the people who will read the queue.
Report reasons, the banned-word list, the daily ceilings, the privacy policy and the terms are all text and numbers you enter. Nothing about how your thread is governed reads like a vendor default.
This page names what the build does not have: no strike ladder, no moderation log, no data export. You own the code, so each of those is a sprint rather than a support ticket to a vendor.
Roles the build defines, from viewer and creator through manager, moderator and admin
Things a reader can report: a post, an account, or one single comment
Feature packs in the build, with one left off by design because its keys are yours
Events that raise an alert: a like, a comment, a follow and a gift
Short video is where the audience already is. What is still open is who runs the conversation on top of it, and this build hands you the controls for that on day one.
The Commercial Case
A discussion app is cheap to serve and expensive to staff, which is the opposite of most video products. The commercial question is therefore not bandwidth but attention: how much reader time the thread holds, and how little operator time it costs to keep clean.
Text rows are the cheapest thing in the database, and they are what brings a reader back twice.
The post owner decides what a new reader sees first, which is editorial control that costs nothing.
A per-account daily roof is the difference between a busy thread and an unreadable one.
Readers who can see a report reason and a result are readers who keep posting.
Run properly over a year or two, what accrues is:
Illustrative planning scenarios, not measurements and not earnings estimates. They describe how the same control set tends to be staffed as a thread grows, so you can budget people alongside servers.
At this size the word list and the daily ceilings do most of the work, and the report tables are short enough for one person to clear between other tasks.
Typical of a launch: a single admin account, no appointed moderators yet, and the approval queue left off because nothing is arriving faster than it can be read.
Here the moderator role starts to matter: two or three appointed accounts that freeze and remove without reaching settings, keys or payouts.
Report reasons get rewritten at this stage, because the first list rarely matches what readers actually complain about once there are enough of them.
A thread this busy is where the pre-publish approval pack and the optional automated media screening earn their cost, because human reading alone stops keeping up.
It is also where the add-on modules stop being optional: a strike ladder, a moderation log and a transparency export are what a regulator or a partner will ask to see.
10Why Miracuves
Why Miracuves
You can buy a cheap script, commission a custom build, or take a product that already has the comment and report layer specified. The trade is speed against control, and the table below is where we think this build sits on it.
Six things that decide it, in our experience
Six working days on the standard build, with publishing support included.
No per-seat fee, no revenue share, and no vendor between you and a schema change.
This page lists what is missing as plainly as what ships, so your plan is real.
Twelve comment endpoints, three report tables, eight ceilings, one moderator role.
Each add-on gets a written scope and a figure before any of it is built.
Sixty days of guidance, six months of priority fixes, twelve months of updates.
| Criteria | MiracuvesMiracuves Clapper 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 |
| Comment Thread Depth | Replies, likes, owner pins, mentions | Flat comments, if any | Only what the brief asked for |
| Reports And Reasons | Post, account and comment, your reasons | Rarely more than an email link | Built to order, at cost |
| Abuse Ceilings | Eight server-side caps plus a word list | Client-side at best | Depends what you asked for |
| Moderator Role | Freeze and remove, without admin keys | Admin login shared around | Another sprint |
| Admin Over Comments | Comment and reply lists, delete either | Database access and hope | Scoped separately |
| Honesty About Gaps | Listed on this page, before you buy | Found after you deploy | Depends on the agency |
| Support Window | 60 days, 6 months, 12 months | None | Whatever the retainer 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 |
Start the conversation
Bring us the policy. We will bring the build.
Tell us what your thread has to withstand and who will be reading it. You will get a straight answer on what the standard build covers and what has to be scoped, before anyone talks price.
11Learn more
Blog & Resources
Stay updated with the latest trends, guides and case studies on short-video platform development.
Product4 questions
A ready-made, white-label short-video platform sold on its comment layer rather than its feed. Comments can be replied to, liked, pinned by the post owner and deleted; mentions notify the account named; a banned-word list refuses comments on submit; daily ceilings cap how much any account posts; and a moderator role can freeze accounts and remove posts and stories. It ships as Android and iOS apps, a web build with an optional progressive web app, and an admin panel, all under your brand.
The app is what a reader, a creator and an operator touch. The script is the Laravel API, the MySQL schema and the Flutter and Blade clients underneath, which is where a ceiling, a report reason or a moderator permission is actually changed. You receive both, with the full source code.
No. There are no groups, no clubs and no community spaces in this product, and we would rather say so here than let you discover it after purchase. What it does have is the public thread and the controls around it: comments, replies, likes, owner pins, mentions, report queues, ceilings, a word list, a block list and the moderator role. Discovery is by hashtag, by location and by search, not by joining anything. If grouped spaces are central to your product, say so on the first call and we will scope them rather than imply they are already there.
Flutter for the Android and iOS builds, PHP 8.1 with Laravel 10 for the API and the web build, MySQL or MariaDB with a Redis queue worker, and Firebase for web sign-in, chat and live room state. Live rooms use Zego, media processing uses FFmpeg, and storage is local disk, Amazon S3 or DigitalOcean Spaces as you configure it. A CDN in front of the origin is your choice rather than a bundled dependency.
Cost and go-live4 questions
The Professional tier starts at $3,999, paid once, live in 6 working days. That is the standard build with the comment, report and ceiling set described on this page. What raises the figure is scope you add: a bespoke report workflow, a strike ladder, a moderation log, a data export, parental controls or a stricter age gate. Each is quoted against a written scope first.
Six working days for the standard branded build, with app publishing support included. Each customization extends that, and anything custom carries a written scope and a figure before work begins.
Yes, and that is the normal arrangement. It is self-hosted on an account you own, with the storage target and every provider key set in your own configuration. Because the API holds no session state, moving it to another provider later is a deployment task rather than a rewrite.
Since 2010 we have delivered 9,000+ projects for 6,000+ clients, and the catalog holds 90+ ready-made solutions. This codebase already runs QifQif, a short-video platform operating regionally in the UAE. You get go-live in 6 days, full rebranding, the source code, 60 days of platform guidance, priority bug fixes for 6 months and product updates for 12 months. You also get a page that lists what the build lacks, which is rarer than it should be.
Revenue and legality2 questions
Readers buy coin packs you price and spend them on gifts, pay-per-view unlocks or creator subscriptions. Creators can also run their own ad campaigns with a goal and a budget. Your share of subscriptions, tips, shop sales and pay-per-view is a commission percentage you set in the admin panel, and creator balances and withdrawal requests are managed there too.
Building a short-video app with comparable features is ordinary practice. What matters is that you launch under your own name, branding and content, and that you meet the law and the store rules in every market you serve, which for a discussion app means content moderation, privacy and the rules protecting minors. This product is built by our own team and carries no code, design or content from Clapper or any other platform. Put your markets in front of your own counsel; Miracuves gives no legal advice.
Ownership and support3 questions
Yes, in full, with no per-seat fee and no revenue share. That is the point of the list of gaps on this page: each one is a change your own developers can make, in tables and settings they can read, without asking us first.
What is in the build: TLS on client traffic, a deployment API key plus a per-user token on every request, framework password hashing on the admin account, Firebase handling app sign-in, provider secrets held server-side, separate moderator and admin roles, and per-account daily ceilings. What is not in the build: two-factor on the admin login, request throttling at the route level, and an audit log of admin actions. All three are named as hardening in our own compliance notes, so scope them before you scale. The code is built to the controls ISO 27001 and SOC 2 ask for, but Miracuves holds no certification on your behalf and any certificate you need is issued to your own operating entity.
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, Mon-Sat, 10:00-19:00 IST. Longer maintenance is available as a separate 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 Clapper.
Read our full Legal Notice & Disclaimer →“Clapper Clone” is used descriptively. It is how the software industry refers to building a platform with functionality similar to Clapper, 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 Clapper website or applications.
Clapper 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.