Corxor AISOS
Structure is not invented.
It is arrived at.
A planet is round because nothing else survives its own mass. Orbits settle into resonance because nothing else stays. A prime holds because nothing divides it.
AISOS is a result of the same kind.
Where we are now
The endpoint was the beginning.
It is no longer the boundary.
Corxor began by making decisions at the place where a process acts. That work continues, and the systems already deployed keep getting more defensive as the layer beneath them grows — nothing running today stops running.
What changed is the scope. Endpoint protection is one component of the system now, not the shape of the company. The same decision layer belongs anywhere a machine has to judge something before a human can.
This is the direction the technology was already moving. We are building for where it arrives, not where it was — and doing it without breaking the ground underneath anyone who deployed early.
An operating system for judgement, and the cyber services and frameworks built around it.
The operating system
Security tools produce alerts.
An operating system produces decisions.
AISOS is the intelligence layer beneath every defender and every platform Corxor builds — one decision grammar that does not fragment as the instances multiply. It is the first of its kind, and it is still being written.
Where the value is
The asset is the data,
and what can be safely derived from it.
Every institution now holds more value in its data than in the systems that move it. Harnessing that value — grounding it, training on it, governing what may act on it, and keeping it inside the boundary that makes it worth anything — is the work we are most often asked for.
Ground truth before models
Knowing what your data actually says — labelled, reconciled and disputed — before anything is allowed to learn from it. Most failed model programmes failed here, quietly, months earlier.
Training inside the boundary
The corpus that makes a system accurate is the same corpus that makes it sensitive. Training runs in your region, your tenancy, or entirely inside your perimeter. It does not travel.
Derivation you can defend
A result is a measurement someone else could repeat, on a corpus we are willing to name, with the failures counted beside the successes.
Governed autonomy
What a model is permitted to act on, and how far, written down and enforced in the product — so the value can be harvested without handing over the judgement.
Evidence, not noise
How a decision reads.
Every AISOS instance speaks the same grammar: a case, a ledger of the loop, and a decision that carries the policy that bounded it.
The aperture is the human seat. Autonomy is bounded, and every step above is replayable.
Cyber services
Engaged directly, or not at all.
Assessment & Scanning
A controlled examination of your estate, under written scope.
Vulnerability Discovery
Adversarial review by the team that writes the defence.
AI Data & Model Services
Models trained on your ground truth, evaluated against your adversaries.
Bespoke Engagements
Defence built to constraints no product ships with.
Onboarding & Adaptation
The system is fitted to the institution before it is enforced.
Engineering Practice
Platforms and integration, held to the same standard.
Products
Instances of the system.
Cyber Defense AISOS
AISOS deployed where execution happens. Derived decisions, bounded autonomy, and a protection core built on the assumption that it is the first thing attacked.
Client Platforms
FastLocated, FactuurKompas and RackNav — platforms where the client's critical data is treated as the primary asset from the first design decision rather than protected at the end.
The security-critical platforms are not products. They are built for a single client, under contract, and are not listed anywhere.
Data sovereignty
Security that respects
where your data lives.
Behaviour is the evidence. Content never is. Defending a machine does not require pulling the person using it into somebody else's database.
Cloud
Multi-tenant, isolated per institution, operated by us.
Dedicated
Your own instance, your own region, no shared control plane.
Sovereign / On-premise
Inside your perimeter. Nothing leaves it — including the models.
Deployments
Operators who cannot afford to lose.
Two deployments already live: one in regulated bonded customs space, one on a factory floor. Delivery and the first period of operation are carried out by the team that builds the system.
Engineering series
We build AISOS in the open.
Engagement
There is nothing here to buy.
Engagement begins with a request, not a purchase. Every request is examined properly — the security of the institution on the other side of it becomes our reputation the moment we accept.
Every exchange is encrypted and leaves no trace beyond the matter it concerns.