Now
GitHub and manual setup
- Download the public repo
- Run your own app/runtime stack
- Use local files or your own compatible pack tree
- Best for technical users comfortable with setup
Docs / Self-Host
Run your own
DaedalMap deployment.
Today, self-hosting means using the open repo and setting up your own runtime. Later, this path should become easier through native app delivery and clearer packaged installs.
Later
Native local install
- Simpler packaged local install
- Clearer pack sync and workspace behavior
- Less repo setup overhead
- Better path for analysts who want control without full developer setup
Current self-host path
Right now, the practical path is to use the public GitHub repository and follow the runtime setup directly. 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 want their own runtime because the work is sensitive, custom, offline, or deeply tied to local files and policies. DaedalMap should support both without pretending they are the same use case.
Where this goes next
In the future, this path should become much friendlier: native installs, clearer pack syncing, and better local workspace behavior. The open repo is the current path, not the final form.