Trust
How our systems are installed, controlled and supported.
Plain answers, product by product. Where a condition depends on the product, the configuration or the contract, this page says so.
Installation and hosting
Where the system runs.
It depends on the productOur products are separate systems. What is true for one is stated for that one, below and on its own page.
KraftSync TransitA customer instance runs on the operator's own server. Sign-in is required and the data is held only there.
PHAROSDesigned for self-hosted and disconnected installation, with one deployment per customer.
CityTwin and TerraScanHosting is agreed per deployment: on infrastructure the customer chooses, or operated by us.
When we hostOur own hosting is in the European Union. Another region is a matter for the contract.
Dedicated solutionsInstallation and hosting are defined in the project, with the customer.
Access, protection and export
Who can see the data, and how it leaves.
AccessCustomer deployments require sign-in. Roles and who holds them are set by the customer.
Roles under data protection lawIn a deployment the customer decides why and how personal data is processed, and we act on the customer's instructions. The data processing agreement is part of the contract and names the suppliers involved in that deployment.
ExportHow data is exported depends on the product. CityTwin exports the city model as open JSON against a published schema and its layers as GeoJSON. For the other products the export formats are stated in the contract.
Third-party dataOpen sources keep their own terms. Layers a customer licenses from another supplier remain that supplier's.
TrainingWe do not use customer data to train models.
External providers and models
Which AI is used, and where.
It differs by productNot every product uses a generative model, and none is tied to a single supplier.
CityTwinThe question-answering layer works with interchangeable model providers. The default configuration uses a European provider. A locally hosted model can be used instead.
TerraScanScores are computed by the pipeline, not by a language model. Report text can be generated with an external language model or with the built-in deterministic generator.
KraftSync TransitAlerts and recommendations come from a rule engine.
PHAROSResults come from a calculation engine. It calls no external service. The engine is implemented; the planner interface is a prototype on synthetic data.
In your deploymentWhich provider and which model are used, and what is sent to them, is written into the contract before anything goes live.
Control of AI actions
The system proposes. A person decides.
Proposals, not actionsScores, layouts, schedules and answers are proposals. Their assumptions are shown with them.
KraftSync TransitThe rule engine recommends and the dispatcher decides. The platform executes nothing by itself.
PHAROSA command to a node passes through a role-gated queue and counts only when the node acknowledges it.
CityTwinAnswers carry their sources, their assumptions, the gaps in the data and a confidence level, so they can be checked before use.
Labelled valuesMarking every operational value as measured, computed or estimated, at field level, is implemented in KraftSync Transit. It is not a common mechanism of the four products. The three kinds of value
In the other productsCityTwin records, for each element of the city model, its sources, a confidence level and whether it is an assumption. Sources and method. TerraScan shows the indicators behind a score with their shares, labels each report as generated on real data or on indicative data, and gives a confidence level that follows from it. In its public demonstration only the fire module runs on real data. What is real, module by module. PHAROS keeps the nominal range next to the terrain-masked footprint and states the assumptions of each result. The metric and its assumptions
RegulationWhether a particular use falls under a regulated category depends on that use. We do not state a classification here. We provide the description of the method, the known limits and the records the customer needs for its own assessment.
Export control
PHAROS is dual-use, and treated as such.
Review firstPHAROS plans maritime sensor barriers, which makes it dual-use software subject to export control review. We establish the end user and the jurisdiction before a technical conversation goes further, and we decline the enquiries we cannot place.
The other productsCityTwin, TerraScan and KraftSync Transit are civil systems for administrations and operators.
Support and reporting problems
How to reach us when something is wrong.
SupportSupport terms, response times and update arrangements are set in the contract for each deployment. We do not publish a general guarantee here.
Reporting a problemWrite to [email protected] with the detail and how to reproduce it. We do not send legal threats to people who report vulnerabilities in good faith, and we tell you when the fix has shipped.
DocumentsFor a data processing agreement, a security annex or a compliance questionnaire, use the same address and name the document you need.
CertificationsWe hold no certification or accreditation that we could cite here. Where a procurement requires one, we say so in writing and tell you what we can show instead.
This websiteThe site sets no advertising or analytics cookies. If you press the RO button, the page is translated by Google Translate, which loads a script from Google and stores a language cookie. Until then the site makes no third-party request. Server logs are described in the privacy notice.