Skip to main content
CinePro is more than a single API — it’s a small, modular ecosystem of tools that work together. Each piece has a distinct role: a compliant backend, a demo frontend, and an automation layer for home media servers.

CinePro Core

OMSS-compliant TypeScript backend. The engine of the whole ecosystem.

CinePro Frontend (WIP)

Reference React UI built on top of Core. Useful for testing, not production.

CineHome Backend (WIP)

Downloads movies and TV episodes to a folder on your home server or NAS.

CineHome Frontend (WIP)

Next.js UI that sends download requests to the CineHome Backend.

​
CinePro Core

CinePro Core is the heart of the ecosystem. It is a fully OMSS-compliant (Open Media Streaming Standard) streaming backend built in TypeScript using the @omss/framework. Its job is to find and return playable streaming sources for movies and TV shows identified by TMDB IDs.

OMSS-Compliant

Follows the Open Media Streaming Standard specification for a consistent, interoperable API contract.

Modular Provider System

Drop-in provider folders under src/providers/ with auto-discovery. Ships with built-in providers.

Production-Ready

Redis caching, Docker + Docker Compose support, TypeScript strict mode, and full error handling baked in.

Type-Safe

Full TypeScript implementation with strict types end-to-end for reliable provider development.
CinePro Core requires a TMDB API key to resolve metadata. You can get one for free at themoviedb.org/settings/api.
Quick links:

​
CinePro Frontend

The CinePro Frontend is a React + Vite demo application that connects directly to a running Core instance via the VITE_API_URL environment variable. It demonstrates how to consume the Core API in a real browser context.
This frontend is not intended for production or large-scale use. It was built for testing and reference purposes. The README itself notes: “it has only been made for testing purposes.”
It supports:
  • Browsing and watching movies and TV shows
  • Video streaming via HLS.js
  • Responsive design
Think of it as a working proof-of-concept — a starting point for building your own UI on top of Core, not a finished product. Quick links:

​
CineHome

CineHome is a two-part automation stack — a backend service and a Next.js frontend — that lets you automatically download movies and TV episodes to a predefined folder on a running system such as a NAS or home server. It uses CinePro Core to resolve sources and then downloads the media locally.

CineHome Backend

Node.js service that receives download requests and uses the CinePro Core API to resolve and download media to a local folder.

CineHome Frontend

Next.js UI that communicates with the CineHome Backend via NEXT_PUBLIC_CINEHOMEBACKEND. Used to queue and manage downloads.
CineHome is tightly coupled to CinePro Core. Make sure your Core instance is running and reachable before setting up CineHome.
Setup overview:
1

Run CinePro Core

Deploy Core with a valid TMDB_API_KEY. See the Core quickstart for full instructions.
2

Deploy CineHome Backend

Clone cinepro-org/CineHome-backend, configure it to point at your Core instance, and start the service.
3

Deploy CineHome Frontend

Clone cinepro-org/CineHome-frontend, set NEXT_PUBLIC_CINEHOMEBACKEND to your CineHome Backend URL, and run npm run dev or build for production.

​
How the pieces fit together

​
Community & Discussions

CinePro is actively maintained and open to contributors. The best place to get help, propose features, or discuss new providers is the GitHub Discussions board.

GitHub Discussions

Ask questions, share ideas, and connect with contributors.

Contribute to Core

New providers, bug fixes, performance improvements, and docs are all welcome. Open a PR on the core repo.
The most impactful contributions right now are new provider implementations. Check the existing providers under src/providers/ in the core repo for the reference pattern.