Kineflix
Kineflix is a responsive, single-owner OTT/SVOD web service with full source code to customize and run as your own branded SaaS.
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.
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.
- Hierarchical catalog
- Curated discovery (Search across titles and synopses)
- Availability/rights
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.
- Signed playback
- DRM-required playback
- Concurrent streams
- Device registry
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.
- Account profiles
- Child profile policy
- Profile continuity
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.
- SVOD plans
- Purchase and rental
After signing in, a viewer picks a profile. That choice scopes the session: from then on, watch history, watchlist, ratings, continue-watching and playback preferences (autoplay, preferred audio and caption language) all belong to that profile alone. Nothing leaks between profiles on the same account.
One profile can be marked as a child profile and given a maturity ceiling — the highest rating it is allowed to reach. The ceiling is applied by the same decision that governs the whole catalog, which means two things worth being precise about:
A profile can also carry a PIN, which is asked for before that profile is entered or edited.
A single versioned decision weighs all of the following together:
The stream limit is a plan setting you control, per plan.
The plan limits that matter to a viewer are:
The prices and limits that ship with a new installation are starting suggestions, not product rules. They exist so the pricing page is usable on day one. Reprice, rename or restructure them freely.
A principle worth keeping when you do: plans should differ by capacity, breadth and convenience — never by removing the ability to watch. A plan that cannot stream is not a cheaper plan, it is a broken one.
Individual titles can carry offers:
Two behaviours matter when something goes wrong:
If new media fails to process, the previously good version is preserved. What is never allowed is preserving availability by weakening protection.
The platform underneath the product — counted in this product's own source, not claimed from a template. Where a row carries a list, open it to read the names behind the number.
Coinbase
dLocal
Flutterwave
Komoju
Mollie
NOWPayments
Opn
Paystack
ActiveCampaign
Customer.io
Segment
Canny
Amplitude
Custom Head Scripts
Pushover
Twilio SMS
Crisp
Tawk.to
Monday.com
fal.ai
Axiom
hCaptcha
Freshsales
Pipedrive
Pabbly Connect
AWS S3
MuxHover a table to isolate what it touches; click one to read its relationships. The big nodes are what everything else hangs off. organizations is referenced by 41 tables because every single record in this product belongs to an organization, and that is what makes tenant isolation a property of the database rather than something the application has to remember on every query.
all 89 tables, as text
active_boosts · admin_notifications · analytics_daily · analytics_events · analytics_funnels · announcement_dismissals · announcements · api_key_logs · api_keys · asset_rights_evidence · assistant_actions · assistant_conversations · assistant_messages · assistant_usage · audit_logs · automation_log · automation_templates · availability_rules · collection_items · collections · commerce_orders · content_offers · credit_balances · credit_transactions · credits · currencies · data_exports · data_imports · entitlements · episodes · faq_categories · faq_items · feature_flags · genres · gift_codes · inbound_webhook_events · inbound_webhooks · jurisdiction_profiles · languages · marketing_audience_members · marketing_audiences · media_assets · media_tracks · media_versions · notification_log · notification_rules · notifications · order_items · organization_limit_overrides · organizations · plan_prices · plans · platform_secrets · platform_settings · playback_daily_rollups · playback_decisions · playback_events · playback_grants · playback_leases · product_purchases · products · profile_sessions · provider_event_inbox · provider_prices · push_devices · registered_devices · report_templates · roles · scheduled_tasks · seasons · seo_meta · subscriptions · theme_page_sections · theme_section_library · theme_sections · title_credits · title_genres · title_ratings · titles · translations · user_sessions · users · viewer_accounts · viewer_profiles · viewer_subscriptions · watch_progress · watchlist_items · webhook_logs · webhooks
The chassis, and anything particular to this product. 3 required, 3 optional.
A Node host for Next 16.2.10 and React 19.2.3.
A Supabase project; the Supabase client is present in this build.
Four jobs are declared in `vercel.json`; another host needs an equivalent runner configured by hand.
Choose one shipped provider: Brevo, Mailgun, Resend, SendGrid or SMTP. In-app notifications continue without email.
Optional service hooks are declared for Upstash and may remain unset when unused.
Optional Sentry settings, including browser-facing configuration, may remain unset when unused.
Already built — plug and play
Every provider integration in this list ships wired into the product. You bring your own keys, connect them in the admin, and go live — there is no integration code to write. Nothing is resold through us: the ongoing cost is whatever these providers charge you. Capabilities marked plan-gated elsewhere on this page unlock by plan, not by extra code.
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.