Use the free engine
Self-hosting is where the open-core promise becomes concrete: run the engine yourself, choose your own data, and control the runtime assumptions.
Docs / Self-Host
Run your own
DaedalMap deployment.
Self-hosting means using the open repo, running your own runtime, and choosing your own packs and local data paths.
Build your own pack tree
You are not limited to the hosted catalog. The self-host path is also where private or custom sources fit.
Technical path first
The self-host path is developer-oriented. GitHub and manual runtime setup are the entry point.
GitHub and manual setup
- Download the public repo
- Run your own app/runtime stack
- Use local files or your own compatible packs
- Best for technical users comfortable with setup
Local control
- Choose the packs and local files you want to run
- Keep private data on your own machine or network
- Run offline once the required data is installed
- Avoid hosted-query constraints when local control matters more
Current self-host path
The practical path is the public GitHub repository plus direct runtime setup. That keeps the engine open and usable for people who want control, private deployment, or a local-first workflow.
Why self-hosting matters
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 they are the same use case.