STOP 01
Documents flow in. The engine addresses every passage as a byte-exact row —
handing row ids to the vector store and writing content rows to
.spdb files, the single source of truth.
STOP 02
A local agent ingests and retrieves against on-device .spdb storage — no server.
When the device fills up, SpeedyDb spills to a cloud instance for storage and retrieval.
A policy gate decides what leaves the device: sync everything, or keep sensitive files on-device.
STOP 03
The same engine drops into your app as a ~0.7 MB library — no browser quota to fight. The application (or its user) sets the storage budget; SpeedyDb keeps data within it, reserving model + index space first and evicting cloud-backed cold data before anything local-only.
STOP 04
One cloud-backed context, linked across your browser, your application, and other people. Access is scoped by a privacy policy — grant or restrict per user, or per group.
STOP 05
No process-resident cache — reads are served from the reclaimable OS page cache, and the binary is ~0.7 MB. So the memory budget stays free for the things that actually need it: local models, vector DBs, and your coding tools.
STOP 06 · LAST STOP
Drop a file or load a sample and watch it flow through the pipeline — all on-device. Local ingest is coming soon; this is the platform you'll test it on.