BookHaven
Released under GPL-3.0, BookHaven provides browser-based EPUB reader on self-hosted infrastructure.
A browser-based ebook manager, honestly reviewed. No marketing fluff, just what you get when you self-host it.
TL;DR
- What it is: A self-hosted, browser-based EPUB library manager — scan your local ebook collection once, read anything from any device without installing apps [README].
- Who it’s for: People with large EPUB collections who want a clean web UI to browse and read from any device on their network, and want to share that library with family or a small team [README].
- Cost savings: Kindle Unlimited runs $9.99/mo, Scribd $11.99/mo — and neither lets you own the books. BookHaven runs free on any $5–10/mo VPS. If you already have the ebooks, you pay nothing extra [README].
- Key strength: Non-destructive metadata editing (your files stay untouched), OPDS support for dedicated e-reader apps, OIDC/SSO for family deployments, and a reasonably modern UI for a solo project [README].
- Key weakness: 115 GitHub stars as of this writing — this is a young, single-maintainer project. No third-party reviews exist yet. You are betting on a small open-source project, not an established product [GitHub].
What is BookHaven
BookHaven is a self-hosted web application that scans a directory of EPUB files, indexes them into a database, and serves them through a browser UI. You point it at your ebook folder, it builds a library automatically, and from that point you can browse by author or series, search, read in the browser, download to a device, or connect a dedicated e-reader app via OPDS [README].
The pitch in the README is plain: “BookHaven scans and manages your local library of EPUB ebooks, and allows you to read and download your ebooks on any of your devices, with a sleek, modern, and responsive interface.” [README]. There’s no marketing layer here — this is a GitHub project by a single developer (HrBingR) with 325 commits and 115 stars as of March 2026.
What sets it apart from a basic file server is the combination of features you wouldn’t expect from a project this size: OIDC/SSO for authentication, OPDS for e-reader app integration, non-destructive metadata editing, role-based access control, CloudFlare Access support, and book upload via the UI. That’s a surprisingly complete feature set for a solo project [README].
The license is GPL-3.0, which means you can self-host freely but cannot fold it into a closed commercial product. For personal or small-business use, that restriction is irrelevant [GitHub].
Why people choose it
No third-party software reviews of BookHaven exist at the time of writing — the project is too young. What follows is drawn entirely from the GitHub README and primary source analysis.
The reason someone lands on BookHaven specifically, rather than Calibre-Web or Kavita, is usually one of three things.
They want a clean modern UI. Calibre-Web is the establishment choice, but it inherits Calibre’s desktop-era design DNA. Kavita has a stronger community but is heavier. BookHaven’s README shows a screenshot that looks contemporary — single-page app feel, responsive layout, author-browsing grid [README]. For non-technical family members who will be the end users, that matters.
They want OPDS without the complexity. OPDS (Open Publication Distribution System) is the protocol that lets apps like KOReader, Moon+ Reader, and Marvin connect directly to your server and download books. BookHaven supports it natively [README]. For someone with a Kobo or Android e-reader, this means the library is accessible from the device itself, not just a laptop browser.
They want multi-user access with basic role separation. BookHaven has RBAC (admin, editor, regular user), OIDC for SSO, and CloudFlare Access bypass support [README]. A family or small team can have proper user accounts without running a separate identity server. That’s a feature Calibre-Web had to add via a third-party fork and still isn’t clean.
Features
Based on the README:
Core library:
- Scans a local EPUB directory on a configurable interval, or manually on demand [README]
- Home page browsing sorted first by author alphabetically, then by series [README]
- Dedicated author page with alphabetical grid navigation — click a letter, see all authors starting with it [README]
- Search by author, book title, or series [README]
- Filters: favorites, finished, not-yet-finished [README]
- Book download to any device [README]
Reading:
- In-browser EPUB reading — no separate app required [README]
- No format conversion, no additional software on the client side [README]
Metadata:
- Non-destructive editing: title, author, series changes stored in the database only, original EPUB files untouched [README]
- Post-upload metadata form to fix metadata immediately after adding books [README]
Multi-user:
- Basic RBAC with admin/editor/user roles [README]
- OIDC support for SSO — new user registration and existing user login via external identity provider [README]
- CloudFlare Access integration — bypass the login screen when using CF Access in front of the app [README]
Integration:
- OPDS support for e-reader apps (KOReader, Moon+, Marvin, etc.) [README]
- Book request system — users can request titles, admins/editors can view and resolve [README]
- Upload via UI — drag-and-drop or file picker, with metadata correction after upload [README]
Infrastructure:
- Docker and Docker Compose deployment [README]
- Database support: MySQL, SQLite, PostgreSQL [README]
- Redis required for caching/session [README]
Pricing: SaaS vs self-hosted math
BookHaven has no SaaS version. It is self-hosted only. The cost equation is simple:
BookHaven (self-hosted):
- Software: $0 (GPL-3.0) [GitHub]
- VPS to run it: $5–10/mo (Hetzner, Contabo, or any small Linux server)
- Storage: depends on your library size — EPUBs are small, a 10,000-book library typically fits in under 20GB
What you’re escaping:
- Kindle Unlimited: $9.99/mo, ~4 million titles, DRM-locked, can’t keep books if you cancel
- Scribd: $11.99/mo, ebook + audiobook combo, rotating catalog that changes without notice
- Apple Books / Google Play Books: per-book purchase with DRM, library tied to account
If you already own your EPUB files (legally purchased DRM-free, or from sources like Standard Ebooks, Project Gutenberg, or Humble Bundle), your ongoing cost with BookHaven is exactly the VPS fee — typically $5–10/mo. Over a year, that’s $60–120 versus $120–144 for Kindle Unlimited, and the books you’ve added to BookHaven are yours permanently.
The honest framing: this tool isn’t for people building a new library. It’s for people who already have hundreds of EPUBs sitting in a folder and want a proper interface to read them from anywhere.
Deployment reality check
What you need:
- A Linux server or VPS with Docker and Docker Compose
- A database: MySQL, SQLite, or PostgreSQL (MySQL is the default in the example compose file) [README]
- Redis (bundled in the default compose example) [README]
- A domain and reverse proxy (Caddy or nginx) if you want HTTPS from outside your home network
- A folder of EPUB files accessible to the container
The setup path:
The README describes a four-step Docker Compose deploy: download the example files, rename them, edit the .env to configure database credentials and base URL, run docker compose up -d [README]. That’s the correct level of complexity — not beginner territory, but not painful for anyone who has deployed a Docker service before.
What can go wrong:
Library scanning. BookHaven scans a mounted directory. If you mount the wrong path, or your EPUBs are nested in a structure the scanner doesn’t expect, you’ll have an empty library. The README doesn’t document the expected directory structure in detail [README].
EPUB-only. If your collection includes PDFs, CBZs, or MOBIs, BookHaven won’t handle them. This is an EPUB reader, not a general document server [README]. If you have mixed formats, you need a different tool (Kavita or Calibre-Web) or a conversion step.
Single maintainer, 115 stars. This project does not have a community around it yet. If you hit a bug, you’re filing an issue with one developer. The changelog exists (there’s a CHANGELOG.md in the repo) which is a good sign, but there’s no forum, no Discord, no ecosystem of guides [GitHub]. Compare this to Calibre-Web (4,000+ stars, years of community documentation) or Kavita (7,000+ stars, active Discord).
No mobile app. Reading in a browser is fine on a tablet, but on an e-ink Kindle or Kobo you’re using the OPDS feed and a separate app. BookHaven doesn’t ship a native app and isn’t trying to [README].
Realistic time estimate for someone who’s deployed Docker before: 30–60 minutes to a working instance. For someone new to Docker: half a day, including learning the basics.
Pros and Cons
Pros
- Non-destructive metadata editing. Your original EPUB files are never touched. Changes live in the database. This matters when your files are from a carefully organized Calibre library — you don’t want a web app rewriting your source files [README].
- OPDS support built-in. Connects directly to KOReader, Moon+ Reader, and other OPDS-compatible apps on e-ink devices. This is the feature that turns a web app into an actual e-reader workflow [README].
- OIDC/SSO and RBAC out of the box. Most alternatives don’t ship with both. For a family or small-team deploy, this is real convenience [README].
- CloudFlare Access integration. If you’re already using CF Access to protect self-hosted services, the bypass flag means you don’t need a second authentication layer [README].
- Book requests. Users can request titles. Small feature, high value for family deployments where your teenager wants books you haven’t added yet [README].
- Upload via UI. Add books through the web interface without SSH access to the server [README].
- Active development. 325 commits, a maintained CHANGELOG, multilingual README [GitHub]. Signs of an engaged maintainer, even if the community is small.
Cons
- EPUB-only. PDFs, CBZs, MOBIs, AZW3s — not supported. If your collection is mixed format, this is a hard blocker [README].
- 115 stars, solo maintainer. Small project risk is real. If the maintainer loses interest, you’re maintaining a fork or migrating. No community documentation, no third-party guides [GitHub].
- No third-party reviews. Every claim in this article comes from the README. There’s no user feedback loop yet — no Trustpilot, no Reddit thread, no G2 page. Unknown reliability in production [GitHub].
- Requires Redis. That’s an additional service to run alongside the database. For a minimal home server, Redis-for-a-book-app feels heavy [README].
- No PDF/CBZ support is worth repeating — the self-hosted ebook reader market is full of tools that handle multiple formats, and BookHaven deliberately doesn’t [README].
- UI unverified. The README screenshot looks clean, but screenshots are chosen by the developer. Without user reviews, the actual UX quality is unverified.
Who should use this / who shouldn’t
Use BookHaven if:
- You have a large EPUB collection (legal, DRM-free files) and want a proper library interface accessible from any device.
- You have family or roommates who want to access a shared library without each person managing their own files.
- You already use CloudFlare Access for other self-hosted services and want consistent authentication.
- You need OPDS to sync with your Kobo, Kindle (via KOReader), or other e-reader app.
- You’re willing to accept small-project risk in exchange for a lighter, more focused tool.
Skip it (use Calibre-Web instead) if:
- You need format conversion (EPUB → MOBI, etc.) alongside library management — Calibre-Web integrates with Calibre for this.
- You want the most battle-tested self-hosted option with years of community guides and a large support forum.
- Your collection includes PDFs or comic formats.
Skip it (use Kavita instead) if:
- You want multi-format support (EPUB, PDF, CBZ/CBR, manga) in one tool.
- You want a more active community and faster bug response.
- You want reading statistics, reading lists, and a more polished reading interface.
Skip it (stay on Kindle/Kobo store) if:
- You don’t own DRM-free EPUBs — BookHaven only works with files you already have.
- You don’t want to maintain server infrastructure. There’s no managed cloud option.
Alternatives worth considering
- Calibre-Web — the established standard. Requires a Calibre library on disk, supports format conversion, has a large community. More complex to set up, heavier, but far more documentation and community support. Better choice if you already use Calibre on your desktop.
- Kavita — multi-format (EPUB, PDF, CBZ, manga), actively developed, larger community, better reading interface with statistics. Better default choice for most people who want a general media server for reading.
- Koodo Reader — browser-based EPUB reader but client-side only (reads files from your local device). No server component, no multi-user, no OPDS. Different use case.
- Ubooquity — older Java-based option, supports comics and books, OPDS server. Still maintained but UI is dated.
- Readarr + Calibre — if you also want automated book acquisition and organization, this combo handles the full pipeline. More infrastructure, more capability.
For a non-technical founder wanting the simplest path: Kavita is the safer bet with more community support. BookHaven is for people who specifically want the narrower EPUB focus and modern UI, and are comfortable accepting the smaller project risk.
Bottom line
BookHaven is a promising young project in a crowded but underserved category. The feature list is more complete than you’d expect from 115 stars — OPDS, OIDC, RBAC, non-destructive metadata, CloudFlare Access support, and book requests are real features, not paper promises. But “promising” is not the same as “proven.” There are no third-party reviews, no community forum, no track record of production reliability, and the entire project depends on one maintainer staying interested.
If you have an EPUB collection and want a self-hosted library server, and you’re willing to accept small-project risk, BookHaven is worth a test deploy. If you need certainty, use Kavita or Calibre-Web. The math on owning your library rather than renting it from Kindle Unlimited is obvious either way — the question is just which server you trust with it.
Sources
- HrBingR/BookHaven — GitHub README (115 stars, GPL-3.0, 325 commits). https://github.com/HrBingR/BookHaven
Note: No third-party software reviews of BookHaven exist at the time of writing. All feature and deployment claims in this article are sourced from the project README and GitHub repository directly. The links provided as third-party sources in the research brief ([1]–[5]) refer to unrelated “BookHaven” named entities (a book review blog and Stanford’s literary blog) and contain no information about the HrBingR/BookHaven software application.
Features
Authentication & Access
- Role-Based Access Control
- Single Sign-On (SSO)
Search & Discovery
- Advanced Filters
Compare BookHaven
Related Documents & Knowledge Base Tools
View all 226 →Stirling-PDF
75KThe most popular self-hosted PDF platform — merge, split, convert, OCR, sign, and process documents with AI, all running on your own infrastructure.
AppFlowy
69KAn open-source Notion alternative with AI, wikis, projects, and databases — cross-platform (desktop, mobile, web) with offline-first architecture and full data ownership.
AFFiNE Community Edition
66KAn open-source workspace that merges docs, whiteboards, and databases into one platform — a privacy-focused alternative to Notion and Miro with AI built in.
Docusaurus
64KA static site generator built on React for documentation websites — write in Markdown/MDX, version your docs, and deploy anywhere. Created by Meta.
Crawl4AI
62KOpen-source LLM-friendly web crawler that generates clean markdown from any website, purpose-built for RAG pipelines, AI data extraction, and automated research.
Atom
61KGitHub's hackable text editor, officially sunset in December 2022. The codebase remains archived on GitHub as a reference for community forks like Pulsar.