Open-source ebook library management, honestly reviewed. No marketing fluff, just what you get when you decide to own your reading collection.

TL;DR

What it is: A Docker-based ebook library server that merges Calibre-Web’s clean UI with Calibre’s conversion and metadata engine — plus automation layers that neither project ships on their own [README].
Who it’s for: Readers who want their ebook collection on their own server, accessible from any device, with automatic ingestion and format conversion, without running two services in parallel [README].
Cost to run: Free software (GPL-3.0) on a $5–10/mo VPS. No per-book fees, no vendor lock-in, no DRM gating [README][1].
Key strength: Genuinely solves the “Calibre vs Calibre-Web” split — you used to need both running simultaneously to get a decent self-hosted library. CWA unifies them into one container [README].
Key weakness: It’s a community project driven by one maintainer (crocodilestick), and the third-party review ecosystem is thin. You’re betting on a passionate hobbyist, not a funded company. The project has 5,162 GitHub stars and 379 forks, which is healthy for the niche but not the scale of a Nextcloud or Immich [README].

What is Calibre Web Automated

To understand why CWA exists, you need to understand the two projects it’s built on.

Calibre is the original desktop ebook manager — powerful, battle-tested, hideous UI, and genuinely problematic when containerized. The main issue is its dependency on a KasmVNC server for the desktop GUI, which is slow, resource-heavy, and essentially unusable on mobile. If you’ve tried running Calibre on a headless server and accessing it from your phone, you know the pain [README].

Calibre-Web solved that problem by building a clean, modern web UI that reads Calibre’s library format. It’s lightweight, mobile-friendly, and genuinely pleasant to use. But it dropped most of Calibre’s actual library management — no format conversion, limited metadata editing, no automated book ingestion. The result was that anyone who wanted the full experience ran both: Calibre on the server to manage the library, Calibre-Web to browse and read. Two containers, two maintenance burdens, one clunky workflow [README].

Calibre Web Automated is the project that collapses that setup into one. It ships Calibre-Web’s UI with Calibre’s engine underneath it, adds an automated ingest folder (drop a file, it gets processed and added), handles format conversion, and layers in a set of quality-of-life features that neither upstream project has: OAuth 2.0/OIDC single sign-on, KOReader reading progress sync, and a companion mobile app [README].

The project is now at 5,162 GitHub stars (1,548 commits), fully GPL-3.0, and funded entirely by Ko-fi donations. The maintainer is explicit that it will always be free and open source [README].

Why people choose it

There are no dedicated review sites doing deep CWA comparisons — the project is niche enough that third-party coverage is sparse. What exists is mostly self-hosting community content that treats Calibre-Web (stock) as the point of reference, which is useful context.

XDA Developers’ Ayush Pande covers Calibre-Web in a roundup of self-hosted entertainment services and calls it “hands-down my favorite self-hosted utility for organizing my ebook collection” — noting OPDS feed support, multi-format compatibility, and the customizable shelf system [1]. That review is about stock Calibre-Web, not CWA specifically. CWA’s pitch is: everything that review praises, plus the automation that makes it actually manageable at scale.

The self-hosting community’s general case for running your own library server is consistent across sources: you own the files, the files don’t disappear, and no vendor can remove access [3]. Tim Kicker’s self-hosting overview frames it bluntly: streaming services mean you’re renting, not owning, and entire platforms — music, video, books — can and do shut down [3]. The Kindle ecosystem is a real-world example: Amazon has remotely deleted purchased books from user devices. A self-hosted Calibre library can’t do that by definition.

For the managed-hosting crowd, ElfHosted offers Calibre-Web (with CWA’s Ko-fi listed as a contribution option) as a hosted service — which is telling. It means there’s a market of people who want the CWA experience but don’t want to touch a Linux server [2].

The choice of CWA over stock Calibre-Web specifically comes down to two features:

Automated ingestion. Drop an ebook file into a watched folder; CWA picks it up, converts it if needed, fetches metadata, and adds it to your library without any manual steps. Stock Calibre-Web requires you to manually upload or use the Calibre desktop app as a middle step.
No parallel Calibre dependency. CWA bundles the Calibre binaries it needs. You don’t run a separate Calibre container. This halves your container maintenance and eliminates the sync issues between the two services.

Features

Based on the README and project documentation:

Core library management:

Calibre-Web’s full web UI — browse, read, download, search [README]
Automatic ingest folder: drop files in, library updates automatically [README]
Format conversion using Calibre’s engine (EPUB, MOBI, AZW3, PDF, and more) [README]
Metadata fetching and editing [README]
OPDS catalog feed for compatibility with external reader apps [1]
Customizable shelves for organizing your collection [1]
Full support for ebooks, audiobooks, and comics [1]

Authentication and access:

OAuth 2.0 + OIDC single sign-on — integrate with your existing SSO provider [README]
Standard username/password as fallback [README]

Device sync:

KOReader sync via the KOSync plugin — reading position syncs across devices that run KOReader [README]
Kobo device sync support [README]

Mobile:

Calibre Web Companion — a Flutter/Material You companion app, unofficial but recommended by the project, available on Google Play and F-Droid [README]
Lets you browse and download books directly to your device, filling the gap in mobile UX [README]

Deployment:

Docker and Docker Compose (the recommended path) [README]
Kubernetes manifests in the repo for k8s users [README]
SQLite database — no external database dependency [README]

Affiliated tooling:

Shelfmark: a separate web UI for searching and requesting book downloads, designed to integrate with CWA [README]. Note: CWA is explicit that it doesn’t support or endorse piracy of copyrighted material.

On the roadmap (active development per README): features are actively being added; the project shows 1,548 commits and regular releases.

Pricing: self-hosted math

CWA has no SaaS tier. It’s GPL-3.0 software — free to run, forever.

The relevant cost comparison is infrastructure, not licensing:

Self-hosted on a VPS:

Software: $0
Hetzner CX22 (2 vCPU, 4GB RAM, 40GB disk): ~~€4/mo (~~$4.50/mo)
Storage for a large ebook library: budget an extra $1–3/mo for a volume or use a NAS you already run
Total: ~$5–8/mo

Managed hosting (ElfHosted):

ElfHosted offers hosted Calibre-Web as part of their platform [2]. Their “Ultimate Stream” package runs ~$39/mo — that covers far more than just a book server, but it’s the reference point if you want zero Linux maintenance [2].

vs. the Kindle ecosystem:

Kindle Unlimited: $9.99/mo for unlimited reading, but you own nothing. Cancel the subscription, the books are gone.
Buying Kindle ebooks: $5–15 per book, locked to Amazon’s ecosystem, subject to remote deletion and DRM.
One-time ebook purchases (DRM-free from Humble Bundle, Smashwords, direct author stores): this is the right comparison. A self-hosted CWA server manages files you actually own, in open formats, accessible forever.

There’s no dramatic monthly savings calculation here the way there is for replacing Zapier or a $200/mo analytics SaaS. The value proposition is different: it’s sovereignty over your library, not just cost reduction. Your books stay your books, even if Amazon changes its policies, raises prices, or disappears.

Deployment reality check

CWA’s README makes the Docker Compose path straightforward. It ships a docker-compose.yml and the default credentials (admin / admin123) are documented clearly [README][2]. The project also ships Kubernetes manifests for users running k8s.

What you actually need:

A Linux VPS with 2GB RAM minimum (4GB comfortable if you’re running format conversions)
Docker and docker-compose
A volume mounted for your book library (CWA reads an existing Calibre library or initializes a new one)
Optionally: a domain and reverse proxy (Caddy or nginx) for HTTPS
Optionally: an OAuth provider if you want SSO instead of local accounts

What can go sideways:

The main friction point for new users is the watched folder configuration. You need to understand how CWA’s ingest paths map to Docker volume mounts — getting this wrong means books you drop in don’t appear in the library. The README covers it, but it requires reading carefully.

Network shares (NFS/SMB) are flagged explicitly in the README with a warning section: ”🚨 Deploying on Network Shares (NFS/SMB) 🚨” — this is a known pain point if your book library lives on a NAS mounted over the network. Inotify file watchers don’t reliably fire over NFS, which can break the auto-ingest feature.

KOReader sync requires the KOSync plugin configured in your KOReader device separately — CWA provides the server endpoint, you configure the client [README].

The companion mobile app (Calibre Web Companion) is unofficial and third-party. It’s not shipped or maintained by the CWA project, so feature gaps or bugs there are out of CWA’s hands [README].

Realistic time estimates:

Technical user with Docker experience: 30–45 minutes to a working instance
Non-technical user following a guide: 2–3 hours including domain and HTTPS setup
Migrating from existing Calibre-Web: the README has a dedicated migration section — budget an extra hour for library reconciliation

Pros and cons

Pros

Solves the Calibre/Calibre-Web split. The core problem this project addresses is real and well-executed. One container, one library, no sync issues [README].
Automated ingestion actually works. Drop a file, it appears in your library with metadata. This is the killer feature for anyone building a library from downloads or rips [README].
GPL-3.0, genuinely free. No commercial tier, no hosted upsell, no “community vs. enterprise” gating [README].
OAuth 2.0/OIDC out of the box. Most comparable tools don’t ship SSO without significant configuration work. CWA treats it as a first-class feature [README].
KOReader sync. If you read on a Kobo or Android device running KOReader — which is the enthusiast standard for open ereaders — reading position sync across devices just works [README].
Companion mobile app. The Calibre Web Companion app (Google Play, F-Droid) fills the mobile UX gap with a modern Flutter interface [README].
OPDS support. Your library is accessible from any OPDS-compatible reader app — Kybook, Moon+ Reader, Marvin, etc. [1]
Active development. 1,548 commits, regular releases, an active GitHub community [README].

Cons

Single-maintainer project. This is the honest risk. CWA is built and maintained by crocodilestick. The project is healthy now, but there’s no company behind it, no funded team, no SLA. If the maintainer burns out or moves on, the project stalls [README].
NFS/SMB deployment is flaky. If your library lives on a NAS, the file-watch-based auto-ingest may not reliably fire. The project flags this prominently [README].
No dedicated third-party review coverage. Unlike n8n or Nextcloud, CWA hasn’t been picked up by major self-hosting review publications. Finding real-world user experiences beyond GitHub issues requires digging through Reddit threads.
Mobile experience requires a separate app. The web UI is not great on phones. The companion app is the answer, but it’s unofficial and adds a dependency [README].
GPL-3.0 copyleft license. If you’re building a product on top of CWA, the GPL requires you to open-source your modifications. MIT this is not. For personal use this is irrelevant; for commercial embedding it matters.
Shelfmark integration ambiguity. The affiliated Shelfmark downloader is a separate project. CWA explicitly distances itself from copyright infringement — but the obvious use case for Shelfmark involves navigating legal grey areas around book acquisition [README].

Who should use this / who shouldn’t

Use Calibre Web Automated if:

You have an ebook collection (bought DRM-free, ripped from physical books you own, or accumulated from Humble Bundle and similar) and you want it accessible from any device, organized, with format conversion.
You previously ran Calibre + Calibre-Web in parallel and want to collapse that to one container.
You read on a KOReader device and want cross-device progress sync.
You want SSO integration with your existing self-hosted identity provider.
You’re comfortable with Docker Compose and basic VPS administration.

Skip it if:

Your entire reading life runs through Kindle and you have no desire to move away from Amazon’s ecosystem. CWA can’t import your DRM-locked Kindle purchases without DRM removal, which is legally and technically its own project.
You want a managed, hands-off solution. Consider ElfHosted or a similar managed platform instead [2].
Your library lives on an NFS or SMB mount and you don’t want to deal with the file-watcher gotchas.
You need a supported, funded project with a roadmap and SLA. CWA is a passion project — which means it’s excellent, but the support model is community forums and GitHub issues.

Consider stock Calibre-Web instead if:

You don’t need automated ingestion and are fine with manual uploads.
You want the absolute simplest setup with the lowest maintenance surface.

Alternatives worth considering

Calibre-Web (stock) — the upstream project CWA is built on. Simpler, less featured, no automated ingestion. Right for minimal setups.
Kavita — a newer, actively developed book server with a clean UI and good manga/comics support. Worth comparing if your collection is heavy on comics or manga.
Komga — similar to Kavita, focused on comics and manga specifically. Better for that use case than CWA.
Audiobookshelf — if your library is primarily audiobooks and podcasts rather than ebooks, Audiobookshelf is the better choice. It also handles ebooks but its strengths are audio [1].
COPS (Calibre OPDS PHP Server) — minimal, just serves an OPDS catalog. No frills. Right if all you want is feed access from a reader app.
Readarr — book acquisition automation, part of the *arr stack. Often runs alongside CWA rather than replacing it: Readarr handles finding and downloading, CWA handles the library.
Ubooquity — Java-based, older, less actively maintained. Skip it unless you have a specific reason.

For most people building a self-hosted reading setup, the practical choice is CWA vs. Kavita. Pick CWA if your library is primarily standard ebooks and you want the Calibre metadata engine underneath. Pick Kavita if you prioritize a polished, more actively maintained UI and your library leans toward manga or comics.

Bottom line

Calibre Web Automated does exactly what its name promises, and that’s rarer than it should be. The Calibre-plus-Calibre-Web parallel deployment problem is real, annoying, and has been the accepted cost of entry for a self-hosted ebook library for years. CWA eliminates it, adds automated ingestion, SSO, and KOReader sync, and ships it all in a single Docker container under a genuinely free license. At 5,162 stars, it’s found its audience — people who know what they want and are tired of the two-container compromise.

The honest caveat is the single-maintainer risk. This project’s quality and momentum depend on one person’s continued investment. That’s not a reason to avoid it — plenty of excellent self-hosted tools run this way — but it’s a reason to have a backup plan and to monitor the release cadence before building your entire library workflow around it.

If you own your ebooks and want them organized, searchable, and accessible from every device you own, this is currently the best single-container way to do it.

Sources

Ayush Pande, XDA Developers — “I built an all-in-one self-hosted entertainment suite with these 6 services” (May 20, 2025). https://www.xda-developers.com/i-built-a-self-hosted-entertainment-suite-with-these-services/
ElfHosted Documentation — “Hosted Calibre-Web — Cloud eBook Reader & Library”. https://docs.elfhosted.com/app/calibre-web/
Tim Kicker — “The Selfhosting Experience” (June 26, 2024). https://tim.kicker.dev/2024/06/26/the-selfhosting-experience/

Primary sources: