Aviation & critical infrastructure security

New detection capability on the scanners you already own.

When a new threat appears, adding detection for it means waiting on your equipment manufacturer's release cycle — if they choose to build it at all. Sentriko lets you deploy third-party detection algorithms to your existing screening fleet, without replacing hardware and without touching your certified detection.

Request an Agility Audit See how it works
David Pilgrim, founder of Sentriko

Built by David Pilgrim — thirty years in screening and detection, including senior roles at Smiths Detection and Rapiscan Systems.

Sentriko — capability catalogue
Wildlife & ivoryThird-party developerDeployed
Lithium-ion cellsThird-party developerAvailable
Biosecurity — organicsThird-party developerAvailable
Currency & bulk cashThird-party developerAvailable
Deploy Wildlife & ivory → Terminal 3, integrations 4–7 DEPLOY

Illustrative interface. Names are example categories, not listings.

600,000+ Screening machines already in service worldwide — the installed base Sentriko deploys onto
Non-mandatedYour certified detection is untouched
Offline-capableScreening and audit run with no network
Vendor-neutralBuilt across the major equipment makers
The problem

The agility gap

Threats change at the speed of software. Screening capability changes at the speed of hardware procurement. That gap is where the risk sits — and it is structural, not anyone's fault.

Capability arrives late

A new threat is identified. Detection for it means a change request into a manufacturer's roadmap, then a validated release, then a fleet rollout. Operators describe a multi-quarter process at best.

Measured in release cycles, not weeks

Some capability never arrives

Wildlife trafficking. Biosecurity. Lithium-ion cells in the wrong place. Real screening problems, each a narrow market — and manufacturers reasonably decline to build detection with no fleet-wide business case behind it.

Niche threats have no OEM roadmap

Experience walks out of the door

Screening officer turnover runs high across the industry. Every departure takes interpretation skill with it, and automated detection is the only part of the capability that doesn't resign.

Detection software doesn't have a notice period

We publish a cost-of-latency model covering throughput, penalty exposure and staffing that quantifies this for a given site. It's built on operator interviews and public data and is available on request — we'd rather walk you through the assumptions than put a headline number on a web page.

How it works

An open marketplace, on the equipment you already have

Sentriko sits alongside your existing screening equipment. It reads the image formats the machines already produce, runs additional detection models against them, and gives the security team one place to choose, deploy and audit that capability.

01 — CONNECT

Read what the machines already output

Our ingestion layer converts proprietary manufacturer image formats into a common representation, so one algorithm can run across equipment from different makers.

02 — CHOOSE

Pick capability from a catalogue

Security leadership browses available detection models, sees what each does and what it costs, and selects what the site actually needs.

03 — DEPLOY

Push to the fleet, with a record

Deploy to chosen equipment from one console. Every deployment and every detection event is written to a tamper-evident local ledger.

Architecture

Built for people who can't take chances

The first four questions every security director asks. Here are the answers before you have to ask them.

Does this affect my certification?

No. Your equipment manufacturer's own detection is certified and stays exactly as it is — we do not modify, replace or interfere with it. The marketplace targets supplementary, non-mandated detection: threat types that sit outside the certified detection standard. That distinction is deliberate and it is the foundation of the whole design.

Where does my screening data go?

Nowhere. Detection runs on an edge node inside your environment. Screening images do not leave your network. The system operates fully offline — detection, logging and audit all continue with no connectivity — and synchronises catalogue and licensing information to a control plane only when a connection is available and permitted.

Can I prove what happened?

Yes. Every deployment, configuration change and detection event is written to a permissioned, tamper-evident ledger held locally at each site. It runs offline and re-anchors when the site reconnects. The audit record is yours, held on your infrastructure, and it survives an argument.

Is there a language model in the detection path?

No. Detection models run under a standard inference runtime with deterministic, reproducible behaviour. There is no generative model anywhere in the decision path. We think this matters enough to state plainly rather than leave you to work out.

Two sides

A marketplace needs both

Operators want capability that already exists. Developers want customers who already have the integration. Someone has to solve both ends, and that is the work we are doing.

For operators

Security directors

  • Add detection for threats specific to your route network or region
  • Keep your existing equipment and your existing certification
  • One console across equipment from different manufacturers
  • Priced per integration per year, not per capital purchase
Request an Agility Audit →

For algorithm developers

AI and detection labs

  • Build the integration once, reach equipment from multiple manufacturers
  • Standard inference runtime — bring the model you already have
  • A route to airport buyers without a multi-year enterprise sales cycle
  • A deliberately low platform fee, because supply is what the market needs first
Founding developer programme. We are funding the first algorithms onto the platform directly. If you build detection for a threat type the major manufacturers won't touch, we want to talk.

Get SDK early access →

Who is building this

Thirty years inside the problem

David Pilgrim

David Pilgrim

Founder, CEO & Principal Engineer

Three decades in screening, detection and critical infrastructure systems, including senior product and business roles at Smiths Detection and Rapiscan Systems. He has sold, specified and delivered screening programmes across Asia Pacific, Europe and the Middle East, and holds an MSc in Engineering Management from the University of East London.

Sentriko exists because the same conversation kept happening. Customers asked for vendor-neutral, open capability. Inside the manufacturers, it was consistently seen as a distraction from selling hardware. The demand was never in doubt; the incentive to build it simply sat with the wrong party.

Why this specific model works. Earlier in his career, David led a project at a previous company to build a custom detection algorithm for a threat a Tier 1 international hub needed and no standard product covered. Long after leaving, the customer's Operations Director told him at a trade show what it had done for them: passenger wait times had gone from 15–45 minutes down to around five.

That result belongs to that operator and that project, not to Sentriko. But the mechanism is exactly what Sentriko productises — the right algorithm for the actual threat, on the equipment already installed. The difference is that it took a bespoke engagement then, and it should take a catalogue selection now.

Sentriko on LinkedIn →

Where we are

Honest status

Sentriko is early. We would rather you knew exactly how early than found out later.

NOW Q3 2026

Working demo

  • Multi-manufacturer format ingestion in test with a Singapore screening test-and-measurement partner, under an agreement to license
  • End-to-end demo — ingest, deploy, detect, audit
  • Founding developer conversations under way
Q4 2026

Hardening

  • Reliability and performance work to pilot standard
  • Security review and deployment tooling
  • First algorithms packaged onto the platform
2027

Pilot and open catalogue

  • First operator pilots in the beachhead markets
  • SDK and developer onboarding opens
  • Air cargo alongside aviation

Target first markets: Singapore, Norway, New Zealand and Denmark — chosen for regulatory openness to new screening approaches — plus air cargo sold direct to freight operators.

Join the network

Join the Inner Circle

Security director, algorithm developer or investor — tell us which and we'll send what's actually relevant to you. No newsletter blast.

We reply personally. Nothing is shared with third parties.