The Atlas Network is the answer to a question that came up twice: after building BBQ Atlas, then wanting to build a completely different atlas, why rebuild the whole map-and-entity stack from scratch? The network is the extracted engine — data models, the map renderer, the entity-page pipeline, and the SEO scaffolding — made multi-tenant so a new atlas is a configuration, not a rewrite.
Two atlases run on it today. BBQ Atlas — 135 venues and 27 pitmasters across four live city guides. The War Atlas — 3,680 battles across 812 wars, source-cited to open data. Different subjects, different data, the same engine underneath.
"The interesting thing about an atlas isn't any one map. It's that geography is a reusable lens — point the same engine at barbecue or at battles and it holds."
The stack is Next.js with server-rendered entity pages so every joint, dish, battle, and commander is a real crawlable URL. The platform is the durable asset; each atlas is an expression of it.