Use the free engine
Installing it yourself is where the open-core promise becomes concrete: run the engine yourself, choose your own data, and control the runtime assumptions.
Installing it yourself means running the same engine on your own machine or network. This page focuses on the public GitHub/manual path and the controlled local research runtime.
Installing it yourself is where the open-core promise becomes concrete: run the engine yourself, choose your own data, and control the runtime assumptions.
You are not limited to the hosted catalog. The manual install path is also where private or custom sources fit.
GitHub/manual setup is the raw technical path. The local runtime is the guided research-oriented path with easier local control and pack handling.
Publicly, DaedalMap has two paths: use it online or install it yourself. If you install it yourself, the public GitHub path is the raw technical route. The packaged local runtime is the guided research-oriented route.
Some people want the hosted app because it is easy. Others need their own runtime because the work is sensitive, custom, offline, performance-sensitive, or tied to local files and policies. DaedalMap supports both without pretending the local runtime and the full GitHub/manual path are the same use case.
The engine is open. The pack layer is governed by upstream source terms and by DaedalMap's maintained distribution lanes. GitHub/manual setup is the open technical path. The local runtime is the controlled handoff for research and deeper local work, not a promise that every maintained pack becomes a public bulk download.