The company
The answer is usually already in the records
A company already records what it bought, what it shipped, what it paid and what went wrong. Runink reads those records and puts an answer in front of the person who has to act on it.
Our mission
Most of what an operations, finance or compliance team needs to decide is sitting in systems it already pays for, in a shape nobody has time to read.
We connect to those systems, keep the working copy on the machines the customer's plan names, and show the reasoning behind every answer so the person who signs off can check it.
Our vision
Work where the software does the reading and a person does the deciding — and the record of that is complete enough to hand to an auditor, a regulator or a counterparty without preparing it first.
That is what we are building towards rather than something we claim to have finished. It is why every answer arrives as a draft that waits for a name, why a check that could not run says so instead of passing, and why the reasoning about a customer's records never goes to an outside AI service.
How we build it
Six rules the software follows. Each one is a thing you can ask us to show you in a running system, which is the only reason they are worth putting on a page.
A person signs, and is named
The software drafts the action and stops. It waits in a queue until somebody approves, edits or rejects it, and the record keeps who that was. In claims, customs and payment the act carries liability, and liability does not transfer to software.
It shows its working
Every draft arrives with the rule it applied and the records it read. You can disagree with it on the evidence rather than on trust.
It says when it does not know
Not measured is a separate answer from zero, and the software stores it as one, with the reason. A check it could not run reports that it could not run it, rather than passing.
It names the step it skipped
When part of a job does not happen, the result says which part and why. Software that reports success for work it did not do is the failure we designed hardest against.
No outside AI service reads your records
The models run on the machines your plan names (your own servers or cloud account, or Runink's shared machines), and there is one inference endpoint: the one set up for your plan. That is how it is built rather than a switch somebody sets, so ask us to walk the boundary with you rather than taking the sentence.
We do not claim certifications
We have not been audited against SOC 2 or ISO 27001 by anyone. The software is built against those frameworks and it will tell you what it checked; it will not tell you it is certified, because it is not.
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
One next step
The rules above are things you can ask us to show you.
Bring one lane, one claim, or one month of invoices. Half an hour, with whoever owns the problem in the room, and we walk that one example end to end. If the losses you carry are not the shape this addresses, we will say so.
Book a consultation