Search ten thousand titles without lag
Scheduled3 min read By NT²
You added item two thousand. The scroll still works—but search should not mean loading your entire financial life into memory every time you type.
The second thousand items feel different
The first version of a vault is forgiving. Fifty credentials, a handful of bank records, a passport scan—you remember where things live.
Then years pass. Side projects, tax folders, hardware wallets, insurance renewals, API keys for clients you forgot you still had. The question stops being “where did I paste this?” and becomes “will the app still feel instant when I need one field under pressure?”
If the answer is no, people revert to screenshots, desktop files, and chat threads. Performance is not a benchmark brag—it is whether the safer habit survives growth.
Our first pass on this theme—Ten thousand items, still a vault—named the product boundary. This article goes one level deeper: how NT² is designed to keep list and search usable as the vault scales on your device.
Load the page, not the attic
A notes app or spreadsheet often treats “open the vault” as “render everything.” NT² treats the vault as a local database with structured rows:
| Habit | “Load everything” path | Paged vault path |
|---|---|---|
| Open list | Memory grows with every item you ever saved | Paged list — one screen of rows at a time |
| Search | Scan every title in JavaScript | Full-text search on titles in SQLite — results without loading full payloads |
| Open item | Decrypt only when you tap | Decrypt one record when you need it |
| Sensitive payload | Mixed with list UI | Encrypted blob stays separate from list metadata |
| Offline | Depends on sync finishing | Local-first — index lives on device in OPFS-backed storage |
You are not asking the UI to hold ten thousand decrypted secrets in RAM to find one IBAN.
Why structure helps search
Categories are not cosmetic. A Credential row searches differently from a Document row because the fields mean something:
- Bank items expose institution and account labels—not paragraph three of a memo.
- Document items carry issuer and expiry in predictable places.
- Crypto items keep mnemonics masked until copy time.
That shape feeds search and filters. “Stripe production key” is a title and a template—not a needle in a long note.
NT² also keeps attachments as encrypted blobs with metadata in SQLite. List and search stay about what you need to find; heavy ciphertext loads when you open the item.
Pre-launch honesty
NT² Vault is in active development and not open to the public yet. Counts and limits may change before launch; this article describes design intent—local indexing, paged reads, search without loading the whole vault—not a benchmark sheet.
If you are evaluating whether a structured vault can replace your “digital attic,” the question worth asking is simple: does finding one record stay calm at scale? That is what we are optimizing for.
Learn more
- First-pass growth story: Ten thousand items, still a vault
- Category education: Not another password manager login
- Product pillars: nt2.me/about
- Follow the blog: RSS feed
When NT² launches at se.nt2.me, year ten of your vault should still start with search—not with scrolling until your thumb gives up.
Last updated 2026-11-13
Related stories
- Ten thousand items, still a vault
2 min read
- New Ledger, same old Notes mistake
2 min read
- Consulate with no signal—where is your passport?
2 min read