BookWyrm

Key features

• Shelves, statuses, and annual goals The classic to-read, reading, read, and stopped-reading shelves combine with an annual reading goal and progress statistics, so yearly challenges work the way Goodreads users expect.[1]

• Reviews with optional ratings Reviews can include star ratings or be rating-free, and ratings and reviews aggregate across the network by default, so small instances still show meaningful book-level reception.[1]

• Granular privacy controls Every status, review, rating, quote, and reply can be public, unlisted, followers-only, or direct, and follower requests can require manual approval, which matters for readers logging personal material.[1]

• ActivityPub federation Users follow readers on other BookWyrm servers and can be followed from Mastodon, so the reading community is not fenced inside one site, and accounts can migrate between instances.[1][2]

• Connector-backed book data with manual fallback Book records come through Open Library and Inventaire connectors, and where those fall short, users can add books manually rather than waiting on a central data team.[1]

• Export, RSS, and reading statistics Libraries export in convenient formats for use in other services, shelves and user pages offer RSS feeds, and yearly statistics summarize reading with an optional PDF export.[1]

• Documented Docker self-hosting Production deployment runs the web app, task workers, scheduler, database, and cache as containers, with documented configuration and backup steps for the database, activity records, and uploaded media.[1]

• Community translations The interface is translated into many languages through an open translation workflow, and the instance list includes French- and German-language servers alongside English ones.[1][2]

Who will love it

• Readers leaving Amazon-owned tracking Readers leaving Goodreads over Amazon ownership and tracking will feel at home, because BookWyrm reproduces the core shelf, review, and goal workflow on community-run infrastructure with open registration on the flagship instance.[1][2]

• Fediverse users Fediverse users benefit most from cross-instance follows and Mastodon visibility, since reading posts reach the timelines they already use instead of living in a separate silo.[1][2]

• Docker self-hosters Docker self-hosters wanting their own reading instance get a containerized, documented production path including backups, which fits a home-server or small-community setup.[1]

Who should avoid it

• Smaller catalog and no official mobile app The federated network is far smaller than Goodreads at roughly tens of thousands of users, niche book data can be incomplete, and there is no official native mobile app, only an installable web app and unofficial clients.[1][2]

• Server-choice friction for newcomers Federation starts with picking an instance and understanding cross-server follows and migration, which is more friction than a single centralized signup for non-technical readers.[1]

• Varying instance guarantees Instance rules, moderation capacity, and longevity vary across volunteer-run servers, so communities with formal requirements should vet an instance before committing.[1]

Interoperability and portability