Deployment Architecture

Overview

TrueTopo runs on Cloudflare R2 (storage), Workers (API and auth), and CDN (edge caching). There are no long-lived application servers.

R2 buckets

Bucket / purpose	Domain / use
app-truetopo	app.truetopo.com (PWA build)
truetopo-site	www.truetopo.com (marketing)
data-truetopo	data.truetopo.com (datasets)
truetopo-tiles	tiles.truetopo.com (map tiles)
truetopo-layers	Vector layers / PMTiles
truetopo-docs	docs.truetopo.com (this site)
truetopo-api	api.truetopo.com (API surface)
truetopo-legal	legal.truetopo.com
truetopo-status	status.truetopo.com
truetopo-id	id.truetopo.com (identity)

Example bucket layout (data / tiles)

data-truetopo (data.truetopo.com):

• gazetteer/ — GeoJSON or FlatGeobuf for names
• trails/ — Access and trail datasets
• hydro/ — Hydrology
• catalog.json — Dataset index and metadata

truetopo-tiles (tiles.truetopo.com):

• gazetteer/ — PMTiles or z/x/y for gazetteer
• land/ — Ownership tiles
• trails/ — Trail and access tiles
• terrain/ — Elevation, hillshade

Workers

Workers handle:

• API routing — Proxying or serving API responses (e.g. gazetteer, access routes)
• Authentication — Session and JWT validation
• Payments — Stripe webhooks and customer portal redirects

Edge caching

R2 public buckets are served through Cloudflare’s CDN. Static assets (tiles, JSON, app shell) are cached at the edge for low latency worldwide.