VECTORIO
EN
EnglishDeutsch

No cloud. Contested links. And the result has to hold up.

Fuse at the edge. Prove every result.

Sensor, system and network data processed where it is created — on your own hardware, offline, with a record of every step.

Become a design partnerFind your role

What changes for you.

Runs disconnected

The whole pipeline runs on the device or in the vehicle, with or without a link.

Evidence that holds up

Every result carries a tamper-evident record for after-action review and accreditation.

Real time on small hardware

Video at 30 fps with on-device inference, 18.7 ms per frame on one notebook (measured).

One workflow for every tier

The same workflow file runs at the edge, in the command post and in the data centre.

In the field

Compute where the data is born. Send only results.

Sensors, cameras, drones and vehicles run PROTOR on the device. Over 5G, satellite or a local radio link — and 6G as the networks arrive — only small signed results travel. The analysis keeps going when the link drops.

river sensorjunction cameradronefield sensorsvehicle5G · 6G · satelliteedge hubPROTOR on the deviceonly results travel
Raspberry Pi-class boards (beta)4–7 peers in one cluster, demonstratedMQTT · RTSP cameras · REST feedscontinues after a dropoutevery result signed

Environmental protection

River-level and air-quality sensors raise a local alert the moment a threshold breaks — the station keeps measuring when the link drops.

Traffic control

Cameras at the junction count and classify on the device; faces and plates are blurred before anything is stored.

Law enforcement

Body-camera footage is redacted on the device and sealed as evidence that anyone can verify later.

Agriculture

Field sensors and drone imagery turn into a field map at the farm, without a fast uplink.

NGOs and disaster relief

Damage reports, sensor feeds and images are processed in the crisis area on a single rugged box.

Defence and dual use

Sensor streams are fused at the edge; the same workflow runs in the vehicle, the command post and the data centre.

Workflows

Real workflows. From this field.

5 workflows from our test suite that teams in this field start with — ready to adapt to your data.

Faces are detected and blurred frame by frame on the device itself; the result goes out as a sealed evidence package anyone can verify.

PROTOR · Body-camera footage, redacted on the devicerunning
Video File InputVideo.File.SubscriberFace BlurVideo.FaceBlurEvidenceEvidence CollectorPackageEvidence PackOutputBinary File Writer
  1. Video File InputVideo.File.Subscriber
  2. Face BlurVideo.FaceBlur
  3. EvidenceEvidence Collector
  4. PackageEvidence Pack
  5. OutputBinary File Writer
nodes
bodycam-input → Video.File.Subscriber
face-redact → Video.FaceBlur
evidence-collect → Forensic.EvidenceCollector
evidence-pack → Forensic.EvidencePack
evidence-output → BinaryFile.Publisher
18.7 ms per frame · 30 fps · 0 % frame drops · measuredfaces blurred on the devicesealed evidence package

Real workflows and node types; the designer view is illustrated. Measured values come from our end-to-end test runs.

Find your role. 5 of them.

Defence data fusion at the edge

Fuse at the edge. Prove every result.

Defence primes and integrators

The sovereign data layer under your C2.

Drones, space and constrained edge compute

Cluster-grade analytics on a few watts.

Telecom/6G network analytics

Real-time RAN analytics at the edge.

Public safety and police data fusion

Auditable data fusion you control.

Your pilot. Three steps.

1

Your data shape

Tell us what data you have, where it lives and what the result must be.

2

A scoped pilot

On your data and your hardware, with the success measure written down first.

3

A clear decision

You see the result against that measure — and keep every workflow and record.

Beta · design partners wanted

Bring us your hardest data problem. Let's solve it together.

A short pilot on your data and your hardware. We agree on what success looks like before we start.

Start a pilotSee the numbers