Your assets are horizontal by nature. Your organisation is vertical by design. So the asset's data has no owner.
From the apps your teams use down to the European cloud it runs on. Start with the layer you need: each one works on its own, and together they make one platform.
App names are working titles.
Retrofits, firmware updates, spare parts, new owners - each one recorded somewhere else. With the real configuration of every unit in the field, spare parts, upgrades and service contracts are sold against what is actually out there - not against a guess.
Batch, supplier, firmware, field changes - one query, not four systems. Warranty claims, recalls and regulatory demands are answered from one record with its full history: what was installed, when it changed and who approved it.
Right asset, right procedure, right person. Manuals and expert notes are bound to the individual machine, so Hubbiot AI answers from the version that matches what is in front of the technician - and the expertise of a retiring engineer stays with the asset.
Digital transformation rarely fails for lack of tools. It fails because every tool holds its own version of the asset, and AI inherits the same confusion.
Most questions about an asset are asked by systems, not people. The ERP needs the installed configuration before it quotes a spare part. The service system needs the history before it plans a visit. Each gets one answer - with the same access rules as everyone else.
Agents that plan maintenance, answer a customer or draft a quote connect to the twin over MCP. Access decides what each may read, every call is audited, and every answer cites the record. On your servers.
Keep the systems you run today. The twin sits underneath them, so your ERP, your service system and your AI agents all work from the same record of the asset.
Sovereignty and portability are not features we plan to add later. They are architectural decisions made from day one. On your premises, in your cloud, in Hubbiot SaaS or a hybrid of them, and the data stays where it runs.
Maximum control and full sovereignty. Comes with its own dedicated AI Server, delivered configured and ready to use, so your AI runs on site and neither your data nor your questions leave your infrastructure. Air-gapped if your environment requires it.
AWS, Azure or GCP - runs inside your own accounts. Your data stays in your cloud, never sent to Hubbiot.
Some parts on your premises, others in Hubbiot SaaS, working as one twin. Hubbiot AB maintains and monitors the on-site instances remotely, and your data never leaves your premises.
Hosted and run by us on our own European infrastructure - a managed service without giving up sovereignty.
Connected products must make their data accessible to the user - who may share it with a service partner of their choice. The OEMs that benefit already know what each machine is and who may see what.
Source: Regulation (EU) 2023/2854, Art. 3(1)
Early warning within 24 hours of an actively exploited vulnerability - for products already in the field, including ones past support. If the answer lives in four systems, 24 hours is not much time.
Source: CRA Article 14
Instructions may be supplied digitally if they remain accessible for at least ten years - longer than most portals and file formats last. And they must match the machine as it is today.
Source: Regulation (EU) 2023/1230, Art. 10(7)
Identity, composition, state of health and dismantling information linked to one physical battery for its whole life. A Digital Twin requirement in all but name.
Source: Regulation (EU) 2023/1542
The asset, which is horizontal by nature, has no natural home in an organisation that is vertical by design. Hubbiot gives it one: a single data backbone, and the business value it creates.
"What exactly is installed in machine SN-4471, and who may service it?"
Someone spends days reconciling - and still answers with a caveat.
One answer - with every change, document and permission behind it.
One platform, many sectors - and inside every customer it spans all verticals. Wherever a machine outlives the systems that describe it, the twin has to be the one record that does not.

Configuration history per vehicle, recalls by batch

Sovereign data, full lineage, decades of service life

Installed base, spare parts and field service

Distributed sites, long horizons, strict compliance

Fleets of machines that change task and firmware

Traceability per unit, audit-ready by default
Every site and every asset reporting into one twin. Open any serial number to see what is inside it now, or rewind to any day in its life.


Models with versions, individuals with their real composition, every event recorded as a fact in one graph.
AccessEach party sees exactly its slice - manufacturer, dealer, operator, service partner, regulator - without bespoke role engineering.
KnowledgeManuals, specs and procedures bound to the right version of the right machine, so Hubbiot AI answers from the correct document.
One way in, then the twin grows across your organisation as the value shows. Every step builds on the same record.
A walkthrough of Hubbiot Heim on sample data, shaped around your own questions.
One team and one fleet, with your own systems connected and goals agreed up front.
More teams and divisions on the same twin, each adding the apps it needs.
Every division and every vertical, run where it fits best: on site, in Hubbiot SaaS or both.
Or start from the database: TvennDB first, with Hubbiot Heim and the apps on top later.