This is the companion to I own my books, where I made the case for stripping DRM and actually owning what I buy. This post is the machinery overview: how I store, serve, and read all of it from my own homelab.
My books workflow
When I find a book I want to buy, I go to eBooks.com and search for it. They have most titles, but occasionally I will have to go to Kobo to find it; regardless, I purchase the book.
Note: This is just an overview of how this works and is not a technical, step-by-step walk-thru.
Calibre
If the book has DRM, the distributor gives me a file with the .acsm extension. If the book is DRM free, then they hand me the ePUB file directly. Either way, the next step is to import the downloaded file into Calibre. With the right plug-ins, Calibre will automatically download the book, remove the DRM (if any) and add the ePUB file to the Calibre books library.
Syncthing
Once the book is in Calibre as a DRM-free ePUB, Syncthing syncs it to one of my homelab instances that serves it with Calibre-Web.
Calibre-Web
I use Calibre-Web to then serve my Calibre books on my local network. Calibre-Web implements the same endpoints the Kobo store exposes: sync, library metadata, cover images, reading state. This is the first piece that allows me to connect my books library to my Kobo device.
DNS and certificates
Two things have to be in place to allow my Kobo to connect to Calibre-Web. My local DNS has to point an internal hostname at the server running Calibre-Web. And that server needs a real, publicly trusted TLS certificate, because the Kobo thinks it’s talking to a commercial store and won’t accept a self-signed one. Getting a legitimate certificate for a hostname that only exists inside my homelab is the fiddly part. I may write that up separately.
Kobo
Now I update the api_endpoint setting in the .kobo/Kobo/Kobo eReader.conf file on the Kobo itself so it points to the internal hostname from the DNS and certificates section above. I plug the Kobo into my computer over USB and it mounts as a drive, which is how I get at the file. There’s no way to do this from the device’s settings menus.
All together now
So my workflow looks like this in practice:
- Buy and download the book.
- Import the book into Calibre.
- Open my Kobo device and download the new book to the reader.
- Read.
The default software on the Kobo is a first-class reading experience. Connecting it to my Calibre-Web server keeps that experience intact while my whole library syncs down over my local network.
KOReader
I see many people talking about KOReader, so when I first started on this path, I had every intention of installing and using it. In my own tests, the software just felt a lot rougher and harder to make into a nice reading experience, and I still had to connect my device directly to my laptop to load books. No shade towards KOReader and all the people who seem to love it, but the Kobo reading software works perfectly for me, and I can’t think of a feature that KOReader provides that isn’t already in the Kobo software.
Audiobooks
I listen to a fair amount of audiobooks, and my preference is to purchase them from Libro.fm. Their audiobooks are already DRM-free, so I just download the files from the Libro.fm website and boom, I have my backup.
Audible books do have DRM, but I can remove it. In order to make my backups, I use ffmpeg with credentials that audible-cli legitimately pulls from my authenticated account. I’m decrypting content I bought, using a key I’m entitled to, into a universally playable format (.m4b). So I can back up even Audible exclusives like Dungeon Crawler #8.
No matter how I purchased and backed up the audiobooks, I prefer to listen to them in Audiobookshelf, which is a self-hosted solution in my homelab.
Conclusion
And that’s my books workflow and an overview of how I self-host all this. I’m really interested in hearing about others’ book workflows too. Drop me a line if you’ve written something up and want to share.
Originally posted on my site: https://michaelharley.net/posts/2026/07/21/how-i-self-host-my-ebooks-and-audiobooks/
Excellent writeup! Thanks for posting. Lately, I’ve been using Calibre Web Automated, an active fork with a lot of added features and compatibility features.
Depending on someone’s setup it may or not be worth it to switch (Calibre-web works great), but I’d definitely recommend it for someone starting up.
that’s me.
my partner asked me to self-host their e-books. For now i only have jellyfin (on Debian) running to stream music locally. I bookmarked calibre-web last week as an e-book solution.
What made you choose c-w automated over c-w? Any other advices?
Sure. As a fork, it has all of the benefits of Calibre-web. It’s stable, well established, versitile, works well with Calibre desktop software (they are three different projects, despite the similar names). Yet it has a number of different features like automatic ingest, writing/converting files, sending to different devices, etc. There is a pretty complete list on the GitHub page I linked. It has a big community and active development, so its likely that any features you might look for could be coming soon.
There are other self hosted software projects for ebooks (you can even use Jellyfin!). I had switched to Booklore at one point for a more modern UI and tracking, but it was more flash than execution and ultimately looks like it flamed out over some community issues. There are also projects like Kavita that are designed for features around comics/manga, but also do an excellent job with ebooks in general.
You should consider two things: what the library looks like, and where it will be read. If it is mostly books with a few other media (like comics, PDFs, etc.), then CWA is probably a good bet. If it’s mostly comics and manga with some books and other media, consider whether Kavita is the better fit. If it is mostly DRM content, and you or if you want to manage it through Calibre Desktop, how does it connect? How often are new books being added and from where?
What screen will it ultimately be read on? If it’s an ereader, check out the “books” and “self-hosted” communities here on Lemmy for which protocol, etc. is used. If it will be read on a computer or mobile device, what apps are available? Will it be read on multiple devices?
For example, if it is a small library, read on an Android/iOS device, Jellyfin with JellyBook may be fine. If it is a large manga library already tracked on AniList, Kavita may be a good bet. If features like notes and highlights are important to sync across devices, something like Anx Reader with WebDAV might even be better.
What OP describes is an excellent setup for 90% of cases.