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.

Open the app Run your own version

Screenshot: app running with a pack loaded, map and data panel visible

Hosted access

Maintained convenience

Best for people who want more than the public demo without running the pipeline themselves.

Broader curated pack access
Maintained hosted convenience
Broader product access over time
A clearer path beyond the public demo

Coming soon.

Public app

Fastest way in

Best for first-time users who want to understand the engine and see the product working.

Hosted public web app
Starter or demo catalog
Map-first, chat-first exploration
No setup required

Open the app

Self-hosted

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

What you are paying for

Operational value

Source discovery and curation
Converter maintenance
Normalization and alignment
QA-tested releases and metadata
Freshness, packaging, and runtime access

Why pricing varies

Access and scope

Hosted demo 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 and ongoing maintenance is what becomes paid.

That means the important question isn't "which tier am I in?" it's "which access path fits what I need right now: public demo, maintained hosting, or personlized deployment?"