Logistics & Supply Chain

The evidence of your next loss is already in your systems.

An entry held for a missing paper while the port charge runs. A refrigerated load drifting warm overnight. A claim still inside its filing window. All recorded somewhere already, and nobody with the hours to assemble it.

Where the decision happens

Records you already keepSpread across the systems you already run.
One finding, with its evidenceDrawn together into a single proposed action.
A person approves itBy name, and nothing goes out before they do.
The work goes outAnd the reason stays on the record.

Where it goes wrong

The hold nobody joined to the cost

An entry sits at the port for a missing paper. The notice arrives with everything else from overnight, and the daily charge runs until somebody joins it to the invoice.
Claims that expire quietly

One claim means the carrier's receipt, the weighbridge reading, the rate on the date, the deadline and a drafted letter. Only the largest are worth the morning.
Temperature you read after the write-off

A container drifts out of range overnight and the reading is already in the sensor data. The window between saving the load and writing it off is hours.
Demand that grew on the way up the chain

Every stage rounds up to a full case and adds a safety margin, so the plant builds for demand that never existed. The amplification lives in the sequence, across four systems.

Who owns this

The people whose week it changes.

Operations director

You find out before your customer does, and the fix is drafted when you do.
Chief financial officer

Recoveries stop being a heroic effort and become a pipeline you can read.
Head of planning

Safety margins are argued from your own numbers, not by seniority.
Trade compliance

A held entry arrives with the reason, the papers that release it and the charge accruing.
Chief information officer

A shorter security review, because the data stays on your machines.

What changes

Findings arrive as ranked, specific proposed actions with the records attached, not as another dashboard.
A named person approves, edits or rejects each one, and that approval is recorded. Nothing leaves before it.
Approving ends the work rather than starting it: the message to the carrier, the deadline and the update to your system of record follow from it.
Later, why a claim was filed or an entry held is answered from the record.

How you will know it worked

Every figure below is yours, not ours. Write down where you stand today — the baseline stops being recoverable the moment things improve.

The measure	Your figure today	What moves it
Demurrage and detention days	Terminal and carrier invoices and the per-diem lines your forwarder passes through. A full quarter, by port, separating document-caused days from congestion.	Down on the document-caused share. A hold arrives as a running clock: the entry, the port, the reason, which papers would release it, how long it has sat.
Claim filing rate, and days from event to filing	From carrier exception records and freight audit: claim-eligible events in a quarter, how many were filed, and where each filing fell inside the carrier's window.	Rate up, days-to-file down. The receipt, the reading, the rate on the date and the deadline arrive assembled, so the reviewer judges only whether the case holds.
Days from event to detection	Sample last quarter's holds, excursions and late vessels: when each was recorded, against when a person first acted. Few operations have counted this gap.	Down, and the rest depend on it. Checks run against your own records overnight, so the morning queue is what happened, not what somebody opened.
Spoilage and write-off on temperature-controlled stock	The write-off account in your ledger and the quality rejection log for the same period, with temperature excursions separated from other causes.	Down, by moving loads back inside the window where an excursion is still a save. The reading arrives with the load named and a corrective dispatch drafted.
OTIF, or DIFOT if that is your term	Your transport or warehouse system: confirmed delivery against the date and quantity promised on the order line, monthly and by customer.	Up, through the avoidable failures. A disruption still running arrives with the orders and customers it touches identified, and route alternatives set beside each other with time and cost.
Forecast error and days of stock cover	Your planning system's forecast against actuals by line, days of cover per line, and expedited freight coded as premium or air in accounts payable.	Error stated instead of assumed. A forecast arrives with how closely it fitted your history and how many periods it had, so stock is placed ahead of demand rather than flown to it.

Two things that make the above possible

Your data stays on your machines

The order files, the customs papers, the sensor readings and the reasoning about them stay on hardware you control. Nothing goes to an outside model provider.

What you would notice

The security review a shipper runs before it will let you hold its order data, and the customer-data clauses that today need an exception. With no third party in the path, both have less to argue with.
Research that does not tell anyone what you are researching

When an answer needs the open web — a carrier's standing, a customs ruling, a published rate, a party you are unsure about shipping to — public pages are read directly with an ordinary browser.

What you would notice

The confidentiality of the question. Asking a search company about a consignee tells it who you are checking, and that record sits outside your control. Here the question stays with you, and the pages behind the answer come attached.

Who you would be working with

Runink is founder-led. The person in the first meeting is the person who designed the thing being discussed.

Dan Paes

Chief executive and technical founder

Dan Paes has spent more than twenty years inside other people's enterprises, running digital transformation and full-scale modernisation programmes for global organisations. The long kind: what is being replaced is what the business is running on that morning, and the work is judged on whether anything broke.

He founded Runink and runs it as chief executive. Technical founder is the more useful half of that title — he sets the architecture and works in the code, so the person answering an architecture question in a first meeting is the person who decided the answer, and the distance between a question and a change is short.

It is also why the platform is shaped the way it is. It runs on hardware the customer controls, and the reasoning about their data stays there. That is the more expensive way to build it and it closes off the convenient route, which is the kind of decision that has to be settled by whoever owns the architecture rather than left where it can quietly be traded away.

He is a FINOS Ambassador. FINOS is the Fintech Open Source Foundation, part of the Linux Foundation, and the work there is interoperability between institutions that share a market but not their infrastructure and never their data. It is the same problem this platform is pointed at, argued in the open, in front of people who say so when it is wrong.

20+ years

Digital transformation and full-scale modernisation for global enterprises.
CEO and technical founder

Runink. Sets the architecture and writes code in it.
FINOS Ambassador

Fintech Open Source Foundation, a Linux Foundation project. Open source interoperability, in public.

Check any of it

See whether it fits

Bring one lane, one carrier, or one month of returns. A short conversation is usually enough to tell whether the losses you carry are the shape this addresses. It is built around freight forwarders and third-party logistics providers, manufacturers with international inbound flows, and food, pharmaceutical and chemical distributors.

Book a consultation Read the FACE paper

Runink FACE is the product behind this page. The paper is the long version — what it reads, what it produces, who approves it and where it runs. It carries no case studies, no customer names and no return-on-investment figures.

Where the decision happens

Where it goes wrong

The hold nobody joined to the cost

Claims that expire quietly

Temperature you read after the write-off

Demand that grew on the way up the chain