Skip to main content
Streamly is a white-label OTT / streaming SaaS platform that lets you launch a branded movie, TV, and Live TV experience under your platform host (and {slug} subdomains) — with an operator console, subscriptions, and storefront themes. Instead of building catalog, playback admission, billing, branding, and tenant routing from scratch, you deploy Streamly once, connect Supabase, apply a theme, and start filling your catalog. Built on Next.js, Supabase, PostgreSQL, and TypeScript, with an optional Cloudflare Workers path via OpenNext. Production reference host: streamly.watch.
Streamly theme storefront preview with centered Streamly logo and hero.

Streamly theme storefront — branded logo in the header.

Streamly admin overview dashboard.

Streamly Admin Overview — operator control center.

Streamly does not provide copyrighted media. You supply licensed catalog sources, your own uploads, or demo streams for evaluation.

Why Streamly Exists

Launching a streaming product requires more than a player:
  • Operator vs viewer auth and host-based tenant resolution (platform host / {slug} subdomains)
  • Catalog (movies, TV seasons/episodes, genres, collections, homepage sections)
  • Playback sessions, plans, and billing webhooks
  • White-label Brand & Experience (colors, logos, fonts, SEO, legal pages)
  • Storefront themes that change look without forking routes
  • Live TV, ads, and streaming source addons
  • Deploy to Node or Cloudflare Workers without rewriting the app
Streamly ships that stack as one Next.js application.

One App, Three Surfaces

Admin and dashboard on tenant hosts redirect to the platform host (NEXT_PUBLIC_PLATFORM_HOST).

Who Streamly Is Built For

Core Features

Operator Admin

Viewer Storefront

Tech Stack

Start here (CodeCanyon buyers)

  1. Extract the ZIP and open README-FIRST.txt
  2. Follow Installation (from the ZIP)
  3. Use First Launch Checklist before go-live

What You’ll Have After Setup

  1. Supabase project with migrations applied
  2. Environment secrets configured (local or Worker)
  3. Operator login at /admin/login
  4. An applied storefront theme and Brand & Experience look
  5. At least one catalog title viewers can browse
Next: Quick Start or Platform Architecture.