Open the app
See it working
The hosted app is the fastest way to understand the system and what map-first geographic queries look like in practice.
DaedalMap is a map-first geographic query engine. Maintained packs across disasters, demographics, economics, climate, and risk. Cross-domain joins without building the pipeline first.
Open the app
The hosted app is the fastest way to understand the system and what map-first geographic queries look like in practice.
Run it yourself
The engine is open. Self-host it, inspect the pack model, and work with your own data without cloud dependency.
Coming soon
GitHub is the install path today. Join the list for updates on the launcher and easier local setup.
Move across disasters, population, economics, climate, and risk in one queryable system.
View packsBuild a named corpus from your published packs, load it in the app, and ask comparison, synthesis, and trend questions against that data.
Learn more7 disaster categories, UN development indicators for 190+ countries, global currency and economic data. 1M+ earthquake events back to 2150 BC. 13K+ storms tracked since 1842.
View source mapThe engine is open, the pack model is visible, and any data can be made compatible for the same runtime.
View self-hostAsk location-based questions across disasters, demographics, economics, and risk. Get answers on a map.
A bounded analytical workspace for comparing, summarizing, and investigating data from a defined packs corpus.
Live event monitoring with a focused operational view for active conditions and hazard response.
Open engine
DaedalMap keeps the engine open and the pack structure legible. The hosted app is the easiest path in, but it is not the only legitimate way to use the system.
View packs docsBuild on it
The point is not a one-off demo. The point is a geographic engine with clear data pipelines and a schema model that can absorb new datasets without becoming a different product each time.
View GitHub
Why it exists
Public geographic data is often technically available but operationally unusable. The problem is not just access. It is fragmentation across portals, formats, geographies, and domains.
DaedalMap exists to make that maze navigable enough that someone can ask a location-based question, keep context, load the right corpus, and continue into deeper analysis without rebuilding the workflow from scratch.