VECTORIO“Sovereignty is policy; your pipelines are still scripts on someone's laptop”
City data under city control.
Pipelines under municipal control without a US-cloud dependency
- We must keep data under our control, but sovereign options are slow to arrive.
- NIS2 makes us prove security evidence, and today it is a spreadsheet.
- Every department built its own data silo and script, none of it is auditable.
- Pipelines under municipal control without a US-cloud dependency
- Audit and NIS2 evidence that an authority can verify without the vendor
- One platform for heat maps, records archive and security evidence
From today to the first result.
a spreadsheet for security evidence and a script per department
NIS2 evidence lives in a spreadsheet, every department has its own silo and script, and a mail or records archive must survive an audit 6 to 10 years later.
Each message gets a hash, findings are hash-chained into a tamper-evident ledger, and the signed evidence pack verifies offline on city hardware.
Seal one mail folder as a signed evidence pack and verify it offline.
one folderMail archive with integrity proof. Step by step.
Mail 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.Publisher- IMAP Email SourceReads mail from an IMAP folder.
- Schema ValidationEnforces required fields and safe types.
- Archive Record IDCreates keys or keyed hashes from chosen columns.
- Derive ArchiveComputes new columns from expressions.
- Archive Quality GateChecks rows against rules and routes failures to a dead-letter table.
- Archive Audit LedgerAppends rows as JSON lines.
- DLQ OutputWrites rows to a CSV file.
- Attachment File WriterWrites binary payloads as files.
- Message DeduplicationDrops duplicate rows with a Bloom filter or exact keys.
A real workflow from our end-to-end test suite; the designer view is illustrated.
What you get. From the first pilot.
Pipelines under municipal control without a US-cloud dependency
Audit and NIS2 evidence that an authority can verify without the vendor
One platform for heat maps, records archive and security evidence
Why your tools fall short.
Hyperscaler platforms conflict with sovereignty requirements
Gaia-X defines the rules for data exchange; the processing engine is up to you
Classic BI/ETL suites need licences and heavy infrastructure municipalities lack
- NIS2 obligations and fines
- Digital-sovereignty policy (Gaia-X, sovereign cloud)
- OZG/administrative digitalisation
- Records-retention law
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.
Related roles in Regulated evidence.
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.