Prime Video Clone Features: The Multi-Model OTT Storefront in Full
A pure subscription service asks every viewer to buy the whole catalogue to watch one film. A storefront does not. The same title can carry a subscription entitlement, a rental window, a purchase price and an ad-supported tier at once, and third-party partners can list their catalogues alongside yours on a revenue share you define.
Request a Live Demo →See PricingFeature Set by Role
A viewer can subscribe, rent a new release, buy a boxset and watch a free ad-supported title in the same session, and the ledger accounts for all four correctly. Partners and operators each get their own console.
Viewer
Catalogue, playback, profiles and discovery, across Android, iOS and the browser.
- Email, social and OTP sign-in with QR handoff to television
- Household profiles with separate history, recommendations and kids maturity filtering
- Hero banners, trending, new release and leaving-soon rails, genre and cast browsing
- Films, series, seasons, episodes, trailers, extras and priced boxsets
- Live channel line-up with free, plan-gated or ticketed access
- Adaptive quality, subtitles, multiple audio tracks and 360 VR-ready playback
- Watchlist and Continue Watching synced across devices per profile
Content partner
Third-party catalogue listed alongside your own, settled on measured viewing.
- Content submission with visible approval status
- Title-level performance reporting on their own catalogue only
- Watch-minute logging per title, measured rather than estimated
- Earnings visibility linked directly to what they are owed
- Payout requests routed to operator approval
- Scoped access, so a partner never sees another partner's numbers
Operator
A multi-model service is meaningfully harder to operate than a single-plan one, which is why the console carries as much weight as the viewer app.
- Catalogue management with pricing set per monetization model
- Weekly, monthly and annual plans with catalogue and device limits
- Rental windows configured per title or globally, with scheduled expiry
- Fixed-value or percentage coupons with validity windows and usage caps
- Partner approvals, settlement and operator-gated payout runs
- Territory rights: availability, pricing and model set per region
The mechanism that defines this product is the entitlement engine. A title can be included in one plan tier, rented at one price, sold at another, and made available with ads in territories you choose. The engine resolves which right applies on every play request, in order, so a viewer who holds two of them never sees a conflict - and territory rules are enforced there rather than by hiding a title in the interface.
Storefront vs Generic OTT Script vs Custom Build
What an OTT operator actually compares, judged on entitlement depth and settlement accuracy rather than on player features.
| What an OTT operator compares | Generic OTT script | Miracuves Prime Video Clone | Custom development |
|---|---|---|---|
| Time to launch | Unknown / DIY | 6 days, production-ready | 3-9+ months |
| Entitlement resolution | Basic plan check | Server-side resolution across plans, rentals and purchases | Custom build, often underestimated |
| Rental windows | Rarely supported | Start and finish timers, scheduled expiry | Depends on scope |
| Partner revenue share | Absent | Watch-minute settlement with scoped partner access | Custom build, extra cost |
| Content acquisition API | Manual upload only | Programmatic ingest for catalogue growth | Depends on brief |
| Territory rights | Not modelled | Per-region availability, pricing and model | Varies widely |
| DRM readiness | Public media URLs | Signed media with a documented DRM integration path | Depends on architecture |
| Cost vs speed | Cheap but risky | Balanced and predictable | High cost, slow |
| Ongoing support | Usually none | Defined plans after launch | Contract dependent |
Two things are deliberately not in the base package, and we would rather say so here than after purchase: DRM (Widevine, FairPlay, PlayReady) is a separately scoped integration, and native Smart TV applications for Fire TV, Android TV, Roku and tvOS are custom development. The platform ships Android, iOS and web with QR-based session handoff to television. Pricing lives on the development cost page.
The Technology Behind the Features
A Laravel backend with a REST API layer serving Flutter mobile applications, the web platform, the partner console and the admin platform from one codebase. Media is served through signed URLs with server-side entitlement checks rather than public media paths, which is appropriate for owned and independent catalogue - studio licensing usually mandates a DRM system, and that is an integration we scope separately rather than imply. Rental expiry runs as scheduled work rather than being checked at play time, so access ends predictably and the viewer sees an accurate countdown throughout. Watch minutes are logged per title, which is what makes partner settlement a measurement rather than an estimate.
How It Works, End to End
On a single-plan service the journey is short: subscribe or leave. On a storefront it branches, and every branch is a different way to be paid. Here is the whole path.
Sign in and set up the household
Email, social and OTP sign-in with QR handoff to television. Multiple profiles per household account, each with separate watch history and recommendations, and kids profiles filtered by maturity rating rather than by a setting a child can toggle.
Discover something to watch
Hero banners and merchandised rows, trending, new release and leaving-soon rails, and genre, cast and crew browsing across films, series, seasons, episodes, trailers, extras and priced boxsets, alongside a live channel line-up.
Choose how to pay for it
The same title can sit in a plan tier, be rented at one price, be bought outright at another, or open on an ad-supported tier - and which of those are offered can differ by territory. This is the branch a single-plan service does not have.
The entitlement engine resolves
On every play request the engine decides which right applies, in order, server-side. A viewer holding both a plan entitlement and a rental never sees a conflict, and territory rules are enforced here rather than by hiding a title in the interface.
Watch, and be measured
Adaptive quality, subtitles, multiple audio tracks and 360 VR-ready playback, with watchlist and Continue Watching synced across devices per profile. Viewing is logged in watch minutes at title level, which is what makes partner settlement a measurement rather than an estimate.
Settle with partners and creators of supply
Each partner's share is calculated against their agreed terms from those watch minutes. Statements and payout requests run through the partner console, approval is operator-gated and attributable, and partners see only their own numbers.
Every Feature Earns Its Place
A feature list tells you what exists. This tells you what each one is worth to an OTT operator, and what it costs you not to have it.
| Capability | What it actually does | Why it matters commercially |
|---|---|---|
| Server-side entitlement engine | Resolves plan, rental, purchase and ad rights in order on every play request | One licence earns across four demand curves instead of one, with no additional content spend |
| Rental windows with two timers | A window to start and a shorter one to finish, expiring on schedule | A new release often earns more from one rental than a month of subscription, and predictable expiry avoids the refund queue |
| Outright purchase | Permanent entitlement recorded against the viewer | A buyer pays once and never churns, which is the only revenue on this page immune to cancellation |
| Ad-supported tier | Free access to selected catalogue in territories you choose | Monetizes viewers who were never going to subscribe, so the revenue is additive rather than cannibalised |
| Watch-minute settlement | Viewing logged per title, feeding each partner's calculated share | Partners renew on trust in the numbers as much as on the size of the cheque. An apportionment does not earn that trust |
| Content acquisition API | Programmatic ingest rather than manual upload | Catalogue growth stops being gated on someone's afternoon, which is what lets a partner economy scale |
| Territory rights at the entitlement layer | Availability, price and model set per region and enforced where rights resolve | Licensors treat "hidden in the interface" and "enforced" as materially different, and only one of them survives an audit |
| Signed media URLs | Server-side entitlement checks on every request, not public paths | Public media URLs leak the moment one is shared. This is the floor below which no licensing conversation starts |
| Scoped partner console | Submission, approval status, own-title performance and payout requests | A partner who can see another partner's numbers is a contract problem you only discover once |
What Is Not Included in the Base Package
Two of these matter more than anything else on the page, and both come up in the first serious licensing conversation. We would rather flag them before purchase than after.
- DRMNot included, and this matters if you are licensing premium content. Media is served through signed URLs with server-side entitlement checks, which suits owned and independent catalogue. Studio licensing usually mandates Widevine, FairPlay or PlayReady, and that is a separately scoped integration.
- Native Smart TV applicationsNot in the base package. The platform ships Android, iOS and web with QR-based session handoff to television. Fire TV, Android TV, Roku and tvOS apps are custom development - worth planning for, since most premium viewing happens on a television.
- Dynamic ad insertionAd-supported tiers are modelled and the entitlement engine resolves them. Server-side ad insertion against a live ad decisioning platform is an integration we scope separately.
- Channel bundlingPartner catalogues list alongside your own on a revenue share. Reselling a partner's catalogue as its own priced channel inside your storefront is an extension.
- Seasonal and dynamic pricingPricing per model, per title and per territory is configuration. Rules that change price automatically by date, demand or window are custom work.
- Territory-limited licensing windowsAvailability by region ships. Automatic activation and expiry of a licence window per territory, driven by your contract dates, is scoped separately.
- Custom settlement formulasWatch-minute settlement against agreed terms ships. Minimum guarantees, tiered rates by volume or recoupment against an advance are modelled per deal.
- Catalogue preparationThe acquisition API accepts your content programmatically. Preparing the files, metadata, artwork and territory rights is on your side, and it is almost always the longest task on the project.
See how Miracuves compares to agencies and OTT SaaS
Cost, timeline, source-code ownership and entitlement depth compared - plus the content-protection questions a licensor will ask before they sign.
Frequently Asked Questions
Can one title really carry several prices at once?
How do rental windows work?
How does partner revenue sharing work?
Are there Smart TV apps?
What is an Amazon Prime Video Clone app?
Can a partner see another partner's numbers?
Explore the Amazon Prime Video Clone
See exactly what you are getting - before you commit
Rent a title and watch the timers behave, then sign in as an operator and set the same title to subscription-included in one territory and rental-only in another.
