Case study · Shared operations layer
Two companies, one journey, no shared database.
Lorys B.V. · B.V. · Netherlands · lorys.nl
A horse leaving a Dutch stable for the Gulf travels by truck and then by plane. That is one journey to the client and two companies in reality. Lorys is the layer where those two businesses meet: freight hand-overs, the paperwork that follows the horse, and the money between them. Neither company can see into the other.
Shared ledger
liveimmutable · both sides agree
- Companies
- 2, kept separate
- Access
- One-way, scoped
- History
- Immutable
- Data
- Held in the EU
Before
The obvious answer was the wrong one.
Koekkoek moves horses across Europe by road. Horse E.T. flies them between continents. A single client journey routinely uses both: a truck to the airport, a flight, then another truck at the far end. To the horse owner that is one booking. Between the two companies it is a hand-over, a stack of documents that has to travel with the animal, and an invoice to settle afterwards.
The obvious fix is to plug the two companies' systems into each other. It is also the fix that causes damage for years. Direct integration means each company's primary application has a permanent door into the other's, every schema change becomes a negotiation between two businesses, and nobody can answer the question that eventually gets asked: exactly which of my records can they see?
These are independent companies. They cooperate on some journeys and compete for nothing, but they are not one organisation, and their data should never behave as if they were.
What was built
A third system that neither company owns.
Freight hand-overs
The moment a horse passes from road to air, or back, recorded once as a shared event rather than twice in two systems that later disagree.
Shared workflows
The steps both companies need to see on a joint journey, without either of them gaining sight of the rest of the other's operation.
Financial transactions
What one company owes the other on each shared movement, captured as it happens instead of reconstructed from invoices at month end.
Reconciliation
Both sides settling against the same record of what actually moved, so a disagreement becomes a lookup rather than an argument.
Permission-scoped access
Each company reaches only its authorised segment. Not by convention or good manners, but enforced, so the boundary holds when someone new joins or a script misbehaves.
Immutable audit trail
Every action recorded in a way that cannot be quietly rewritten later. When two companies share liability for a live animal, the history has to be worth something.
The hard part
The architecture decision was the whole project.
The engineering that mattered here happened before any feature was built. Connecting two companies is a data-ownership question wearing an integration costume, and getting it wrong is expensive in a way that only shows up two years later.
So Lorys was built as a boundary rather than a bridge. Each company's own platform stays sovereign and unmodified. What crosses between them crosses through Lorys, where access is one-way and scoped: a company can see and write only the operational segment it is authorised for, and nothing else exists as far as it is concerned.
That decision buys three things. Tenant isolation is structural rather than promised, so neither company is trusting the other's discipline. Either side can change its internal systems freely, because nothing external depends on their shape. And the awkward question, who is allowed to see what, has a precise answer that can be shown to a partner, an auditor or an insurer.
It also means the shared history is neutral ground. Neither company hosts the record of their joint work, so neither can be accused of editing it.
Where it stands
Two independent companies run joint journeys as a single operation, while each keeps full ownership of its own data. The hand-overs, the shared paperwork and the settlement between them all live in one place both can trust, precisely because neither controls it.
Commercially the same structure lets Lorys be the single face a client deals with, stable to stable, road and air, while behind it the separation stays absolute.
Because the shared record is where two companies' liability meets, it is held inside the EU and written so that history cannot be quietly revised. Neither party has to take the other's word for what happened.
The pattern generalises well beyond horses. Any two businesses that cooperate on part of a workflow and must not see the rest of each other have this problem, and most of them solve it with a direct integration they regret.
What a request passes through
Platform & engineering
- Permission-scoped access
- One-way data flow
- Tenant isolation
- PostgreSQL with immutable audit logging
- Reconciliation engine
- wAI operation engine
- EU-hosted infrastructure
More work
European road transport, live animals
Koekkoek Int. Horse Transport B.V.
A platform, not an app: the whole company on one set of records.
Intercontinental equine air transport
Horse E.T. B.V.
A platform that understands the horse before the journey is planned.
Horse transport, Morocco corridor
Med&Ark Services SARL
A sister company given exactly the slice of the parent's data it needs.
Start here
Your operation is different. That is the point.
Every system here was built around how one company actually works. Tell us how yours runs and we will tell you what it would take.