Open
Free engine
The runtime and schema model stay legible so people can understand the system and run it beyond the hosted demo.
Docs / How It Works
One engine,
multiple trust models.
DaedalMap is built so the same core runtime can support a public hosted map, a more capable account-backed experience, local analyst workflows, and self-hosted deployments.
Maintained
Pack operating layer
The paid value is the work required to turn messy public data into maintained, queryable, release-ready packs.
Path
Demo to self-host
The public app is the fastest way in, but the same product model should extend into local and self-hosted use.
Open engine, maintained operating layer
The engine and schema model are meant to stay understandable and inspectable. The maintained layer is the operational work that turns public or partner source material into coherent, queryable releases.
Map-first querying
The product is not a generic dashboard shell and not a pure GIS desktop replacement. The user can ask a GIS question, zoom up and down through location hierarchies, and keep context while the runtime selects from fixed data packs you choose.
Runtime catalogs
A runtime catalog determines what the current shell can see. That means the same underlying engine can expose a public demo surface, a broader hosted catalog, or a private local catalog without changing the basic query model.
Why the split matters
This keeps the product honest. Hosted convenience, maintained releases, support, and broader access are the paid layer. The value is not a fictional ownership claim over raw public data. The value is the maintained system around it.