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 The catalog, the cart and the seller payout arrive with the feed.
A shop and a short-video feed on one Laravel backend: products with stock and approval, cart and coupon checkout, orders, reviews, seller shops, registered businesses, wallets, withdrawals and refunds. The buyer never leaves for a second app, and the source code is yours.
Be live in 6 Days, backed by
Shop and order activity
Commerce Build Overview
viewer, creator, seller, business, manager, moderator and admin
browse, product page, reviews, cart, coupon, payment, orders, addresses
categories, product approval, orders, business requests, withdrawals, refunds
products, orders, order items, cancellations, reviews, business ledger
The build ships with a written security and VAPT readiness document, including the hardening items to close before you launch. It is not an audit, and no certification is held for you.
Serving 6,000+ clients in that time, from 2010 onward
Chosen by 6,000+ companies across the world
01See it live
Shop It Yourself
Put a product in a cart rather than read about one. Three live demos follow: the buyer app, the admin panel where products and refunds are cleared, and the browser shop. Credentials are printed next to each.
The shop as a buyer meets it: categories and product search, a product page with price, stock and reviews, cart and coupon checkout, saved shipping addresses, and My orders with cancellation.
miracuves@yopmail.com | User_321
Where the operator works: shop categories, product approval and rejection, the order list, business registration requests, business withdrawals and the refund queue, beside user and content moderation.
admin | Admin_$321
The same catalog in a browser: marketplace listing, product detail with gallery and buy action, the shop bag on the reel sidebar when the shop pack is on, and public business profiles.
Demo Video Tour
Prefer a walkthrough with questions? Take 30 minutes with our team and we will trace one order from the product page to the seller payout on your own numbers.
Walk through an order with us.Screen by Screen
These are real screens from the running build, grouped by who uses them: the buyer browsing and ordering, the seller or business listing stock and watching a balance, the admin clearing products and refunds, and the browser shop. Check them before you commit.
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 RedNote Clone App is a ready-made lifestyle and shopping app: a short-video feed with a real shop behind it, the arrangement RedNote is known for and the one TikTok adopted later with its own storefront. Buying happens where discovery happens, so a viewer who likes what a creator is holding opens a product page instead of a search engine.
Our build carries the whole commerce half as shipped code, not a roadmap: products, cart, orders, reviews and a seller dashboard, plus registered businesses with their own wallet, withdrawals and refunds.
With Miracuves, your RedNote clone arrives:
A single Laravel API and one MySQL database serve the Flutter apps, the web shop and the admin panel.
Name, logo, palette, splash screens and language belong to you. Nothing of ours remains visible in what ships.
Ten commerce tables, seventeen shop endpoints and nineteen admin controls are part of the same build as the feed.
The Engine
The script is the code itself: the Laravel API, the MySQL schema, the Flutter app and the admin panel that the product runs on. Our TikTok Clone Script guide covers how one of these is priced; what you receive here is the same thing for the commerce build, with the orders, order items, cancellation and business ledger tables already in place for your team to extend.
Taking the Miracuves commerce build means:
Put plainly: a RedNote clone app saves you from building a feed and a storefront as two projects. They are one codebase here, which is also why this page, the conversation-led hub and the sound-led hub are the same product with different arguments, never two separate clients.
Features
The twelve panels below follow one purchase from end to end: a product tagged on a reel, a catalog, a product page, a cart, an address, a payment, an order, a seller marking it shipped, a business balance, a withdrawal and, when it goes wrong, a refund. Each one is a surface in the running build, and the readiness of anything pack-gated is stated on its own panel.
A bag icon on the reel sidebar and in live, opening the products attached to what is playing.
A creator picks products while posting a reel, and the tags are written once the post exists.
Categories you define, filtered listings, product search and suggestions as a buyer types.
Price, sale price, stock, gallery and the ratings left by people who already bought.
One call carries the cart, the chosen address, an optional coupon and the payment method.
A buyer keeps several addresses, marks one default, and the order stores the one used.
Both sides of the same order: the buyer tracking it, the seller moving it along.
Any approved account runs a storefront: listings, stock and the sales that come from them.
A seller becomes a registered business, reviewed by you before it trades.
Sales, commission, withdrawals and refunds land in one auditable running balance.
A business asks to be paid out; you approve, reject or mark it paid.
A cancellation passes through the seller and then you, and the ledger records the money going back.
Commerce sits behind a feature pack, so the shop can be switched off for one market and on for another without a second build. Switched off, the bag and the tag row simply are not there.
Need product variants, tax tables or a shipping-rate engine? Those are scoped as separate modules.
Operator Queues
A marketplace lives or dies on its queues. Nineteen of the admin controls in this build exist purely for shop and business work: clearing products, opening orders, approving a business, releasing a withdrawal and processing a refund, each with a remarks field that travels back to the seller.
New listings arrive pending. Approve, reject or delete them before a buyer ever sees them.
The full order list with a detail view showing line items, totals, gateway and payment status.
Read the submitted name, license id and address, then approve, reject or suspend the account.
Three outcomes per request: approve it, reject it with remarks, or mark it paid once the money has moved.
Cancellations the seller has already passed on reach you here, and processing one writes a debit refund to that business.
The taxonomy buyers browse by is yours: add, rename or remove a category whenever the catalog shifts.
Set the platform share on creator product sales, the display currency, the coin value and the global limits, without touching code.
The payout methods a seller may pick from are a list you maintain, so a local rail can be added or retired without a release.
Sellers and businesses do not need the app; the browser carries the same storefront, orders and balance.
One Flutter codebase, with the commerce surfaces switched on or off from the panel rather than by shipping a new binary.
04Inclusions and what you pay
Deliverables
Eight deliverables, not a download. Two apps, a browser shop, the admin panel where orders and refunds are worked, the API layer, your branding applied throughout, help getting on both stores, and the support window after launch.
Your branded Android build with the feed, the shop, the cart and My orders in it.
The same build on iPhone, with the identical shop and checkout path.
The browser edition where the marketplace, product pages and business dashboards live.
The queues: products, orders, business requests, withdrawals, refunds, reports and global settings.
The Laravel API every surface talks to, with the payment, auth, streaming and storage integrations already wired.
Name, logo, palette, splash screens and language, applied across apps, web and panel.
Your cloud account, your domain, your developer accounts, with us alongside through both submissions.
Guidance while you configure the shop, then fixes and updates on a fixed window.
Pricing
A launch-ready white-label RedNote Clone starts from around $3,999, feed and shop together, and moves with the integrations, the payment rails and the scale you need.
What moves the number: payment gateways per market · product variants and tax rules · shipping logic · hosting and storage · branding depth · surfaces you publish · support window.
Professional
Pre-Built Launch PackageRight choice for: D2C brands, creator merch shops and regional marketplaces
You receive exactly the build the demo runs, rebranded and deployed on your own infrastructure.
Get StartedEnterprise
Custom, Compliant & Large-ScaleRight choice for: Retail groups, multi-country sellers and agencies running several storefronts
Or have the commerce layer reshaped around your fulfillment, tax and payout reality.
Request a Quote05Who it is for
Who It’s For
This build suits anyone whose revenue depends on someone buying what they just watched: brands, creators with products, retailers and the agencies that launch for them.
What separates these six from a plain video app is that each needs an order record, a seller balance and a refund path on day one, not in a later phase.
Stop paying to reach your own customers on a platform you do not own. Run the catalog and the content in one place you control.
A creator who already sells drops, prints or kit gets a storefront attached to the audience instead of a link in a bio.
Many sellers, one checkout, and a platform share taken on every line without chasing anyone for it.
Deliver a working storefront app to a client in days, then bill for the catalog work, the launch and the growth.
Run the sale inside the stream: the host pins stock, the audience opens the bag, and the order lands in the same panel.
A city-sized catalog with cash on delivery, local language and a short list of categories beats a global marketplace nobody browses.
If a sale is the point and video is how you get there, owning both halves beats renting a feed and paying a marketplace separately.
Book a Free Strategy CallSix Ways It Gets Used
The same build serves a single brand with one catalog and a marketplace with hundreds of sellers. What changes is how many business accounts you approve and who keeps the commission.
One brand, one catalog, one audience. The reel and the product page belong to the same app, so a campaign ends in an order rather than an outbound click.
Give every creator a storefront instead of a link in a bio, with their own listings, their own sales screen and a balance they can withdraw.
In categories where people read reviews before buying, the rating on the product page is the whole conversion story, and only buyers can write one.
Hundreds of sellers, one checkout. Each registered business carries its own balance, ledger and withdrawal history, and your share comes off each line automatically.
The host pins stock while broadcasting and the audience opens a bag without leaving the stream. Both sides of that are gated by the shop pack.
For a city-sized catalog, cash on delivery and a short category list matter more than a global marketplace. Both are configuration, not custom work.
Whichever of the six you recognize, the gap is never the video. It is the order record, the seller balance and the refund path, and those are already written here.
Book a Free Strategy CallIndustries
The same shop and feed is configured differently for each of these twelve sectors.
The Miracuves RedNote clone is a social commerce build: a short-video feed sitting on the same Laravel API as a shop with products, carts, orders, reviews and seller storefronts. Discovery feeds are served per request, with following, hashtag, location and nearby variants beside the main discover feed.
Commerce covers the full round trip. A buyer saves shipping addresses, applies a coupon, pays by card or on delivery and tracks the order. A seller lists stock, sees incoming sales and marks them shipped. A registered business holds a balance, a transaction ledger and withdrawal requests, and a cancellation can be refunded back through the same ledger.
Underneath sit Flutter 3.10 and later for the apps, Laravel 10 on PHP 8.1 and later for the API and web, and one MySQL database. Adaptive renditions are generated with FFmpeg behind a feature pack, never upscaling past the source height, and file storage points at a local disk, Amazon S3 or DigitalOcean Spaces. This version runs a single instance per deployment.
On the governance side there are report reasons you define, report queues for posts and users, moderator powers to freeze an account or delete a post, optional automated screening through Sight Engine, an optional age gate, and account deletion with configurable retention. Products and businesses pass your approval before they trade. Payment cards are handled by Stripe or PayPal and are not stored by the platform. Every part of it arrives as source you own.
06Under the hood
One Order, End to End
Six steps take a buyer from signup to a delivered order and a seller from a listing to money in a bank account. Every one of them is an existing screen and an existing endpoint.
A buyer registers by email, Google or Apple and adds the shipping address the checkout will use.
The discover feed plays, and where a reel carries product tags a shop bag appears on the sidebar.
On the reel composer a seller picks from their own products with a multi-select picker.
Outside the feed sits the catalog itself, with categories, search and full product pages.
One call carries the cart, the address, the coupon and the payment method, and the order is written.
The seller moves the order along and the business balance carries the sale, ready to withdraw.
Behind The Scenes
A listing carries seller, category, optional business, price, sale price, stock and gallery, and waits as pending until an admin approves it
Placing an order writes the order and its line items together, copying the shipping address onto the order and storing commission and seller earning per line
A tag row links a product to a post or to a live host, which is what lets the bag on a reel list exactly the right items
Stripe and PayPal are initiated and verified server-side with keys held in the backend; the order keeps its gateway and paid state, and no card data is stored
Each business holds a balance with total earnings, commission paid, withdrawn and refunded, and every movement is a ledger row storing the balance that followed it
A cancellation row keeps the reason, the refund method and a state that moves from pending approval through the seller decision to refunded by admin
Technology
This is the stack the running demos are built on, not an aspirational one. One Laravel API, one MySQL database and a single Flutter project serve the apps, the web shop and the admin panel.
Flutter 3.10+ · Laravel Blade + JSLaravel 10 on PHP 8.1+MYSQL / MariaDBZego · FFmpeg · Firebase · HLSAWS / GCP / DigitalOceanStripe · PayPalThe commerce schema is plain relational MySQL, so your team can add variant tables, a tax engine or a shipping-rate service without unpicking a layer of borrowed abstraction. Nothing about the stack ties you to a single cloud.
How It Runs
This section states the shape of the deployment plainly, including what the current version does not do. A buyer deserves the architecture, not an adjective.
A commerce platform carries a second kind of load that a plain feed never does: money that must reconcile. Orders, line items, commissions, balances and refunds are separate records precisely so a disputed figure can be traced rather than argued about.
Everything below is from the product documentation handed over with the code, including the items marked as out of scope in this version so you can plan around them instead of discovering them.
A single Laravel API serves the mobile apps, the web shop and the admin panel, against one MySQL database. There is no second service to keep in step.
The build is self-hosted on the account you nominate, so how it scales and what it costs are decisions your team keeps.
With the ABR pack enabled, publishing a reel seeds a rendition job and a scheduled worker expands the ladder with FFmpeg.
Uploads, product images and business logos go to whichever disk you configure, with the storage location set in one place.
Background jobs run as scheduled commands. This version deliberately ships without Laravel queue workers, and the documentation says so.
Stated plainly because it changes how you plan: multi-tenant white-label is out of scope in this version, so each brand is its own install.
Nothing here is load-tested on your behalf and no uptime figure is promised. What you get is owned code on your own infrastructure, which is what makes sizing, caching and queueing decisions yours to take when the numbers demand them.
07Security and trust
Security
A shop raises the stakes: you hold addresses, orders, payout details and money that belongs to other people. What follows is taken from the security document that ships with the build, including the items it lists as recommendations rather than as shipped behavior.
The handover includes a security and penetration-testing readiness document covering authentication, authorization, the API surface, file upload, payments and the admin panel. It is explicit that it does not replace a third-party test or a compliance audit, which is exactly why it is useful to your own reviewer.
Commerce widens what you hold: identity and contact details, shipping addresses, order history and the payout details a seller submits. Account deletion is implemented, privacy policy and terms are served from settings, and retention is yours to define.
Every API call carries a deployment Api-Key plus a per-session AuthToken stored server-side. The documentation states the shipped Api-Key is a shared default and must be changed per deployment and kept off the client.
Viewer, creator, seller, business, manager, moderator and admin are distinct. A moderator can freeze an account and remove content but does not approve payouts; a manager acts for a creator only within the permissions granted.
The security document ends with a checklist to complete before going live, and it is worth reading as a to-do rather than a feature list. Rate limiting on login and sensitive routes is on that list, which means it is not configured for you.
Card payments are initiated and verified on the server with keys held in the backend, and cards are never stored by the platform. Coin spending and balance debits are the places to insist on atomic updates, and withdrawals require an admin decision.
Marketplace Duties
Selling adds a second set of obligations on top of the content ones: returns, refunds, seller identity, tax and consumer protection. The software gives you queues and records for all of it. The policies, the people working those queues and the legal position in each market remain yours. Miracuves gives no legal advice.
In concrete terms that means: products arrive pending and need your approval; a business submits a name, license id and address and waits for a decision that carries your remarks; cancellations move through four recorded states before money goes back; every balance movement is a typed ledger row; reports on posts and users reach a queue; a moderator can freeze an account or remove content; optional screening through Sight Engine and an optional age gate exist; and account deletion is implemented. None of that is a certification. Miracuves holds no audit, no certification and no app-store approval for you.
Approval gates on products and on businesses, a refund path with a state per step, a ledger that explains every balance, order records that keep the address and gateway used, report queues on posts and users, moderator powers to freeze or delete, blocking, an optional age gate and account deletion. It arrives as source code you own, so you can tighten any of it.
Your returns and refund policy and the window it promises, the people deciding cancellations, delivery and fulfillment, listing rules for what may be sold, dispute handling, and your privacy policy, seller terms and community guidelines. The code can route a refund request; it cannot decide whether the buyer is owed one.
Registration captures a business name, license id and address, and the status field lets you suspend an account later. Whether that is sufficient identity checking, what tax you must collect and remit, and what you owe a seller and by when are decisions for your counsel and your accountant, not for a schema.
Two sets apply at once here. On content: the EU Digital Services Act with GDPR, the UK Online Safety Act, India IT Rules 2021 and US COPPA where children use the service. On selling: consumer protection, distance-selling and returns rules, trader information duties and tax in each market you take orders from. Have counsel review both lists. Miracuves offers no legal or regulatory opinion.
08Grow the platform
How add-ons work
Take a module at launch or once real orders show you the gap. The core is not rebuilt either way.
Every item below gets a written scope and a figure before any work begins.
A module lands in your repository on the same terms as the rest of the build.
Advance Add-Ons
These eight are not in the base build, and several are listed in the product documentation as gaps rather than features. They are here so you can price them honestly instead of discovering them after launch.
Size, color and option sets as first-class records. The base schema leaves an attributes field for simple cases only.
Zone-based rates, weight bands and tax tables at checkout. The base build prices an order from its line items alone.
Carrier integration, tracking numbers surfaced to the buyer and in-store pickup as a delivery option.
The ordered-concat helper exists in the app, but the drag-to-reorder strip on the edit screen does not. This module builds that interface.
Trackable codes that attribute a sale to the creator who tagged it, with its own payout rule.
The build bakes static images today. Animated overlays are named as a remaining gap in the editor documentation.
Sales by seller, by category and by period. The documentation marks reporting beyond the fund dashboard and ad stats as out of scope.
One core serving several brands. The current version is explicitly single-instance, so this is engineering work and is quoted as such.
Neighbouring Products
This build earns its keep when a viewer buys something. When the money comes from subscriptions, a back catalog or paid requests instead, one of these four is the honest recommendation.
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
Eleven revenue streams are documented for this platform, and the two that matter most here are the commission on a shop sale and the commission on a registered business sale. Both rates are set by you in the admin panel.
The difference from an advertising model is that your cut is recorded on the order line itself, next to the seller earning, at the moment the order is written.
Each order item stores the platform commission and the seller earning, at a rate you configure.
Orders tied to a registered business credit its balance as a sale, net of your share.
A separate percentage applies when a creator rather than a business is the seller, tunable by region or category.
The gifting economy does not disappear because a shop exists; coins, gifts and tips still run with their own commission.
Creator plans, unlockable posts, creator-funded promotion and rewarded ads are all documented streams you can switch on.
Minimum redemption, which gateways exist and whether withdrawals are open at all are settings, so you can pause payouts during an audit.
| 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
The benchmarks above describe attention. The argument on this page is narrower: when the product page is one tap from the video, you stop paying twice, once to be discovered and again to be bought from.
Owning both halves also means the order, the address and the review are records in your database rather than a report you download from someone else.
No marketplace fee schedule, no third-party storefront rules, and no intermediary standing between a buyer and the order record.
A creator or a shop registers as a business, submits a license id and an address, and waits for your approval, with no spreadsheet in the middle.
Stitching a video app onto a separate commerce platform is the slow, fragile path. Here both halves already share one database.
A rating is written after a purchase, which is a quieter but real advantage over a feed where anyone can praise anything.
In plenty of markets a card-only checkout kills the order outright. Cash on delivery sits beside card payment as a configured option.
The platform share on a sale is a number in your own settings, not a rate negotiated with a vendor who can revise it later.
Shop endpoints in the API, from category listing to order cancellation
Revenue streams documented for the platform, two of them commerce
Address endpoints, so a buyer keeps a real address book
States a cancellation passes through before money goes back
Those are counts from the documentation handed over with the code, not market forecasts. The figures above them come from their publishers; these come from the build itself.
The Commercial Case
A social shopping app has a simpler economic story than a pure content app: every sale is a measurable event with a commission on it. Growth comes from more sellers, bigger baskets and fewer abandoned carts, all of which you can see in your own tables.
Income is tied to a completed order rather than to attention you have to sell on again.
Each approved business adds listings and buyers you did not have to acquire yourself.
The bag opens on the reel that caused the interest, so the journey has one fewer place to leak.
A saved address, an order history and a review habit make the second purchase cheaper than the first.
Run properly, the same install tends to become:
We will not print an earnings figure we cannot source. What follows is only how the platform is usually configured at three audience sizes, and which revenue lines tend to be switched on at each. Your own basket size and commission decide the rest.
You are the only seller. Products, cart, coupon and orders are enough, with the commission setting irrelevant because the margin is simply yours.
Typical for a D2C brand or a single creator running merchandise, where the work is merchandising and content rather than seller operations.
Business registration, the approval queue, per-line commission and withdrawal handling all come into use, and someone now owns the refund queue as a daily job.
Typical for a curated marketplace or a creator network, where seller quality is the product and your commission rate becomes a real lever.
This is where variants, tax tables, shipping rates and seller reporting stop being optional, and where gifting, subscriptions and rewarded ads usually run alongside the shop.
Typical for retail groups and regional marketplaces. Plan the modules into the budget rather than discovering them at this stage.
10Why Miracuves
Why Miracuves
For a social shopping build there are really three routes: a ready-made product like this one, a cheap script that stops at a feed, or a custom agency project. The honest difference is where the commerce half comes from.
Six Reasons Buyers Pick Us
Branding, deployment and store submission inside one week.
Plain relational tables for orders and ledgers, with no obfuscated layer in the way.
Variants, tax, shipping and multi-tenancy are listed as modules on this page rather than implied as included.
Ten tables, seventeen shop endpoints and nineteen admin controls, not a plugin bolted to a video app.
Scope and price per module before work starts, so the budget does not drift mid-build.
Sixty days of guidance, six months of priority fixes and twelve months of updates, stated rather than hinted.
| Criteria | MiracuvesThis RedNote Clone Build | 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 |
| Shop, Orders and Refunds | Shipped: 10 tables, 17 endpoints | Usually a feed with no checkout | Built from zero, billed by the hour |
| Seller Payouts and Ledger | Business wallet with a typed ledger | Absent entirely | Possible, at project cost |
| Hosting | Your cloud, one instance per deployment | Often undocumented | Whatever the contract specified |
| Revenue Streams | 11 documented, commission rates configurable | One or two, hard-coded | Whatever you pay to have built |
| Operator Queues | 19 shop and business controls | Rarely more than a user list | Scoped screen by screen |
| What Is Not Included | Named on this page as quoted modules | Discovered after purchase | Priced as change requests |
| Ongoing Support & Updates | Available with clear plans | Usually none | Depends on contract |
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 catalog can be taking orders next week.
Bring the catalog, the markets and the payment rails you need. You will get a straight answer on what the base build covers and what has to be quoted.
11Learn more
Blog & Resources
Stay updated with the latest trends, guides and case studies on short-video platform development.
Product4 questions
It is a ready-made social commerce platform: a short-video feed and a working shop on one backend. The commerce half covers products with categories, stock and approval, a cart with coupon and payment, shipping addresses, orders with cancellation, buyer reviews, seller storefronts, and registered businesses with a balance, a transaction ledger, withdrawals and refunds. It ships as Android and iOS apps, a web app with an optional PWA, and the admin panel where those queues are worked, all under your brand.
The codebase is the same one. What this page argues for is the commerce half: ten shop and business tables in the schema, seventeen shop endpoints in the API and nineteen shop and business controls in the admin panel. Our conversation-led and sound-led hubs argue for different halves of the identical product. You are never buying two things, and one deployment is never presented to you as two.
Yes. Commerce sits behind a feature pack called shop, controlled from the admin panel. With it off there is no shop bag on a reel, no Tag product row on the composer and no shop icon, and the gate is fail-closed, so a missing or unreadable pack setting also reads as off. Note that this version runs one instance per deployment, so a genuinely separate brand means a separate install rather than a tenant switch.
Flutter 3.10 or later for both apps, Laravel 10 on PHP 8.1 or later for the API, the web app and the admin panel, and one MySQL or MariaDB database. Firebase handles authentication and direct messages, Zego handles live streaming with tokens issued by your backend, FFmpeg builds adaptive renditions, Stripe and PayPal take payments, and file storage points at a local disk, Amazon S3 or DigitalOcean Spaces. Hosting is your own account, on AWS, Google Cloud or DigitalOcean.
Cost and go-live4 questions
The Professional plan starts from around $3,999, paid once, with go-live in 6 working days and the shop included rather than sold separately. What moves the figure is the payment gateways you need per market, product variants, tax and shipping logic, branding depth and the surfaces you publish. Enterprise builds for retail groups and multi-country sellers are quoted against scope.
Six working days for the branded build, deployment and store submission support. The honest caveat is that your own preparation runs alongside: payment gateway accounts, the categories you want, your first listings and your returns policy. Any module from the list above is scoped and quoted in writing before it is started, and that scope sets its own timeline.
Yes, and it is the only way we ship it. The build is deployed to the account you nominate on AWS, Google Cloud or DigitalOcean, with your database, your storage bucket and your payment keys. Order records, buyer addresses and seller payout details live in your database, not in any system of ours.
Since 2010 we have delivered 9,000+ projects for 6,000+ clients, and the catalog holds 90+ ready-made solutions. For this build specifically: the commerce half already exists rather than being quoted as a phase two, the schema is plain relational MySQL your own team can extend, and the gaps are named on this page as priced modules instead of being implied as included. Delivery is 6 working days with full source-code ownership, 60 days of platform guidance, 6 months of priority bug fixes and 12 months of product updates.
Sellers & revenue2 questions
Every order line stores its price, the platform commission and the seller earning, so your share is recorded at the moment the order is written. A registered business accumulates those earnings in a balance with a typed ledger of sales, withdrawals, refunds and adjustments, each row keeping the balance that followed it. The business requests a withdrawal with a method and account details, and you approve it, reject it with remarks, or mark it paid. The commission rate, the minimum redemption, the available gateways and whether withdrawals are open at all are all settings. Coins, gifts, tips, subscriptions and pay-per-view run alongside with their own configurable commission.
Here is the precise state of it. The shop bag on a reel, the product bag in live, the host pin control and the Tag product row on upload are built and gated by the shop pack, and the web surfaces are deployed and smoke-tested on our staging build with the pack on. On the app side the same surfaces exist and the gating fixes are written, but they reach a device only with the next app build, and end-to-end device testing is recorded as pending. The plain shop, the cart, orders, reviews, seller shops and the business wallet are not in that category at all; they are long-standing parts of the product. We would rather you read that distinction here than find it later.
Ownership, security & support3 questions
Yes. The apps, the API, the web shop, the admin panel and the database schema are handed over with no revenue share, no per-seat fee and no commission to us on anything you sell. Add a variant table or a tax engine yourself if you prefer; nothing in the licensing stops you.
What is in the code: HTTPS and TLS required in production, an Api-Key plus per-session tokens held server-side, Firebase-backed user authentication, an encrypted admin password, seven separated roles, server-side payment initiation with keys in the backend, and no card data stored by the platform because Stripe or PayPal holds it. What is on the hardening list for you to close before launch: rotating the default Api-Key, rate limiting on login and sensitive routes, restricting cross-origin access, turning debug output off, limiting the scheduled-task endpoints, two-factor authentication for the admin and an edge or firewall layer in front of the origin. We hold no certification, no completed audit and no penetration-test result on your behalf, and the security document that ships with the build says so itself.
Sixty days of dedicated platform guidance while you configure categories, commission and gateways, then 6 months of priority bug fixes and 12 months of product updates. First response is under 2 hours, Monday to Saturday, 10:00 to 19:00 IST. Longer maintenance is available as an option, and because you hold the code your own team can work on it in parallel from day one.
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 RedNote.
Read our full Legal Notice & Disclaimer →“RedNote Clone” is used descriptively. It is how the software industry refers to building a platform with functionality similar to RedNote, 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 RedNote website or applications.
RedNote 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.