Open-Source DevOps · zoriya

Kyoo

Kyoo is a self-hosted media server for movies, TV shows, and anime that aims to minimize maintenance by automatically handling metadata and file scanning without requiring strict folder structures. It features dynamic transcoding, subtitle support, intro/credit detection, and deploys via Docker or Kubernetes with OIDC authentication.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/zoriya/Kyoo

2.5k

GitHub stars

Forks

TypeScript

Primary language

GPL-3.0

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	zoriya/Kyoo
Owner	zoriya
Primary language	TypeScript
License	GPL-3.0 — OSI-approved
Stars	2.5k
Forks	75
Open issues	65
Latest release	v5.0.0 (2026-04-06)
Last updated	2026-07-06
Source	https://github.com/zoriya/Kyoo

What Kyoo is

Built in TypeScript/React with a multi-container architecture (backend, transcoder, frontend), Kyoo uses FFmpeg for transcoding, supports hardware acceleration, and provides a Swagger API for integration. It emphasizes automatic media detection and low-friction setup compared to Jellyfin or Plex.

Quickstart

Get the Kyoo source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/zoriya/Kyoo.git2cd Kyoo3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Self-hosted streaming for media enthusiasts

Ideal for users wanting a personal streaming service without plugin complexity; works with messy file naming and requires minimal manual metadata curation.

Anime-focused media libraries

Kyoo's anime name parsing handles poorly-named release files automatically, making it well-suited for anime collections that typically have inconsistent naming.

Kubernetes deployments

Official Helm chart support enables straightforward deployment in K8s environments, though multi-replica setups are noted as work-in-progress.

Implementation considerations

Multi-container orchestration required: backend, transcoder, and frontend must be coordinated; single-box Docker Compose is simpler than distributed setups.
FFmpeg transcoding is CPU/GPU-intensive; hardware acceleration (e.g., NVIDIA NVENC, Intel QSV) should be evaluated for your hardware and expected concurrent user load.
Media scanning relies on automatic naming detection; pathologically named files may still fail and warrant bug reports; test with a sample library before full deployment.
OIDC integration available but requires compatible identity provider; local user management or fallback auth method should be clarified during setup.
Watch list sync and offline download features marked 'soon' in v5; confirm roadmap status if these are critical for your use case.

When to avoid it — and what to weigh

Music, ebooks, or games required — Kyoo is narrowly scoped to video content only; if your library needs multi-media support, choose a broader platform like Jellyfin.
iOS/tvOS client support needed — Apple platform clients are explicitly not planned due to hardware and licensing costs; only web and Android (in development for v5+) are supported.
Plugin ecosystem required — Kyoo has no plugin system and builds all features directly; if you need custom extensions or third-party integrations, this will not be extensible.
Commercial redistribution or proprietary derivatives — GPL-3.0 requires source disclosure and derivative works remain GPL-licensed; any commercial use requires legal review and compliance with copyleft obligations.

License & commercial use

GPL-3.0 (GNU General Public License v3.0) – a strong copyleft license requiring all derivative works and modifications to remain open-source and GPL-licensed.

Commercial use of Kyoo for internal operations (e.g., company media streaming) may be permissible under GPL-3.0, but commercial redistribution, embedding in proprietary software, or SaaS offerings require legal review to ensure GPL compliance and source-code disclosure obligations are met. Do not assume commercial use without counsel.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Adequate
License clarity	Clear
Deployment complexity	Moderate
DEV.co fit	Good
Assessment confidence	High

Security considerations

OIDC support enables delegated authentication to trusted providers. Self-hosted deployment means network exposure and media-server security posture depend on firewall, TLS/HTTPS, and identity provider strength. No cryptographic audit or formal security disclosure program mentioned in README. Evaluate container image provenance and keep dependencies (FFmpeg, Node.js) patched. Data in transit and at rest protections require configuration review.

Alternatives to consider

Jellyfin

Open-source (GPL-2.0), broader media support (music, ebooks), larger community, but monolithic architecture and requires structured folder organization; more established but less opinionated about low-maintenance setup.

Plex

Closed-source, commercial SaaS + self-hosted hybrid, strong UX and cross-platform clients (iOS/tvOS), but mandatory metadata curation, plugin system adds complexity, and privacy concerns with cloud relay.

Emby

Closed-source, self-hosted media server with broader codec support and plugin ecosystem, strong client ecosystem, but proprietary licensing and higher operational overhead than Kyoo's simplified design.

Software development agency

Build on Kyoo with DEV.co software developers

Evaluate Kyoo for your streaming infrastructure. Review the installation guide, test with sample media, confirm OIDC/auth needs, and assess multi-container deployment readiness. Contact our team to discuss GPL compliance, Kubernetes integration, or custom DevOps requirements.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

kyuubi Medoo kubero

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source DevOps DevOps & Deployment Cloud Deployment API Development Talk to DEV.co

Kyoo FAQ

Does Kyoo require a specific folder structure or manual metadata tagging?

No. Kyoo automatically detects and parses media using file names and metadata; manual folder hierarchies are not required, making setup simpler than Jellyfin or Plex.

Can I use Kyoo commercially or embed it in a product?

GPL-3.0 permits internal use but requires legal review for commercial distribution or proprietary embedding. Source code must remain open and derivative works must be GPL-licensed. Consult counsel.

What hardware do I need for transcoding?

CPU-based transcoding is supported; hardware acceleration (NVIDIA NVENC, Intel QSV, etc.) is recommended for high-concurrency scenarios. Exact specs depend on video bitrate, resolution, and user count; test with your media sample.

Is iOS/tvOS support planned?

No; the project explicitly states Apple platform support is not planned due to hardware and yearly developer fee costs (~$100). Only web and Android clients are targeted.

Work with a software development agency

DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If Kyoo is part of your open-source devops roadmap, our team can implement, customize, migrate, and maintain it.

Ready to Deploy Kyoo?

Talk to DEV.co Schedule a Consultation