Skip to content
Jigsaw HubMission Control
Mission Control · Build Brain

The build brain

The technical knowledge base behind the migration: how the data layer is sharded, how routes resolve, the stack underneath, and how the platform is tuned for answer engines.

113+Data shards
234 MBRaw venue data
24,428Venues migrated
74,000SEO routes
Knowledge base

Architecture snapshots

The venue corpus is split into 113+ shards so no single function ever loads the full data set, keeping us under the serverless memory ceiling.

Shards
113+
Raw data
234 MB total
Strategy
Lazy, per-route shard reads
Goal
Bypass Vercel / sandbox memory limits
data/
├─ shards/
│  ├─ venues-000.json
│  ├─ venues-001.json
│  └─ … venues-112.json  (234 MB raw)
└─ index/
   └─ shard-map.json     (city → shard lookup)