Is DaedalMap open source?
The core engine and runtime direction are open. The paid layer is not ownership of public data; it is the maintained operating layer around packs, freshness, packaging, hosted convenience, and support.
What do I get without paying?
The public app and public docs are meant to let people understand the system, try the core workflow, and see how the map-first query model works before they commit to anything.
What is a pack?
A pack is the release unit for data. Instead of treating the repo as the product, DaedalMap treats maintained, versioned data packages as the thing that gets installed, promoted, or made available.
Can I make my own pack?
Yes. That workflow is still being tightened, but the direction is explicit: contributors should be able to build a source pack, document it clearly, run it through QA, and eventually submit it or maintain it over time.
Can I run DaedalMap myself?
Yes. Right now that means using the open GitHub repository and doing your own setup. Over time, the local path should get simpler through better packaged installs and a clearer native-app style workflow.
Why does the site talk so much about sources?
Because trust depends on source clarity. People need to know what families are in the system, where they came from, how current they are, and what is still stronger or weaker today.
Is the hosted app the same as local use?
It is the same product family, but not the same operating assumption. Hosted mode optimizes for convenience and shared access. Local or self-hosted use optimizes for control, privacy, and deployment flexibility.