Komga — Self-Hosted, Open-Source

Media server for comics/mangas/BDs with API and OPDS support, a modern web interface for exploring your libraries, as well as a web reader.

License: MIT. Built with: Kotlin, Vue, TypeScript, HTML, Go Template, JavaScript, CSS, Sass. Website: https://komga.org. Source: https://github.com/gotson/komga.

Features

Browse libraries, series and books via a responsive web UI that works on desktop, tablets and phones
Organize your library with collections and read lists
Edit metadata for your series and books
Import embedded metadata automatically
Webreader with multiple reading modes
Manage multiple users, with per-library access control, age restrictions, and labels restrictions
Offers a REST API, many community tools and scripts can interact with Komga
OPDS v1 and v2 support
Kobo Sync with your Kobo eReader
KOReader Sync

Installation

See official install docs: https://komga.org/docs/category/installation

Why self-host Komga

Self-hosting gives you three things SaaS can’t: data ownership (the files live on disks you control), cost predictability (a one-time setup vs. recurring per-seat fees that grow with your household or team), and longevity (open-source means the app keeps working even if the maintainers move on, since you can pin a working version). The trade-off is that you take on the operational work of running a server, applying updates, and handling backups.

What hardware do you need

Most self-hosted apps run comfortably on modest hardware — a Raspberry Pi 4, a mini PC, a NAS with Docker support, or a small VPS is usually enough for personal or family use. CPU and RAM requirements scale with how many simultaneous users or how much data you push through Komga. Storage requirements depend on the kind of data you keep; check the README for guidance on data retention.

Where to go from here

Last verified: 2026-05-22