Skip to main content
CinePro is currently in active development and considered in an alpha stage.
Breaking changes, incomplete features, and rapid iteration are expected.

Where the project stands

CinePro originally shipped as a Node.js backend in the cinepro-org/backend repository, which is now archived and no longer the main development target.
The current focus is CinePro Core, a TypeScript, OMSS‑compliant backend in cinepro-org/core that powers the rest of the ecosystem.
CinePro aims to be a modular, high‑performance movie and TV scraper that does not host any media itself and is intended for personal and home use only.
The project is maintained by a small team and relies heavily on community contributions for providers, bug fixes, and documentation improvements.

Legacy backend

JavaScript backend at cinepro-org/backend is archived and kept for historical reference only.

Current focus

TypeScript / OMSS‑compliant cinepro-org/core is the active backend and the foundation for all new work.
Production or commercial deployments are not supported. CinePro Core and the example frontend are intended for experimentation, learning, and home‑lab usage.

Current focus areas

1. TypeScript & OMSS compliance

The primary engineering effort is on the TypeScript rewrite (cinepro-org/core) using the @omss/framework to fully implement the Open Media Streaming Standard.
This includes enforcing strong typing across providers, aligning endpoints with the shared OMSS OpenAPI spec, and keeping CinePro in sync with upstream OMSS changes.
Read the benefits of OMSS HERE!

2. Provider coverage & quality

CinePro Core ships with multiple providers under src/providers (for example vidsrc, 02moviedownloader, fmovies4u, uembed, vidrock, and others), but coverage and stability are still evolving.
Improving provider reliability, adding new sites, and hardening scraping logic against layout changes are ongoing tasks.

Stabilize existing providers

Fix edge cases, improve error handling, and ensure providers degrade gracefully when a source goes offline.

Add new providers

Expand the set of supported sources to increase availability and redundancy for movies and TV shows.

Document provider interface

Publish clear guidelines for implementing OMSS‑compatible providers so contributors can add new ones safely and consistently.

Performance goals

  • Efficient reuse of results via Redis or in‑memory caching for repeated lookups.
  • Configurable timeouts and retries when fetching from third‑party providers.
  • Better logging and error messages to help users and contributors diagnose issues quickly.

3. CineHome integration

Beyond the streaming backend and demo frontend, CinePro is part of a wider ecosystem that includes CineHome, a service for automating downloads to a NAS or similar device.
CineHome uses CinePro Core as a source of streaming links and metadata, then handles the download and storage workflow via dedicated backend and frontend projects.

CineHome backend

cinepro-org/CineHome-backend coordinates downloads using CinePro Core as the discovery engine.

CineHome frontend

cinepro-org/CineHome-frontend provides a UI to manage and monitor automated downloads.
The roadmap here is to tighten the contract between CinePro Core and CineHome so that updates to providers and OMSS endpoints automatically benefit automation workflows.
Future work includes documenting recommended setups (Core + CineHome + storage), shared configuration patterns, and version compatibility guarantees between these projects.

How you can help

If you want to influence the roadmap or help move CinePro out of alpha, contributions are very welcome.
You can join discussions via GitHub Discussions or the contributor chat and start with issues labelled around providers, performance, or documentation.