The blank canvas
Spreadsheet
Best when your collection is small or you want total freedom over the columns.
You become the product designer: views, relationships, care history, and comparisons are all yours to build.
A fair comparison · v1.4.6
There is no crowded lane. That is the point.
BladeVault is not trying to beat a dozen knife apps at their own game. It is a focused answer to a quieter problem: your collection deserves better than a pile of tabs, a heroic spreadsheet, or a generic inventory form.
0fake rivals named
1focused vault
∞ways to make it yours
Market map / honest edition4 approaches
The broad toolbox
Generic inventory app
Best when knives are one category inside a much bigger asset list.
The tradeoff for breadth is usually less room for model families, provenance, measurements, and collector-specific context.
The custom build
DIY database
Best when designing schemas and maintaining infrastructure is part of the hobby.
You get exactly what you build—and inherit every screen, migration, backup, and maintenance decision.
The focused tool
BladeVault
Best when you want a serious knife collection workflow ready on day one.
It is intentionally focused: your knife vault, not every asset you own.
No grand claims. Just a clearer fit test.
The useful difference
Less assembly. More collecting.
A spreadsheet can record a knife. A generic inventory app can hold one. BladeVault is built around what happens after that: comparing close variants, filling missing specs, remembering maintenance, and understanding the shape of the whole vault.
Compare with context
Keep multiple named comparison lists, line up the details, and export a landscape PDF when a decision needs to leave the app.
Care belongs to the record
Maintenance history stays with the knife instead of disappearing into a notes file or a memory you meant to write down.
Keep the source close
Save source URLs and captured product pages alongside the record, so provenance does not evaporate after the purchase.
Own the working data
Local SQLite, images, backups, optional app lock, and local MCP access keep the vault under your control.
Side-by-side, without the spin
How the approaches differ
These are categories, not product reviews. Choose the shape of tool that matches how you actually want to keep your collection.
| What matters | BladeVaultThe focused tool | Spreadsheet | Generic app | DIY database |
|---|---|---|---|---|
| Designed around knives | Yes — the vocabulary is already there | You create the columns | Usually generic | You design the model |
| Model families & variants | Native grouping with distinct records | Manual links or duplicated rows | Depends on the app | Possible, if you build it |
| Side-by-side comparison | Named lists with PDF export | Possible, but hand-built | Varies | Possible, if you build it |
| Maintenance history | Attached to each knife | Usually a notes column | Often an adaptation | You own the workflow |
| Where your records live | Local SQLite + images | A file you control | Depends on the service | Wherever you host it |
| AI / MCP access | Local read access through MCP | Not built in | Depends on the app | You connect it yourself |
“Depends” is doing honest work here. Other tools may support a feature; the difference is whether the workflow is already shaped around your collection.
The short version
If you want a vault, start here.
You care about the difference between two close variants.
You want care, provenance, and notes next to the object they describe.
You would rather own the data than rent access to your collection.
You want a tool that is specific enough to be useful, and open enough to inspect.
One last honest note
You may not need BladeVault yet.
If a notes file or spreadsheet already gives you what you need, keep it. BladeVault is for the moment when the collection becomes a system worth caring for—and you want that system to stay yours.
Choose your setup