One shipment, one record
A regional freight operator replaced seven competing shipment tables with a single record that every depot, planner and invoice agrees on.
Private previewOruvex unifies data across the systems you already run. It matches and resolves records into a trusted golden record, traces every value back to its source, and keeps the result current for your teams and applications.
Unify data across databases, applications and files. Oruvex reads from each system where it lives, so nothing has to be migrated first.
Entity resolution matches duplicate and conflicting records, and rules you can inspect produce one trusted golden record.
Serve one governed, current view to analysts, applications and reports, with full data lineage back to every source.
Matches records that describe the same customer, supplier, product or site, even when systems label them differently.
Combines the best verified values from every source into one authoritative record.
Shows where each value came from and which rule produced it.
Role-based access, policy controls and a complete audit trail across every source.
Keeps the unified view current as source systems change, without batch rebuilds.
Maintains consistent reference data for customers, suppliers and products across the organization.
The console shows incoming records as they are matched, resolved and sent on, with the sources and rules behind each decision one click away.
| Record | Entity | Sources | Status |
|---|
Relational and document stores, read in place.
Analytical stores that already hold your history.
ERP, CRM, billing, support and operations tools.
The CSVs and workbooks every organization still depends on.
Queues and message buses, processed as records arrive.
Internal services and third-party platforms.
“Every report used to begin with an argument about which system was right. Now it begins with the answer.”Head of Data, regional freight operator
A regional freight operator replaced seven competing shipment tables with a single record that every depot, planner and invoice agrees on.
Private previewA healthcare provider group unified supplier and contract data held separately by each regional department, with every change traceable.
Private previewA national retailer brought catalog, warehouse and store data into one view, so what is listed is what is on hand.
Private previewOruvex reads sensitive records on your behalf, so access, visibility and location are designed in from the start.
Data is encrypted in transit and at rest, with keys managed separately from the data they protect.
Role-based permissions, scoped per source, so people see only what their work requires.
Every read, merge and change is recorded, and can be traced back to a person or a rule.
Choose where your data is stored and processed, with infrastructure in the European Union.
An independent security review is part of the path to general availability.
Read in place. Migration is a project of its own, and most teams shouldn't need one to get an answer.
Every merged record keeps a trail to its sources and to the rule that decided it. Nothing is a black box.
Predictable behavior and plain failure modes. The best infrastructure is the kind nobody has to think about.
We open access gradually and would rather be late than wrong. Each stage has to work before the next begins.
Oruvex began in the winter of 2021, when three colleagues at a regional freight operator spent months matching the same shipment records across seven systems that disagreed about almost everything. By spring they had stopped correcting the records and started building something to keep them correct.
The first prototype was called "origin vector": the place a record began, and the place it was supposed to end up. The name was shortened, and it stuck. The founders left to build it properly, and the first outside team ran on it a year later.
We don't think data should have to be moved, renamed or rewritten before it can agree with itself.
Three founders leave the freight operator and incorporate Oruvex. A first working prototype matches records across two live systems.
The reconciliation engine runs against real data from the first outside team. Rotterdam office opens.
The team reaches twelve. A second office opens in Tallinn to house engineering.
The core is rebuilt around traceable, rule-based decisions after a year of lessons from production use.
Private preview begins with a small group of founding partner teams.
The team stands at twenty-four, with the focus on hardening the core ahead of open beta.
Spent a decade in freight operations before deciding the data problem was the real bottleneck.
Designed the original matching engine and still reviews every change to how records are resolved.
Runs partner programs and the day-to-day business, and keeps both offices working as one team.
Leads the work on matching quality and on explaining each automated decision in plain language.
Leadership, partner programs, research and operations, a short walk from the harbor where the company began.
Platform engineering, infrastructure and data science, working on the same core as the team in Rotterdam.
Oruvex names Jonas Aarvik Head of Research to lead work on matching quality and explainability.
Oruvex opens its private preview to a first group of founding partner teams.
Oruvex opens an engineering hub in Tallinn as the team grows to twelve.
Working with a small group of founding teams on the core platform.
CurrentWider access as the core matures.
NextPublished pricing, documentation and support for every plan.
PlannedAdditional sources and regions, guided by what customers need.
Planned