VECTORIOTwenty-four hours to report. The evidence is in five silos.
Evidence on time. Data in place.
Operational, security and public data analysed inside your own perimeter — with results an auditor can verify without us.
What changes for you.
From raw logs to the report pack
Logs, telemetry and asset data are correlated in one run, ready for the reporting deadline.
Proof an auditor can check
Hash-chained records and sealed packages that anyone can verify offline.
Data stays in your perimeter
Processing runs on your own servers; personal data is masked before it moves.
Replay on demand
Any run can be repeated with the same result for the auditor.
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.
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.
Real workflows. From this field.
5 workflows from our test suite that teams in this field start with — ready to adapt to your data.
Every transaction is hashed on the way in, out-of-range amounts go to a review table, and the sealed evidence package is re-verified independently.
- FinancialRandomDataProvider
- Transaction EvidenceEvidence Collector
- Row Integrity Hash · Financial EvidenceKey Generator · Evidence Pack
- Amount Validation Gate · EPK Integrity VerifierQuality Gate · Evidence Verifier
- Valid Transactions CSV · Rejected TransactionsCSV Publisher · CSV Publisher
tx-gen → Generators.Random
evidence-collector → Forensic.EvidenceCollector
integrity-hash → ETL.KeyGen
amount-gate → Sync.QualityGate
valid-output → CSV.Publisher
rejected-output → CSV.Publisher
evidence-pack → Forensic.EvidencePack
evidence-verifier → Forensic.EvidenceVerifierRecords are fetched page by page, sealed before masking, masked, and sealed again — two evidence packages that show exactly what changed.
- Page Numbers (2-3) · Build API URL · JSONPlaceholder Posts · Pre-Mask EvidenceSequence Generator · Compute Fields · REST API Subscriber · Evidence Collector
- PII Masking · Pre-Mask Evidence PackData Masking · Evidence Pack
- Post-Mask Evidence · Pre-Mask EPK VerifierEvidence Collector · Evidence Verifier
- Masked Posts CSV · Post-Mask EvidenceCSV Publisher · Evidence Pack
- Post-Mask EPK VerifierEvidence Verifier
page-gen → Generators.Sequence
url-builder → ETL.Compute
api-reader → RestApi.Subscriber
evidence-pre → Forensic.EvidenceCollector
pii-mask → Security.Mask
evidence-post → Forensic.EvidenceCollector
csv-output → CSV.Publisher
epk-pre → Forensic.EvidencePack
verifier-pre → Forensic.EvidenceVerifier
epk-post → Forensic.EvidencePack
verifier-post → Forensic.EvidenceVerifierMail is read from the server, every message gets an integrity hash and an audit-ledger entry, duplicates and oversized attachments are routed out.
- IMAP Email Source · Schema ValidationIMAP Subscriber · Schema Conform
- Archive Record ID · Message Integrity HashKey Generator · Key Generator
- Combined Integrity · Derive ArchiveKey Generator · Compute Fields
- Archive Quality Gate · Attachment Size Gate · Archive Audit Ledger · DLQ OutputQuality Gate · Quality Gate · JSONL Publisher · CSV Publisher
- Attachment File Writer · Message Deduplication · Oversized AttachmentBinary File Writer · Deduplication · CSV Publisher
- RFC822 Archive Writer · IMAP Stub WriterBinary File Writer · IMAP Publisher
imap-source → IMAP.Subscriber
schema-conform → ETL.SchemaConform
archive-id-gen → ETL.KeyGen
message-hash → ETL.KeyGen
combined-hash → ETL.KeyGen
derive-metadata → ETL.Compute
quality-gate → Sync.QualityGate
size-gate → Sync.QualityGate
attachment-writer → BinaryFile.Publisher
message-dedup → ETL.Dedup
rfc822-writer → BinaryFile.Publisher
stub-writer → IMAP.Publisher
audit-ledger → JSONL.Publisher
dlq-output → CSV.Publisher
dlq-size-output → CSV.PublisherEvery transaction is compared with the customer's normal behaviour; risky ones are stopped, raised as a critical alert and filed as a case.
- Customer Profiles · Transaction StreamRandomDataProvider · RandomDataProvider
- Lookup CustomerLookup
- Compute Risk ScoreCompute Fields
- Fraud Detection GateQuality Gate
- Approved Transactions · Fraud AlertCSV Publisher · Alert
- Fraud Cases CSVCSV Publisher
customer-profiles → Generators.Random
tx-gen → Generators.Random
profile-lookup → ETL.Lookup
risk-compute → ETL.Compute
fraud-gate → Sync.QualityGate
approved-csv → CSV.Publisher
fraud-alert → ETL.Alert
fraud-csv → CSV.PublisherA checkpoint records progress, so a stopped run continues exactly where it left off.
- Log DataRandomDataProvider
- Watermark CheckpointCheckpoint
- Add ProcessingCompute Fields
- Processed Output CSVCSV Publisher
data-gen → Generators.Random
watermark → Sync.Checkpoint
meta-tagger → ETL.Compute
csv-output → CSV.PublisherReal 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.
Critical infrastructure and utilities OT data
OT analytics that stay in the plant.
Public-sector data platforms & smart city
City data under city control.
Cyber/SOC log analytics
Cut SIEM ingest, keep every log.
Healthcare & hospital data platforms
Hospital data, analysed in-house.
Manufacturing / Industry 4.0 IoT & quality data
Line data processed where it is born.
Your pilot. Three steps.
Your data shape
Tell us what data you have, where it lives and what the result must be.
A scoped pilot
On your data and your hardware, with the success measure written down first.
A clear decision
You see the result against that measure — and keep every workflow and record.
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.