Skip to content
Boooks
The Collector's Social Network

For people whose
shelves are the
index of a life.

Catalog every book, vinyl, and CD you own against a local-first metadata index. Lend without losing them. Install it like an app, take it offline. Find the readers and listeners who share your edges.

Live
boooks.net
Pages
123 frontend
Auth
Wenme passkeys
Stack
.NET 10 + Go
Boooks card
A KaritKarma product
/boooks
  • Asset typesBooks, vinyl, CDs (+pluggable)
  • Metadatatsvector + pg_trgm, local-first
  • Cover search512-dim CLIP + pgvector
  • Sign-inPasskey via Wenme
  • Hero featureBorrow + lend
  • InstallPWA, works offline
Everything ships except payments
Definition

What is Boooks?

Boooks is a unified social network and asset-management platform for people who own physical creative assets. It catalogs books, vinyl, and CDs at launch, runs a borrow and lend system designed for collections that actually circulate, and connects collectors through reading clubs, collector groups, and a feed ranked for taste, not for outrage.

It is a KaritKarma product, live at boooks.net. The auth layer is Wenme. Authorization is Darwan, integrated and fail-closed. Payments are deferred by design behind a build-time flag. The collection, social, lending, marketplace, and reading platform logic is the Boooks team's own work on top of that shared infrastructure.

34
Lending endpoints
Across 5 controllers: transactions, circles, insurance, reliability, policies
54
API controllers
457 HTTP endpoints across the .NET monolith and the Go strangler backend
55
Notification types
Triggered from lending, social, marketplace, groups, store, and publisher events
8
Go strangler services
graph, profiles, rooms, digests, reviews, domains, feed, search
Four pillars

Built for collectors, not casual readers.

Goodreads is a book log. Discogs is a music database. Boooks is what they would be if they were designed for the same person, in the same decade.

Live at boooks.net, payments in build
01
Catalog

Local-first metadata lookup.

Scan a barcode or type a title. PostgreSQL tsvector plus pg_trgm full-text search answers from a self-hosted index first, falling back to live APIs only when local results run thin. A Python CLIP sidecar matches cover photos against 512-dimension pgvector embeddings, so a phone snap of a spine finds the edition.

02
Lend

Borrow and lend without losing a book.

A 34-endpoint lending stack across five controllers: transactions, lending circles, lending insurance, reliability scores with chains and stats, and per-user lending policies. Reliability builds across every successful return; reminders escalate politely.

03
Connect

A feed built for collectors.

Posts, stories, reviews, trending, and discovery, with book clubs and collector groups, real-time chat over SignalR, and 55 in-app notification types spanning lending, social, marketplace, and reading events.

04
Trade

Marketplace surfaces, payments deferred.

List from your library with condition grading, offers, and filtered search. Every money-moving step is feature-flagged off behind a build-time flag and labelled coming soon until the payment rail ships. Wishlists and notifications are live today.

Asset types

One library for everything that earns a shelf.

Books, vinyl, and CDs share a metadata model, a condition-grading system, and a social fabric. New asset types plug in from the admin UI by defining a JSONB schema and condition grades, with no new code path required.

01

Books

Gutenberg + Goodreads

60,557 Gutenberg works imported into the built-in e-reader. Goodreads CSV import with ISBN deduplication brings an existing shelf across in one batch.

02

Vinyl + CDs

Discogs + MusicBrainz

Discogs CSV import with release-level matching for collections you already track, pressing-level catalog numbers preserved through the import.

03

Schema-configurable

Admin-defined types

Books and music ship today. Watches, fountain pens, comics, and cassettes plug in through schema-configurable JSONB asset types and condition grades, with no new code path required.

Hero feature

Books come back.

The most common bug in any private library is the friend who meant to return the Murakami. Boooks treats lending as a first class transaction. Thirty-four endpoints across five controllers. Reliability scores per borrower. Lending chains so a third hand-off still tracks back. Automated reminders that escalate politely.

  • Lender, borrower, condition, return date, all captured at hand-off
  • Reliability score builds across every successful return
  • Lending circles and available-to-borrow inventory for your trusted people
  • Lending insurance and per-lender policy templates (max books, duration, who qualifies)
  • Escalating reminder cadence over email and in-app notifications
Lender record
Anika R.
Reliability
97
Books lent
42
Returned on time
39
Active loans
3
Avg duration
11 days
Current loans
  • Norwegian Wood
    Murakami
    Due in 4 days
  • Pachinko
    Lee
    Due tomorrow
  • The Stranger
    Camus
    Overdue by 2
Mockup
Comparison

Boooks vs Goodreads vs Discogs vs a spreadsheet.

Most collectors triangulate. A spreadsheet for the rare stuff, a site each for books and music, and a memory for who borrowed which Marquez. Boooks is the first platform that holds all of that in one place.

CapabilityBoooksGoodreadsDiscogsSpreadsheet
Catalog physical booksMusic onlyManual
Catalog vinyl and CDsManual
Lending with reliability scores
MarketplaceComing soon
Reading clubs and collector groupsClubs only
Installable, offline-capable PWA
Cross-collection (own all three?)If you re-key it
Self-hosted metadata, no remote rate-limit
Passwordless sign-in

Scroll for full table

Onboarding

Three steps to a populated shelf.

The longest catalog migration we have seen took an evening. Bring a Goodreads CSV, a Discogs CSV, or scan a stack of barcodes against the local index.

  1. 01

    Continue with Wenme

    Single button on the auth page. Passkey or magic link, no email-password screen anywhere. OAuth 2.1 with PKCE only. Sessions are Boooks-owned.

  2. 02

    Import what you already have

    Goodreads CSV with ISBN dedup and Discogs CSV with release matching, up to a 50MB file ceiling. Imports run as background batches, create missing assets, and respect reading-status columns.

  3. 03

    Discover, lend, connect

    A collector feed, full-text search over the local index, vanity URLs at boooks.net/yourname, and lending circles for the people you actually trust with a first edition.

Installs like an app

A real PWA with a hand-written service worker.

No wrapper, no app-store wait. The service worker is written by hand with an explicit strategy per route, so the shelf opens in a basement and the lending data is never stale.

sw.js

Per-route caching, written on purpose.

Pages
Network-first HTML with an offline fallback
API
Network-only, so lending data is never stale
Static assets
Cache-first for hashed, immutable files
Images
Stale-while-revalidate, capped at 60 entries

A built-in e-reader, with free books.

The reading platform serves public-domain works from the 60,557-strong Gutenberg import at /read and /free-books, inside the same app as your physical shelf.

B2B Spaces

One front door, eight route groups.

Beyond the consumer app, Boooks ships working Spaces for the trade: 49 pages across store POS, publisher tools, library ILS, and admin, behind one passwordless sign-in.

Store POS
15 pages

Point of sale and inventory ERP for book and record shops

Publisher
16 pages

Catalog, metadata, and royalty surfaces for publishers

Library ILS
12 pages

Circulation and OPAC for lending libraries

Admin
6 pages

Platform administration gated by Darwan authorization

KaritKarma footprint

Built on the platform we already operate.

Wenme for auth. Darwan for permissions, fail-closed. The rest of the engine room (PostgreSQL 18 with pgvector, SignalR over a Redis backplane, a Python CLIP sidecar) is operated by the Boooks team. 167 domain entities, 47 EF Core migrations.

Powered by
Wenme
Passkey sign-in, OAuth 2.1 + PKCE
Powered by
Darwan
RBAC, fail-closed
Powered by
PG 18 + pgvector
512-dim cover search
Powered by
SignalR + Redis
Chat + 55 notification types
Questions

What people ask before they sign up.

Each answer mirrors the on-page text in the FAQPage structured data on this page, so AI answer engines and audit reviewers see the same wording.

01What is Boooks?
Boooks is a collector-focused social network and collection-management platform for physical media: books, vinyl, and CDs at launch, with watches, comics, and fountain pens addable from a schema-configured admin UI. It runs a 34-endpoint borrow and lend stack across five controllers, an installable offline-capable PWA, reading clubs, a built-in e-reader serving 60,557 Gutenberg works, and 8 Go strangler services alongside the .NET monolith. Boooks is a KaritKarma product, live at boooks.net.
02How is Boooks different from Goodreads, Discogs, and a spreadsheet?
Goodreads covers books, Discogs covers music, and a spreadsheet covers neither. Boooks is the first platform that catalogs books, vinyl, and CDs in one library, with a borrow and lend hero feature none of those tools have: 34 endpoints across five controllers covering transactions, lending circles, lending insurance, reliability scores, and per-user lending policies, so books actually come back. The schema is configurable from the admin UI, so additional asset types plug in through JSONB without a new code path.
03Where does the metadata come from?
Boooks runs a local-first metadata lookup backed by PostgreSQL tsvector plus pg_trgm full-text search, so the common query answers with zero per-request cost and no remote rate limit. Project Gutenberg is imported in full at 60,557 works for the built-in e-reader. A Python CLIP embedder sidecar produces 512-dimension vectors stored in pgvector, powering image-similarity cover search: photograph a spine and the edition resolves. Goodreads and Discogs CSV imports bring an existing collection across in one batch.
04How does Boooks handle authentication?
Boooks is passwordless. Sign-in goes through Wenme using OAuth 2.1 with PKCE, supporting passkeys, biometrics, and hardware security keys. The password-flow pages (forgot password, reset, verify) do not exist; those journeys are owned by Wenme. Authorization is Darwan, integrated and fail-closed. Sessions are Boooks-owned.
05Can I import my existing collections?
Yes. CSV import is shipped for both Goodreads (with ISBN deduplication) and Discogs (with release-level matching). Imports run as background batches with a 50-megabyte file ceiling, create assets if they do not exist in the local index, and link them to your library while respecting reading-status and rating columns from the source file.
06Is Boooks free?
Today the whole platform is free to use: catalog, lending, social, the e-reader, and the B2B Spaces, with no card required. Payments are deferred by design behind a build-time flag. Every money-moving surface (marketplace checkout, POS payments, publisher royalties) ships feature-flagged off and presents a coming-soon state until the payment rail goes live.
Go to boooks.net

Your shelf is the
first draft of your taste.

Catalog it, lend it, talk about it with the people who would actually read your annotations. Catalog, lending, social, and the B2B Spaces are live. Free to start, passwordless to sign in.

Free to use, no cardGoodreads + Discogs importBuilt by KaritKarma