Vaultisse: A Deep Dive into the Self-Hosted Physical Book Collection Manager
Vaultisse is an open-source self-hosted tool for tracking individual physical book copies, not just title lists.
Vaultisse is a physical book collection manager shared by an open-source developer on Reddit's r/selfhosted community. Its core idea is to manage each physical copy as an independent entity rather than grouping by title. It supports ISBN scanning for automatic metadata retrieval, copy status tracking (available/checked out/damaged/lost), shelf location tracking, borrower directories, and barcode label generation. Built on Vue 3 + Express + PostgreSQL, it supports both Docker Compose and PM2 deployment, with JWTs stored in HTTP-only cookies for security. MIT-licensed with a read-only online demo, it targets home collectors, teachers, and small community lending library operators.
For home library enthusiasts, teachers, or people running small lending libraries, managing physical books can be a genuine headache. Simply tracking "which books I own" isn't enough — the real pain points lie in monitoring the location, condition, and lending status of every physical copy. A developer on the Reddit community r/selfhosted shared their open-source project Vaultisse, built specifically to address this need.
From "Book List" to "Physical Copies": A Shift in Thinking
Vaultisse's core purpose is fundamentally different from typical reading list apps. The developer explicitly stated in their post that the tool was built to "track the actual physical copies of books, not just maintain a list of titles I own."
This distinction may seem subtle, but it's crucial. If you have multiple copies of the same book, or need to know which shelf a book is on, whether it's been lent out, or whether it's damaged — traditional book catalog software typically falls short. Vaultisse manages each physical copy as an individual entity, making it far better suited to real-world physical scenarios like classroom libraries or community lending collections.
Feature Overview
Vaultisse's features are tightly focused on physical management, covering the full workflow from cataloging to lending tracking:
- ISBN scanning and automatic metadata retrieval: Scan or enter an ISBN and the system automatically fetches cover art, author, and related metadata — no manual entry required.
- Individual copy tracking: Each physical copy is managed independently rather than merged by title.
- Copy status management: Mark copies as available, checked out, damaged, or lost.
- Borrower directory: Maintain borrower information and always know who has which book.
- Shelf/location tracking: Record the physical location of each book so you're not relying on memory.
- Barcode/ISBN label generation: Print labels for physical re-scanning, completing the management loop.
- Full-text search and a collection statistics dashboard.
- Multilingual interface: Supports English, Spanish, Catalan, and Italian.
This feature set closely aligns with the practical needs of a small lending system. The combination of borrower directory and location tracking in particular elevates it beyond a simple collection manager.
ISBN (International Standard Book Number) is a globally recognized unique identifier for books. The current standard is the 13-digit ISBN-13 (earlier editions used the 10-digit ISBN-10). Automatic metadata retrieval based on ISBN typically relies on APIs from public bibliographic databases such as Open Library, Google Books, or ISBNdb. This kind of automated entry dramatically lowers the barrier to building a catalog — users simply scan the barcode on the back cover without manually typing in the title, author, publisher, and so on. For collections of significant size (such as a classroom reading corner or community lending library), this feature is often the deciding factor in a tool's usability: manually entering metadata for hundreds of books is practically infeasible.
Tech Stack and Deployment
For self-hosters, deployment complexity and technology choices are often key factors in adoption. Vaultisse strikes a clean, modern balance here.
Frontend and Backend Architecture
- Frontend: Vue 3 + Vuetify
- Backend: Express + TypeScript + PostgreSQL
- Authentication: JWT stored in HTTP-only cookies
The application runs as a single Node.js process, keeping the architecture simple and maintenance overhead low. Storing JWTs in HTTP-only cookies reflects a commitment to basic security best practices.
JWT (JSON Web Token) is an open standard (RFC 7519) for securely transmitting digitally signed claims between parties, commonly used for authentication in web applications. Storing a JWT in an HTTP-only cookie means client-side JavaScript cannot directly read the token, effectively preventing cross-site scripting (XSS) attacks from stealing authentication credentials — a notable improvement over the common practice of storing JWTs in localStorage, which has well-known security drawbacks. Vuetify is a Material Design component library for Vue 3 that provides ready-to-use UI components out of the box. PM2 is a widely used process manager in the Node.js ecosystem that supports automatic restarts after crashes, log management, and other production operations — a common alternative when container-based deployment is not preferred.
Two Deployment Options
The default and recommended approach is Docker Compose deployment, requiring only Docker and Docker Compose. The default configuration includes two components: the PostgreSQL database and the Vaultisse application itself. Once environment variables are configured, a single command brings everything up:
docker compose up -d
For users who prefer not to use Docker, the repository also includes a non-containerized deployment option based on PM2, documented in DEPLOYMENT.md. This dual-path deployment design accommodates self-hosters with different technical preferences.
Open Source License and Demo
Vaultisse is open source under the MIT license, with source code hosted on GitHub and documentation at docs.vaultisse.com. The developer also provides a read-only online demo at demo.vaultisse.com — demo credentials can be found in the GitHub README, so interested users can try it out without installing anything.
The MIT license means broad freedom of use, with minimal restrictions on personal use or derivative projects, which makes it particularly appealing to the open-source self-hosting community.
Who Is Vaultisse For?
Based on its feature set, Vaultisse targets three main user types:
- Home library enthusiasts: People with large physical collections who need to know which shelf each book is on.
- Teachers: Managing a classroom reading corner and tracking student borrowing.
- Small lending library operators: Anyone needing full borrower management and copy status tracking.
The developer has also expressed openness to feedback from self-hosters already using book cataloging software, and welcomes suggestions for making the tool work better for large personal collections or small lending libraries. This proactive approach to community feedback is often a healthy indicator that an open-source project will continue to evolve.
Conclusion
Vaultisse fills a niche in the self-hosting space: physical management of tangible book copies. Rather than aiming to be a comprehensive solution, it focuses squarely on physical copy tracking, location management, and the lending workflow — and does so thoughtfully. Paired with a clean tech stack, one-command Docker deployment, and an MIT license, it's worth watching for book lovers who want to move away from cloud services and take ownership of their data. That said, as a tool that grew out of a personal project, its performance with very large collections remains to be validated by the broader community.
Related articles
MiniMax H3 Cloud GPU Benchmark: Speed and Cost Per Dollar Across Four Platforms and Four Cards
Developer self-funded benchmark of MiniMax H3 T2V across Vast.ai, Hyperstack, RunPod, and Nebius — RTX 4090 spot beats H100 on cost, L40S matches 4090 speed, full data included.
Fireworks Lab Partners with Genspark on RL Research: 100+ Experiments to Catch Model Reward Hacking
Fireworks Lab and Genspark co-develop RL algorithms on frontier-grade infrastructure, running 100+ experiments and using trajectory inspection to catch reward hacking.
No Fine-Tuning Required: Building a Human-Like Chatbot with System Prompts
No fine-tuning needed: a Reddit veteran shows how system prompts alone can turn Qwen, DeepSeek, and Gemma into human-like chat personas. A breakdown of the 3-step framework.