VECTORIO
EN
EnglishDeutsch

“Your cars record terabytes; your pipeline starts after the upload”

Test-drive logs, filtered at the garage.

KPIs and scenario filters computed before data is uploaded

The problem
  • Test cars fill disks faster than we can upload, so we ship drives.
  • We cannot find the 10 relevant seconds in 10 petabytes.
  • Our supplier data and test logs may not leave Germany.
With PROTOR
  • KPIs and scenario filters computed before data is uploaded
  • Anonymised footage before storage
  • Release-over-release KPI comparisons that are reproducible

From today to the first result.

What you do today

shipping drives from the test cars

Test cars fill disks faster than the upload runs, so drives travel by post, and the relevant seconds are hard to find in the pile.

With PROTOR

KPIs and scenario filters are computed at the test bench before upload, and footage is blurred at 18.7 ms per frame at 30 fps with 0 % drops before it is stored.

Your first step

Compute one KPI at the garage on the log of one test car.

one test car
How it runs

Live camera, on-device detection. Step by step.

A live camera stream is analysed by a local model; only confident detections are kept and sealed as evidence.

PROTOR · Live camera, on-device detectionrunning
CameraRTSP Stream InputDetectONNX ClassifierMonitorVideo ViewerRow FilterETL.FilterEvidenceEvidence CollectorPackageEvidence Pack
  1. CameraRTSP Stream Input
  2. Detect · MonitorONNX Classifier · Video Viewer
  3. Row FilterETL.Filter
  4. EvidenceEvidence Collector
  5. PackageEvidence Pack
nodes
camera-input → Video.RTSP.Subscriber
object-detect → Classification.Onnx
confidence-filter → ETL.Filter
evidence-collect → Forensic.EvidenceCollector
evidence-pack → Forensic.EvidencePack
viewer-output → Video.Viewer
live cameraon-device modelevidence package
  1. CameraReads a live camera stream.
  2. DetectRuns an ONNX model on each row or image.
  3. MonitorShows frames live in a window.
  4. Row FilterKeeps only rows that satisfy a condition.
  5. EvidenceHashes rows and batches into a tamper-evident evidence manifest.
  6. PackageSeals a manifest into a verifiable evidence package.

A real workflow from our end-to-end test suite; the designer view is illustrated.

What you get. From the first pilot.

KPIs and scenario filters computed before data is uploaded

Anonymised footage before storage

Release-over-release KPI comparisons that are reproducible

Why your tools fall short.

×

Spark/Databricks costly at petabyte scale and cloud-bound

×

ROS bag tools work one file at a time

×

Hyperscaler automotive stacks conflict with IP and sovereignty needs

What drives it
  • ADAS/AD validation volume
  • Privacy rules for camera data
  • Cost of cloud storage and egress
  • Supplier/OEM IP protection

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.