Data Platform
An independent data platform that grows with you.
Model Atlas, Data Atlas and Event Atlas together form your data fabric. Every system is integrated with low-code, through its own model — not mapped after the fact.
Model Atlas — active metadata management instead of an archive.
A central model registry captures your systems comprehensively, makes the relationships between them visible as a knowledge graph and detects new data sources automatically — such as a new sensor in the Event Atlas, including a suggestion for the matching model.
Data Atlas & Event Atlas — robust integration infrastructure instead of point-to-point connections.
New or existing databases and files simply plug in: you describe the source, and the Data Atlas handles transformation and delivers the data via open standards such as REST, OData and OGC SensorThings API (STA). The Event Atlas detects new sensors and event sources automatically and records only relevant changes based on clear rules, instead of logging every raw value.
Open code — product independence instead of vendor lock-in.
The code is built on the long-established standards EMF and OSGi rather than proprietary in-house development, and belongs to no one exclusively. Because your data is described independently of any single vendor as a result, modern AI systems can work with it directly and reliably, too.
All data visible, analysable and adaptable — straightforward, in a modern interface.
The integrated analytics interface Eclipse Daanse accesses the data provided via Data Atlas and Event Atlas directly, structured according to the models stored in the Model Atlas — without having to purchase and integrate a separate analytics tool. This turns a well-structured data foundation into a tool that specialist staff and decision-makers actually use in their day-to-day work.
Compatible with what you already have.
Standards & interfaces
- Geodata via GeoJSON — usable in common geographic information systems and geoportals.
- IoT and sensor data via SensorThings API (STA) — connects to existing smart city infrastructure and specialist administrative systems.
- Mature REST and OData interfaces for connecting business applications, dashboards and analytics tools.
- Open data catalogues compliant with DCAT-AP 3.0.
Organisation & operations
- Multi-tenancy from the ground up — multiple agencies, departments or municipalities on the same platform, each with its own access rights.
- Staged approval workflows (draft → reviewed → approved) for controlled, GDPR-aligned access to sensitive data — the recorded details can be reused directly for your records of processing activities (Art. 30 GDPR).
- Flexible deployment — on-premises, hosted or hybrid, depending on your infrastructure.
What sets us apart.
Model Atlas, Data Atlas and Event Atlas share common models, which makes the relationships between your systems visible — not as a separate module bolted on later, but as part of the architecture itself. As a result, you know not only where every piece of information comes from, but also how your systems relate to each other, without having to run or buy an additional tool. Plus, there’s our service: we set up the platform, adapt it and support it.
We develop open source.
Not as a concession, but out of conviction: what is created with public money should belong to everyone — not to a corporation. In the spirit of Public Money, Public Code, the code itself belongs to no one exclusively. More and more organisations now explicitly require this, because it gives them greater IT security, interoperability and product independence. We are part of the Eclipse Foundation and align our architecture with the technical guideline of the German Federal Office for Information Security (BSI) on security requirements for urban data platforms (TR-03187). For you, this means a sovereign choice that holds regardless of us as a company.
Ready for what comes next.
The data platform is model-driven: new requirements extend the model instead of forcing a rebuild of the platform — protecting your investment even against requirements nobody knows about today. In keeping with the once-only principle: structures are described once and reused everywhere — data never has to be captured twice. This keeps your system up to date, even as technologies or organisational frameworks change in the future.
Book a no-obligation consultation: info@datainmotion.com · Technical documentation on GitHub