# Kineflix

> Kineflix is a responsive, single-owner OTT/SVOD web service with full source code to customize and run as your own branded SaaS.

Source page: https://saascode.ai/products/kineflix
Machine-readable record: https://saascode.ai/products/kineflix.md

One-time purchase · full source code · self-hosted by the buyer.

Price: $299 (one-time)

## How to read this document

Written for a model auditing this product on a buyer's behalf. Two labels
appear throughout and they mean different things:

- **measured** — produced by a script reading the product's own source tree
  or database at the stated date. The method is named beside each number.
- **stated** — written by the seller. True or not, it is a claim, and this
  document does not ask you to treat it as evidence.

The live demo is the strongest verification available from outside: it runs
the same source a buyer receives. Nothing to sign up for — the public side is
open, and the seeded credentials below get you into each role.

## What it is

This product publishes two kinds of thing, and keeps them distinct on purpose: standalone titles (a film, a documentary, a special) and series, which contain seasons, which contain episodes. A series is never a folder of loose videos, and an episode is never a title in disguise. Everything else in the product — availability, offers, playback, analytics — hangs off that structure.

## Live demo

Two doors into the same running instance, and the same source a buyer
receives. There is no account to create; the public side is open, and the
seeded credentials below sign you into each role.

- **Guided (recommended):** https://saascode.ai/demo/kineflix — our shell, with a role switcher and
  the credentials in the menu. Best for a person.
- **Direct:** https://kineflix.saascode.ai — the product on its own, no chrome.
  Best when you are relaying steps to someone, or fetching a page.

3 seeded roles. Credentials are published deliberately: these
are demo accounts on a public demo instance, and a reviewer who cannot get
in cannot verify anything.

- **Subscriber** (`member`) — `user@demo.com` / `demo123`
  Browses the library, manages profiles and watches titles.
- **Operations staff** (`admin`) — `staff@demo.com` / `demo123`
  Runs catalog, media, subscribers and recovery work.
- **Service owner** (`super_admin`) — `admin@demo.com` / `demo123`
  Controls providers, rights, plans and instance settings.

Or open a role directly: https://saascode.ai/demo/kineflix?role={role}

## Measured build

*measured — each number names the method that produced it.*

- **roles: 3** — distinct roles accepted by the role CHECK constraint: admin, member, super_admin
- **tables: 89** — distinct CREATE TABLE statements across every applied migration
- **migrations: 118** — .sql files in supabase/migrations
- **page modules: 94** — files named page.tsx under src/app, excluding node_modules and .next
- **source lines: 178,464** — lines of code (comments and blank lines excluded) across 1085 TypeScript files (156,480) and 148 SQL files (21,984); node_modules and .next excluded
- **api route files: 237** — files named route.ts under src/app/api
- **http operations: 316** — exported HTTP method handlers across those files, de-duplicated per file, OPTIONS excluded as CORS preflight
- **schema graph: 89 tables, 147 relationships** — parsed from the applied migrations

A large number here is scope, not quality. It says the product models a
real domain rather than a CRUD skeleton; it says nothing about code
quality, duplication, test coverage or maintainability, and should not be
read as if it did.

Release: v1.0.0 · built 2026-08-27

## Complete capability inventory

17 capabilities. Each summary is *stated* — selected from the
product's own buyer documentation, or written by the seller where marked.

### Catalog, series and publishing

- **Hierarchical catalog** *(seller-authored)* — Publish standalone titles and episodic series without flattening seasons and episodes into loose videos. The hierarchy carries editorial metadata, publication state, availability, offers, playback and analytics, so each downstream decision addresses the intended catalog item.
- **Curated discovery (Search across titles and synopses)** *(seller-authored)* — Search across titles and synopses

### Viewer accounts, profiles and child safety

- **Account profiles** — An account can hold up to five profiles. The maximum actually enabled is a plan setting, so you can offer fewer on a cheaper plan and more on a larger one, up to five. Lowering the limit never deletes anyone's data — existing profiles remain, and the account simply cannot add more until it is under the new limit.
- **Child profile policy** — 1. Titles above the ceiling are not merely hidden from the rows. They are unavailable. A direct link, a search result or a shared address all refuse the same way. 2. The refusal happens on the server at the moment of playback, not only when the page is drawn. There is no arrangement of clicks that gets around it.
- **Profile continuity** *(seller-authored)* — Keep history, watchlist, ratings, continue-watching state and playback preferences isolated to the active profile. People sharing one account can return across sessions to their own place without inheriting another profile's activity or settings.

### Availability rules, streams and protected playback

- **Signed playback** *(seller-authored)* — Serve each viewing session through a short-lived grant tied to the current stream slot rather than exposing a reusable media link. The grant expires with the session and cannot outlive the viewer's entitlement, so saved or forwarded links do not become permanent access.
- **DRM-required playback** *(seller-authored)* — Keep protection-required titles closed until a verified protection provider is configured. Publishing and playback refuse explicitly instead of falling back to an unprotected stream, preserving the protection boundary when a provider is missing or unhealthy.
- **Availability/rights** — When the answer is no, it comes back with a stable reason, not a shrug. Reasons are things like "outside the licensing window", "not available in this country", "no current entitlement", "above this profile's maturity limit" or "all streams in use". You can see the reason a viewer was denied, which is the difference between supporting someone in a minute and guessing for an hour.
- **Concurrent streams** — Concurrent streams are a real capacity limit, not a warning. When playback starts, the account acquires a stream lease — an exclusive slot, taken atomically, so two devices starting at the same instant cannot both win a single remaining slot. The player renews the lease with a heartbeat while watching, and releases it when playback stops. If a device disappears without releasing, the lease expires on its own and the slot returns.
- **Device registry** — Each account has a device list. Viewers can see their devices and sign a device out themselves; you can deactivate one from the back office. Device registration is one of the inputs to the availability decision, so removing a device takes effect on the next playback attempt rather than at some later sync.

### Plans, purchases, rentals and gift codes

- **SVOD plans** — You define the plans. Name, description, currency, monthly or annual cycle, price, trial period and every capacity limit are yours to edit, and a change takes effect from the plan editor without any redeployment.
- **Purchase and rental** — Offers have their own active, paused and scheduled states, so you can retire a price without losing its history. The price a viewer is charged is always read on the server from the offer; it is never taken from what the browser sent.

### Running this product day to day

- **Owner control plane** *(seller-authored)* — Run the service from one owner back office spanning catalog, media, offers, subscribers, analytics and operational recovery. Full owners retain destructive settings and provider configuration, while staff handle day-to-day work without reaching those instance-level controls.
- **Media ingest/processing** — Uploaded material moves through queued, processing, ready and failed states. The queue is where you watch that happen, retry what failed, replace a version and reconcile with the provider.
- **Audience analytics (Track playback starts, completions, unique accounts, active subscriptions and paid revenue)** *(seller-authored)* — Track playback starts, completions, unique accounts, active subscriptions and paid revenue

### What is configured, what is unavailable, and why

- **Jurisdiction profiles** — A jurisdiction profile is the versioned record of the rules you operate under: territory rights, tax treatment, cancellation and refund handling, accessibility and caption duties, and data and consent limits. A new installation ships a conservative default in draft.
- **Responsive web VOD boundary** *(seller-authored)* — Operate a responsive web video service across public discovery, subscriber viewing and owner administration. The product stays within its web VOD scope rather than presenting native apps, live television or an upload marketplace as finished surfaces.

## What each system gives the operator

*stated.*

- **Catalog and publishing** — Publish a coherent film-and-series library without losing editorial control.
- **Profiles and households** — Give each household a private, age-aware viewing experience.
- **Rights and playback** — Offer every viewer only the titles and playback rights they can use.
- **Plans and title rights** — Turn subscriptions and title-level rights into revenue you control.
- **Owner operations** — Keep media, subscribers and revenue recoverable from one operating desk.
- **Operational readiness** — Know which outside capability is ready before it reaches viewers.

## The problems it was built to solve

*stated — the seller's argument, given in full so you can judge it.*

### Every title reaches the right audience without editorial guesswork.

A streaming catalog becomes expensive when the team cannot tell which version of a title is actually ready, where it may appear, or whether the home page and player agree. Scheduled releases turn into calendar reminders, retired work keeps resurfacing, and a series loses its order across separate spreadsheets. The audience notices the inconsistency before the owner does: a promised title is missing, a draft appears early, or the next episode is wrong. Each mistake weakens trust in the library and creates support work that should never have existed.

### Protected playback stays dependable when demand and rights collide.

Video businesses lose confidence quickly when access behaves differently from one screen to the next. A viewer sees a title but cannot explain why it will not start; another household consumes more simultaneous capacity than it bought; a link remains useful long after it should have expired. Support teams then arbitrate access by guesswork while rights owners see a service that cannot demonstrate control. The cost is larger than one failed play: refunds rise, support time expands, and every future licensing conversation begins with doubt about whether the service can enforce the promises it makes.

### Every household gets personal viewing without crossing profile boundaries.

A shared subscription stops feeling personal when one person's choices rewrite another person's experience. Recommendations drift, progress jumps ahead, watchlists become communal scratchpads, and children encounter titles meant for adults. The account still appears to work, but the household gradually loses the reason to keep using separate profiles at all. That failure is especially costly for a family service: the product asks people to trust one login across several viewers, then makes each viewer clean up after the others. Personal continuity and age-appropriate boundaries are what make the shared account feel intentionally shared rather than merely reused.

### Recurring revenue and title sales coexist in one catalog.

A fixed subscription is a poor fit for every piece of a video catalog. Some audiences want continuing access, while others will pay for one premiere, a rental window, or a lasting right to a particular title. Forcing every release into one commercial shape leaves money on the table and makes exceptional programming difficult to price. Splitting those models across separate systems creates a different problem: customers receive conflicting access, finance reconciles incompatible records, and the catalog team cannot see what each title is actually selling. A coherent revenue model needs room for both recurring relationships and title-specific demand.

## What it takes to run it

*stated — external services the buyer supplies and pays for directly.*

- **Node host** (required) — A Node host for Next 16.2.10 and React 19.2.3.
- **Supabase** (required) — A Supabase project; the Supabase client is present in this build.
- **Scheduled runner** (required) — Four jobs are declared in `vercel.json`; another host needs an equivalent runner configured by hand.
- **Email sender** (optional) — Choose one shipped provider: Brevo, Mailgun, Resend, SendGrid or SMTP. In-app notifications continue without email.
- **Upstash** (optional) — Optional service hooks are declared for Upstash and may remain unset when unused.
- **Sentry** (optional) — Optional Sentry settings, including browser-facing configuration, may remain unset when unused.

## FAQ

**What exactly do I receive after purchase?**

The complete source repository behind the live demo — 178,464 lines across the application and its database, 89 tables defined by 118 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.

**Is the live demo the same product whose source I receive?**

Yes. The Kineflix demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately.

**Can I test every account role before buying?**

Yes — all 3 of them: Subscriber, Operations staff, Service owner. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.

**Is this a complete product or a starter template?**

Complete. 94 page modules and 316 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.

**Can I rebrand and modify it?**

Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.

**What does the licence allow?**

A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.

**Can I resell the source code?**

No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.

**What services and ongoing costs are required?**

You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: Node host, Supabase, Scheduled runner. Optional: Email sender, Upstash, Sentry. The table above says exactly what stops working without each one; most have usable free tiers at low volume.

**How difficult is deployment?**

Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 118 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.

**What updates and support are included?**

Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.

**Why does a complete codebase cost $299?**

Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.

**Do I need to be a developer?**

No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.

## Licence

The buyer receives the complete source and may deploy, modify and operate it
as their own SaaS, charging their own customers. The source itself is not
resold or redistributed: you build and deliver **with** it, you do not sell **it**.

## What this document cannot tell you

Stated plainly because a review that misses it is not a review:

- code quality, duplication, or architectural consistency
- test coverage
- query performance under load
- security posture beyond what the stack implies
- how maintainable it will be in a year

Scope is measurable from outside; implementation quality is not. Anyone
evaluating this should say so rather than infer quality from size.

## Written about it

- [OTT platform options in 2026: who holds the viewing rights?](https://saascode.ai/inside/ott-platform-options-viewing-rights-2026.md)
- [Kineflix: a single-owner OTT/SVOD service for subscriptions, purchases and rentals](https://saascode.ai/inside/kineflix-single-owner-ott-svod-service.md)
- [Kineflix vs Uscreen: own the OTT source or rent the managed service?](https://saascode.ai/inside/kineflix-vs-uscreen.md)

## Links

- Catalog page: https://saascode.ai/products/kineflix
- Product record: https://saascode.ai/inside/products/kineflix
- Live demo: https://kineflix.saascode.ai
- Every product: https://saascode.ai/llms.txt