SCROLL TO CONTINUE

STOP 01

The Context Engine

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.

  1. 01 · Ingest document → engine
  2. 02 · Index engine → vector store
  3. 03 · Persist engine → .spdb files

STOP 02

Runs in the browser

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.

Policy
browser agent · localhost
agent · indexing
on-device .spdb—
STORAGE FULL · SPILLING TO CLOUD
policy gate
spill →
← retrieval
CLOUD INSTANCE
storage · retrieval
  1. 01 · Local agent + on-device .spdb
  2. 02 · Overflow device storage fills
  3. 03 · Spill policy-gated → cloud

STOP 03

Embedded in applications

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.

Storage size
Browser
bounded by the device
~2 GB · OS quota
Application SpeedyDb ~0.7 MB
you set the budget
budget 16 GB · 95% free
reserve model + index · evict cloud-backed cold · never drop local-only
  1. 01 · Embed ~0.7 MB library
  2. 02 · Configure you set the size
  3. 03 · Fit budget-managed, no forced spill

STOP 04

Shared context

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.

Scope by
  1. 01 · Link browser + application
  2. 02 · Invite other users join
  3. 03 · Scope grant / restrict by policy