VECTORIO
EN
EnglishDeutsch

Two forests, three address books — and nobody knows who changed what.

Directories in sync. With proof.

Connectype keeps address lists, users and groups consistent across directories and files — previewed, capped and recorded in a signed audit trail.

What changes for you.

See every change first

A preview counts inserts, updates and deletes before anything is written.

Accidents stopped at the gate

A delete cap halts the run when too much would change; the target stays as it was.

10,000 objects in 27.6 s

Created live from LDAP into Active Directory; an unchanged re-run takes 2.5 s with zero writes (measured).

A signed record of every run

Append-only history and an auditor bundle with signed seals and an offline verifier.

Workflows

Real workflows. From this field.

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

10,000 contacts are read with change tracking, checked, mapped to Active Directory attributes and written — rejected rows land in a dead-letter file for review.

PROTOR · Directory contacts, synced as deltasrunning
Contacts fileCSV SubscriberSchema ConformanceSchema ConformMap to AD schemaAD Schema MapperGAL attributesExpression MapperQuality GateSync.QualityGateDirectory exportCSV PublisherRejected contactsCSV Publisher
  1. Contacts fileCSV Subscriber
  2. Schema ConformanceSchema Conform
  3. Map to AD schemaAD Schema Mapper
  4. GAL attributesExpression Mapper
  5. Quality GateSync.QualityGate
  6. Directory export · Rejected contactsCSV Publisher · CSV Publisher
nodes
csv-source-contacts → CSV.Subscriber
schema-conform → ETL.SchemaConform
ad-schema-mapper → AD.SchemaMapper
expression-mapper → ExpressionMapper
quality-gate → Sync.QualityGate
csv-target-contacts → CSV.Publisher
csv-dlq-contacts → CSV.Publisher
10,000 contacts with change trackingmapped to Active Directory attributesdead-letter file for rejects

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

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.