What is DaedalMap?
DaedalMap is a maintained geographic evidence layer with several ways to use it.
Explore is for map discovery. Research is for bounded, source-backed analysis. Ops is for fresh evidence and live watch context. They read from the same maintained pack layer.
Is DaedalMap open source?
The core engine and schema direction are open. The paid layer is not ownership of public data; it is the maintained operating layer around QA, packaging, freshness, hosted convenience, and support.
What do I get without paying?
The public app, public pack catalog, docs, source map, and visible examples show how the map-first query model works and what evidence DaedalMap maintains.
What is a pack?
A pack is a maintained release unit for geographic evidence. It groups source data, metadata, provenance, coverage, licensing, and runtime behavior so the evidence can be explored, analyzed, monitored, or called from tools.
Can I make my own pack?
Yes. A source pack should document its source, methodology,
coverage, update pattern, license, caveats, and
loc_id alignment before it becomes part of the
maintained layer.
Can I run DaedalMap myself?
Yes. Publicly, there are two paths: use it online or install it yourself.
If you install it yourself, you can either use the packaged local runtime or the GitHub and manual setup path.
Why does the site talk so much about sources?
Because source-backed answers need a visible trail. Users should know where the evidence came from, how current it is, what geography it covers, and where the limits are.
Should I use the hosted app or run it myself?
Use hosted if you want the fastest path in: open the app, start querying, no setup. It is the right default for demos, shared team access, and maintained convenience.
Install it yourself if you want the same engine on your own machine. The packaged local runtime is the easier install path. It works offline once packs are installed, keeps private data on your machine, and removes the hosted-query dependency.
Use the GitHub and manual path when you want deeper deployment control, private catalogs, or more technical customization.
The engine is the same either way. The difference is delivery, trust assumptions, and performance. See install it yourself to get started.
Is the hosted app the same as local use?
Same engine, different operating assumptions. Hosted mode optimizes for convenience and shared access. Installing it yourself optimizes for local control. The packaged local runtime is the easier install, while the GitHub and manual path gives deeper control.