Hosted
Fastest path in
- Open the app and start querying immediately
- Best for demos, shared access, and maintained convenience
- Runtime controls what is installed and visible
- Good default when convenience matters more than control
Docs / Hosted vs Local
Same engine,
different operating assumptions.
Hosted, local, and self-hosted use should share one runtime logic, but they do not share the same trust, storage, or operational assumptions.
Local / Self-hosted
More control, more responsibility
- Use local files or privately installed packs
- Better for sensitive workflows, custom stacks, or offline needs
- More room for private catalogs and deployment-specific policies
- Best when control matters more than hosted simplicity
Hosted mode
Hosted mode is the easiest way to use DaedalMap. It is where maintained pack delivery, account access, and product onboarding should feel smoothest.
Local analyst mode
Local mode should keep the same mental model while moving execution and data control closer to the user. That includes local files, local runtimes, and more explicit workspace persistence.
Self-hosted deployments
Self-hosted use extends the same ideas to partner or institutional environments that need private operation, internal catalogs, or contract-specific pack access.