u/Bitter-Pop-2514

Github: https://github.com/bookorbit/bookorbit (⭐ star appreciated!)

Website: https://bookorbit.app

Try the Demo: Live demo

https://preview.redd.it/oeqmju884j1h1.jpg?width=2400&format=pjpg&auto=webp&s=64bea53528cc332b01808db9285bd20e726a1864

Description:

Hi r/ereader - I’ve been building BookOrbit, a self-hosted reading platform for people who want to manage their own library and device workflows.

If you use multiple devices/apps and want control over your files/metadata, BookOrbit is designed for that.

Why it might be useful:

• Free + open source (AGPL v3), self-hosted on your own server/NAS/VPS.
• Kobo support: pair devices with per-device token URLs and sync books from collections you mark for Kobo.
• Kindle support: Send-to-Kindle via email from inside BookOrbit.
• Built-in readers: EPUB/KEPUB/MOBI/AZW3, PDF, CBZ/CBR, and audiobook formats.
• Metadata + organization: 9 metadata providers, collections, smart scopes, and multi-library setup.
• Multi-user ready: permissions, per-library access, and optional OIDC/SSO.

I’d really value feedback from e-reader users on Kobo flow, Kindle email delivery UX, and what integrations you want next.

Project Name: BookOrbit

Github: https://github.com/bookorbit/bookorbit (🌟 star would be appreciated)

Website: https://bookorbit.app | Demo: Live demo

https://preview.redd.it/4z33rr7b3c1h1.jpg?width=2400&format=pjpg&auto=webp&s=d85ddfd7228dc082a643e50df031f162813a7e4c

Description:

For the past few months I've been building BookOrbit, and it's finally in a place I'm happy to share here. BookOrbit grew out of using Booklore, same passion for the problem, entirely different approach and foundation.

What's different:

Booklore is a fantastic project and I have a lot of respect for it. BookOrbit takes the same vision and rebuilds it on a different lightweight stack (more aligned for self-hosters), with enhanced features and a longer-term architecture in mind. Here's what that means in practice:

• Lighter stack - Booklore runs on Spring Boot/Java, solid but with a real JVM memory floor. BookOrbit uses NestJS (Node) + PostgreSQL, idling at ~125-150 MB for large libraries. The live demo hosts 56,000+ books and audiobooks on a tiny VPS at ~225 MB. PostgreSQL was a deliberate choice over MariaDB for its concurrency model, which makes charting and analytics queries genuinely fast.
• Snappy UI - dark/light mode, server-side pagination throughout, handles any library size without slugging out.
• Richer metadata, table views, and analytics - significantly improved workflows and more depth across the board.
• Book Dock - takes book drop to a new level with enhanced UX and smoother workflows for importing books.
• Multi-provider OIDC - full admin UI to configure, reorder, and test multiple identity providers simultaneously (Authentik, Keycloak, Authelia, etc.).
• Tested properly - high unit test coverage and extensive end-to-end tests to keep regressions in check.
• Hardened security - CodeQL analysis, Trivy scanning, and SBOM generation (in progress).

More features at a glance:

• Built-in readers for EPUB/KEPUB/MOBI/AZW3, PDF, CBZ/CBR, and audiobooks (M4B/MP3/FLAC/OPUS/OGG)
• Metadata enrichment from 9 providers (Google Books, Goodreads, Hardcover, Audible, ComicVine, and more) with field-level lock/overwrite control
• Kobo sync with auto-push and reading position, plus two-way progress sync with KOReader
• Multi-user with per-library access control, granular role-based permissions, and fully isolated reading data per user
• OPDS catalog, Book Dock (upload staging before files hit your library), and Send-to-Kindle email delivery
• Customizable dashboard widgets: currently reading, reading streak, goals, reading rhythm, diversity score, year projection, and more
• Statistics page with reading heatmaps, pace, genre breakdowns, top authors/series, and library trends over time
• Grid, list, and powerful table view with sortable, configurable columns

Where this is going:

The goal is to make BookOrbit the most capable and pleasant self-hosted reading platform out there. Right now the focus is on stability, bug fixes, and polishing the overall experience - while building a healthy community around the project.

Long term, the vision is to evolve BookOrbit into a complete reading and metadata ecosystem: deeper Kobo and KOReader integrations, smarter metadata management and automation, enhancing ebook and audiobook reader capabilities, integration with AI tools, and whatever the community shapes next.

Get involved:

This project thrives with community input, and every kind of contribution genuinely matters - whether that's your first PR or your fiftieth. Here's where to start:

• Found a bug? Open an issue - even a rough description helps
• Have a feature idea? Start a Discussion - all ideas are welcome
• Want to contribute code or docs? Check the Contributing guide - the codebase is well-tested and documented, so it's a friendly place to get started
• Enjoying the project? Consider starring the repository on GitHub, it helps the project reach more self-hosters and contributors: https://github.com/bookorbit/bookorbit