Learning level
100/100
Workbook Storage Architecture
VauSheet · 81–100 · Advanced Architecture & SupportProduct version
1.0.1
Guide status
Advanced
Sections
4
Workbook Storage Architecture
Implementation-backedUnderstand the production VauSheet split between browser checkpoints, Supabase control metadata and AWS S3 workbook documents.
What this guide covers
Browser layer
Supabase control plane
AWS S3 document storage
Why the split exists
Quick facts
BrowserCheckpoint / pending edits
SupabaseAuth · metadata · version · lock · realtime
S3Compressed workbook document
SyncVersioned semantic merge
Documentation rule: this VauSheet section describes the current implemented product behavior. It avoids claiming full Microsoft Excel parity or live-cursor collaboration where the current build does not provide it.
01
Browser layer
The browser holds the interactive workbook state and a local synchronization checkpoint so editing remains responsive and recoverable without writing to the network after every keystroke.
02
Supabase control plane
Supabase handles authentication and workbook metadata/control state such as ownership, versioning, synchronization locks and realtime version-change signaling.
03
AWS S3 document storage
The full workbook document is stored as compressed JSON in object storage rather than expanding every spreadsheet cell into a relational database row.
04
Why the split exists
The architecture keeps metadata/queryable control state small in Postgres while allowing the workbook document to scale as an object. Synchronization coordinates both layers so a successful save advances the workbook version together with the stored document.
Updated 2 Sep 2026VauSheet 1.0.1