Trust

Built to be audited in place.

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

The deployment is yours, not a tenant in ours.

01 Self-hosted

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.

02 Residency

When we host, it stays in your jurisdiction

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.

03 Disconnected

No public hostname at all

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.

04 Isolation

Separate deployments, not row filters

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

Your data stays yours, in formats you can walk away with.

Roles

You are the controller

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.

Portability

Open formats, published schema

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.

Third-party data

What is licensed stays licensed

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 website

No analytics, no trackers

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

An AI system a regulator can read.

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.

01 Grounded

Cited evidence only

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.

02 No training on your data

Your corpus is not our corpus

Customer data is not used to train models and is not pooled across deployments. It stays inside the deployment that owns it.

03 Human in the loop

The system proposes

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.

04 Logged

Decisions survive the meeting

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.

EU AI ActWhere a deployment falls into a high-risk use, we provide the technical documentation, the description of the method, the known limitations and the logging the deployer needs for its own obligations. We do not claim the deployer's role, and we do not pretend the assessment goes away because the software is bought rather than built.
UncertaintyEvery operational value is labelled measured, computed or estimated, visibly, next to the number. Gaps in the evidence are shown as gaps. A model that hides its assumptions cannot be argued with, and one that cannot be argued with cannot be signed.

Export control

PHAROS is dual-use, and treated as such.

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.

End user and jurisdiction established first Role-gated, audited export inside the product Silent and public operating regimes Hash-chained decision log Air-gapped installation supported

The other three products are civil systems for administrations and operators and carry no such restriction.

Certification

What this page is, and what it is not.

What this page is

Architecture and policy

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.

What it is not

A certificate we do not hold

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

Found something wrong in one of our systems?

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.