Why a new data hub?
Tourism data is valuable, but often hard to use. We keep running into the same five problems in our projects.
Data silos
Today: Events, accommodation, tours and infrastructure live in separate systems. Anyone who wants to show everything on one website builds the connections themselves.
Our answer: One hub that brings all sources together and delivers them through consistent interfaces.
Interfaces as one-off projects
Today: Every new integration is a project of its own, with its own budget and its own maintenance.
Our answer: Connectors based on an open protocol, each running as its own container. A new source always follows the same pattern.
AI bolted on
Today: AI features often sit next to the data and know neither its origin nor its license.
Our answer: AI is part of the core: hybrid search, answers with citations and an MCP server through which AI agents use the data directly. A quality score is planned.
Duplicates
Today: The same business or event arrives from several sources, with conflicting details.
Our answer: One golden record per object. For every field we record which source it came from and which license applies.
Unknown AI visibility
Today: Nobody knows for sure whether and how offers appear in the answers of AI assistants.
Our answer: Structured, machine-readable delivery (JSON-LD, MCP) and planned AI visibility monitoring as a service.