Maintained convenience
Broader curated pack access, account-backed Research mode, and maintained hosted convenience.
- Broader curated pack access
- Account-backed Research corpora
- Maintained hosted convenience
- Broader product access over time
Pricing
Open engine.
Paid operating layer.
DaedalMap is not priced as if you are buying ownership of public data. The engine stays open. The paid value is maintained packs, hosted convenience, broader access, and support.
Screenshot: app running with a pack loaded, map and data panel visible
Fastest way in
Open the app and start querying with the starter catalog. No setup required.
- Hosted public web app
- Starter pack catalog
- Map-first, chat-first exploration
- No account required
Control your own runtime
Best for technical users who want to run the open engine themselves and adapt their own data.
- Use the open GitHub repo
- Build your own compatible pack tree
- Keep control over runtime and storage
- Best for developer-oriented workflows today
Operational value
- Source discovery and curation
- Converter maintenance
- Normalization and alignment
- QA-tested releases and metadata
- Freshness, packaging, and runtime access
Access and scope
- Hosted app versus broader account access
- Pack scope and catalog breadth
- Refresh cadence and support level
- Local or self-hosted deployment needs
- Onboarding and custom enablement
Current position
The exact packaging will evolve, but the boundary is always stable: the engine and schemas stay open, while the maintained operating layer is what becomes paid.
The useful question is not which tier but which access path fits right now: the public app, maintained hosted access, or a local or self-hosted deployment.