The Future of Geospatial Apps Without Servers
R2, edge compute, and static-first architecture—why TrueTopo bets on a serverless geospatial stack.
Most mapping platforms still run on traditional backends—Postgres, Redis, tile servers, API gateways. TrueTopo is built differently: static assets, edge Workers, R2, D1, KV. No always-on servers. No scaling events. No ops team.
The Architecture
Static-first: The app is a static PWA. HTML, CSS, JS, and pre-built bundles. Hosted on R2. Served via Cloudflare.
Workers for APIs: Gazetteer search, entitlements, Stripe checkout—all run as Workers. Scale to zero. Pay per request.
R2 for data: Tiles, catalogs, vector tiles, static JSON. S3-compatible. No egress fees for Cloudflare → user.
D1 for search: Gazetteer, structured queries. SQLite at the edge. No connection pooling. No cold-start penalty.
Why It Matters for Alaska
- Offline: Static + service worker = full app in the field. No backend required.
- Cost: Low traffic? Low cost. Viral spike? Workers scale. No reserved capacity.
- Latency: Edge = close to the user. Alaskans benefit from Cloudflare's global PoPs.
- Simplicity: One vendor (Cloudflare). One deployment pipeline. Fewer failure modes.
The Tradeoffs
We don't run complex ETL or heavy geospatial processing in Workers. That happens in build pipelines (GitHub Actions, scripts) and lands as static output in R2. The edge is for serving and light compute, not for crunching terabytes.
For a startup building the Alaska mapping standard, that's the right trade. We move fast, keep costs predictable, and deliver a field-ready app. When we need more—we'll add it. But we won't add it until we need it.