English
Komga Hosting
Serve comics, manga, magazines, and ebooks with metadata, reading progress, and OPDS support.
No setup fees-
One click deploy -
2 GB RAM Memory needed -
25 GB Disk Space Needed -
From 5 € Price
Official links
Komga’s official links and original website
Komga Website
More
Tech
- Docker image
- gotson/komga:latest
- Default port
- 25600
How Komga works
Komga watches configured library folders, scans supported files, and builds a catalogue of series, books, metadata, thumbnails, and reading status. Users browse the web interface, open publications in the web reader, search the catalogue, and continue from their own recorded progress. Collections and reading lists add organisation beyond the folder layout.
OPDS feeds expose authorised libraries to compatible reading applications. The server can analyse files, refresh metadata, and rescan changed folders, but results depend on naming, embedded information, format support, and the selected metadata workflow. Komga does not provide the publications themselves or grant rights to upload, download, or distribute them.
Key Komga features
Administrators create libraries and control which users may access them. Each reader keeps separate progress, while the catalogue can group related books through series, collections, and reading lists. Scans and analysis are more demanding after large uploads or reorganisations; ordinary browsing and direct reading place a lighter load on the service.
The catalogue mounts /config and /data, separating application state from customer library files. OPDS clients, reading devices, metadata providers, and source content are external. Customers must supply legally obtained, compatible, DRM-free files and maintain independent originals because the hosted service is not a licensed bookstore or preservation archive.
Who uses Komga
Comic and manga collectors use Komga to browse a structured personal library from several devices. Families create accounts with separate progress, while clubs and small organisations publish an internal catalogue of materials they are authorised to share with their members.
Komga is not suitable for public distribution without rights, DRM removal, purchasing content, guaranteeing metadata accuracy, or replacing original files. Client and format compatibility should be tested with representative publications before a large archive is transferred.
Self-hosting Komga: requirements and cost
Komga consumption is driven by library size, file scans, metadata refreshes, thumbnails, search indexing, concurrent readers, OPDS traffic, and stored application data. Komga’s one-click stack does not add PostgreSQL or MariaDB. Storage is the practical limit because customer publications and generated catalogue files remain on the mounted volumes. Komga is marked storage-driven in the plan mapping, so 50 GB on Plan 3 is a realistic starting point and 100 GB on Plan 4 provides more room for a large working set.
On AvaHost, Komga uses Plan 2 at €5. The hosted Komga package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. Customers provide authorised, compatible, DRM-free publications and any external OPDS readers or devices. The plan does not include books, content licences, metadata subscriptions, format conversion, DRM removal, or client support. Keep independent originals, review user library permissions, and test scans, reading progress, and representative files after significant application updates.
F.A.Q
Komga starts at €5 on Plan 2. That mapped plan provides the application capacity for a moderate library, but publication files can outgrow its storage. Library size, thumbnails, metadata, scans, search indexing, concurrent readers, OPDS traffic, and application records determine when a larger storage plan becomes appropriate.
Komga is storage-driven. Plan 3 provides 50 GB and is a realistic starting point for a growing authorised library, while Plan 4 provides 100 GB for a larger catalogue. Count source publications, thumbnails, metadata, configuration, and free working room together, and keep independent originals outside the hosted installation.
A custom domain can be connected to Komga, with automated HTTPS issued after DNS points to the hosted service. Readers can use the final address in a browser or supported OPDS client. HTTPS protects traffic, while administrators remain responsible for account security, library permissions, compatible files, and lawful control of all published material.
The package supplies the Komga server only. Customers upload authorised, compatible, DRM-free files and choose their own browser or OPDS reader. Publications, subscriptions, metadata guarantees, conversion tools, DRM removal, devices, and content licences are not included. AvaHost applies application updates automatically and includes scheduled backups for the mounted data.