DramaBox Clone Features: One Catalog, Many Markets
Most short-drama platforms can serve one language well. This one is built so that opening a second market is a console job rather than a release - five locales, right-to-left on every surface, and interface copy the operator owns. Here is every capability, grouped by who touches it.
Request a Live Demo →See PricingFeature Set by Role
Every capability grouped by who actually touches it - the viewer in whichever language they arrived in, the wallet deciding whether an episode opens, and the operator running catalog, copy and economy across markets.
Viewer & Player
- Vertical episode player with sequential play
- Language picker on the consumer web app
- Right-to-left layout for Hebrew and Arabic
- Categories, titles and numbered episodes
- Episode 0 as the trailer convention
- Banner, trending, new release and coming soon rails
- Subtitle track from a stored VTT or SRT file
- My List, likes, comments capped at 400 characters
Wallet, Coins & Rewards
- Free episode window set from one setting
- Coin unlock priced per episode
- Rewarded ad unlock with a per-title daily cap
- Reward and purchased coins tracked apart
- Spend draws reward coins first, promos carry an expiry
- Seven typed ledger codes for earn and spend
- Currency catalog with a default for checkout
- Seven day check-in ladder, referrals and bonuses
Operator Console
- App language JSON editing without a rebuild
- Series language catalog kept separate from UI copy
- Default locale set from settings
- Film category, film list and episode modules
- Drag and drop episode reorder with relocking
- Coin packs, VIP plans and order history
- Block, comment hide and report queue
- 24 permission modules across four actions
DramaBox vs Miracuves Clone vs Building From Scratch
The same capability, three different paths to get it - weighted toward what a multi-market operator actually needs.
| Capability | Original DramaBox | Miracuves Clone | Build From Scratch |
|---|---|---|---|
| Locale coverage | Broad, market by market | Five locales shipped: English, Hebrew, Hindi, Arabic, Spanish | One language, then a retrofit per market |
| Right-to-left layout | Yes | Hebrew and Arabic across web, store build and console | Touches every screen you have already built |
| Who owns interface copy | Internal teams | The operator, through app language JSON editing in the console | Developers, via a release, every time a string changes |
| UI copy vs content language | Separated | Series language catalog kept separate from interface copy | Commonly conflated, then painful to untangle |
| Payment rails per market | Yes | PayPlus hosted plus Stripe, Razorpay, Flutterwave and Play switches | One gateway, then an integration per territory |
| Per-episode monetization | Yes | Coins, rewarded ad and VIP window on the same episode | An entitlement model before you write a player |
| Wallet correctness | Yes | Two balance types, seven typed ledger codes, unique keys on unlock rows | Where most builds leak money or double-credit |
| Source code ownership | N/A | Full ownership, self-hosted | Full ownership (you are building it) |
| Content licensing | Held by DramaBox | Not included - you supply and license your catalog per territory | Not included - you supply and license your catalog |
| Price | N/A | $3,399 one-time | Roughly a year of engineering |
The demo catalog that ships is original seed material with royalty-free stills, not licensed third-party drama. Rights clearance is per territory, which is exactly the cost that grows when you open a second market - see Development Cost.
How It Works, End to End
Follow one viewer, in one language, from landing to paying - and then follow the operator opening the next market.
Arrive in a Language
- Default locale comes from settings
- Viewer can switch with the language picker
- Hebrew or Arabic flips the layout, not just the strings
- Rails, search and For You render in that locale
- Series language catalog is separate from interface copy
Hit the Wall, Choose a Tender
- Access resolved at read time from four facts
- Locked in catalog, inside the free window
- Active VIP window, or an existing unlock row
- Coins, rewarded ad and auto-unlock write the same row
- Checkout displays through the currency catalog
Open the Next Market
- Operator edits app language JSON in the console
- No rebuild and no release to change client copy
- Enable the payment rail that market expects
- Same catalog, same wallet, same ledger behind it
- Coin price and free window tuned per market
That third card is the difference. On most platforms a new language is an engineering ticket; here the interface strings live in the console, so the constraint becomes translation and licensing rather than release cycles.
Every Feature Earns Its Place
Nothing here is on the list because it demos well. Each capability exists because leaving it out breaks something specific for an operator running more than one market.
| Capability | Why it is not optional |
|---|---|
| Operator-owned interface copy | Because otherwise every wording fix in Arabic is a developer ticket and a release, and a market you cannot iterate on is a market you will not grow. |
| Series language kept separate from UI language | Because a Hindi interface does not mean a Hindi catalog. Conflating them means a viewer switching language loses the titles they were watching. |
| True RTL, not a stylesheet flip | Because Hebrew and Arabic markets are underserved precisely because most platforms treat right-to-left as a CSS afterthought and it shows immediately. |
| Currency catalog with a default | Because a coin pack priced in one currency and displayed in another is the fastest way to lose a checkout. |
| Multiple payment rails | Because the gateway that works in one territory frequently does not exist in the next, and hosted checkout keeps card data out of your database either way. |
| Two balance types in one wallet | Because promotional coins and paid coins are different liabilities. Pooling them means you cannot expire a promo without confiscating money a viewer paid. |
| Seven typed ledger codes | Because "balance changed" is unanswerable when a viewer disputes a spend, and disputes arrive in every language you serve. |
| Unlock resolved at read time | Because caching entitlement is how a viewer ends up locked out of an episode they paid for on another device. |
| Unique compound keys on unlock rows | Because a double-tap on a slow connection should not charge twice, and slow connections are the norm in the markets this format grows fastest in. |
The Technology Behind the Features
A Vite and React consumer web app served as a static single page application, a Next.js 14 operator console on its own subdomain, and a Flutter GetX store build for iOS and Android. All three talk to one Node.js and Express service running roughly 202 registered handlers across a client router and an admin router, behind nginx and PM2. State is 33 Mongoose models on MongoDB: categories, titles and numbered episodes carrying lock state and coin price; reward and purchased balances against a seven-code typed ledger; unique compound keys on the per-user unlock rows; and indexes on active titles, release date and ledger timelines. The locale provider covers five languages with right-to-left support on every surface, and the same five locale packs serve the console as serve the consumer app.
What Is Not Included in the Base Package
Every capability above is built and demonstrable in the live demo. These are not - and the hub says so too, because it is the kind of thing that surprises buyers otherwise.
Stated against the feature, not implied away
The first item matters most if you are opening markets: the locale framework is complete and RTL is real, but the translated strings themselves are yours to finish. The last five are named in the platform's own VAPT reference as a labelled hardening backlog rather than buried, and they are closed with you at deployment.
See how Miracuves compares to scripts, freelancers and agencies
The deployment process, the content-licensing reality per territory, and what to check before you hire anyone - on the Development Company page.
Frequently Asked Questions
What languages does the interface support?
Can I add a language that does not ship?
Is the catalog language the same as the interface language?
How does episode unlocking actually work?
Can I price differently in different markets?
Which payment gateways are supported?
See it running in Arabic before you commit
Request a working demo of the catalog, the unlock paths and the console, in whichever locale matters to you.
Explore the DramaBox Clone
Ready to launch across more than one market?
Deploy in 6 days with five locales, right-to-left support and operator-owned interface copy included, full source code ownership.
Talk to Us →