On your infrastructure
Every product ships as something you can host yourself, on your servers or your cloud account, with your own identity provider in front of it.
Trust
These products advise decisions taken by administrations and operators of critical infrastructure. Everything on this page describes how they are built and how we operate, and every statement can be inspected inside a deployment rather than taken on our word.
Deployment and residency
Every product ships as something you can host yourself, on your servers or your cloud account, with your own identity provider in front of it.
Where a customer asks us to operate the deployment, it runs in the region that customer requires and the data does not leave it. Our own hosting is in the European Union, and we stand up a deployment elsewhere when the rules a buyer answers to say elsewhere.
An installation can be fully air-gapped, with updates delivered as signed images and nothing reaching back to us. PHAROS is built for exactly this buyer.
One customer's territory does not physically exist inside another customer's database. Isolation is a deployment boundary, not a query somebody could get wrong.
Data protection
In a product deployment the customer is the data controller and Cortex Prime is a processor acting on instruction. A data processing agreement is issued with the contract, and the sub-processors involved in that specific deployment are listed in it by name.
Everything the layer computes leaves in open geospatial and tabular formats with a documented schema, straight into your own systems. There is no export fee and no proprietary container.
Open European sources come with their own terms and we pass them through unchanged. Layers a customer licenses from somebody else remain that supplier's, and are never redistributed through us.
This site sets no cookies, runs no analytics and makes no third-party request. Fonts are served from our own domain. The only records are ordinary web server logs, described in the privacy notice.
AI governance
These products advise decisions taken by public authorities and operators of critical infrastructure. That places obligations on the deployer, so the architecture is built to satisfy them rather than to be retrofitted later.
Reasoning is retrieval over the customer's own model. An answer that cannot point at the record behind it is not returned as an answer.
Customer data is not used to train models and is not pooled across deployments. It stays inside the deployment that owns it.
Scores, layouts and schedules are proposals with their assumptions on screen. No product takes an automated action on a physical system without a person authorising it.
What was proposed, on what evidence, under which assumptions and who accepted it is written to an append-only log, and exported for an audit as a dossier.
Export control
PHAROS plans maritime sensor barriers, which makes it dual-use software subject to export control review. Enquiries are handled accordingly: we establish the end user and the jurisdiction before a technical conversation goes any further, and we decline the ones we cannot place.
The other three products are civil systems for administrations and operators and carry no such restriction.
Certification
Every statement here describes how the products are built and how we operate, and every one of them can be inspected in a deployment: the isolation boundary, the logs, the export path, the provenance on each value.
Where a procurement requires a certification or an accreditation we do not hold, we say so in writing rather than around it, and we tell you what we can evidence instead. We would rather lose a tender than be discovered halfway through one.
Report a problem
Write to us with the detail and how to reproduce it. We acknowledge inside two working days, we do not send legal threats to people who report vulnerabilities in good faith, and we tell you when the fix has shipped.
For a compliance questionnaire, a data processing agreement or a security annex, use the same address and name the document you need.