We build softwarefor the placeswhere mistakesdo not stay small.

See the platforms

An institution can only act as fast as it can trust what it is looking at. We build the two systems that decide whether it can.

01Olympus→Ontology & Decision Platform 02Argion→AI Software Assurance Platform

Some systems are notallowed to fail quietly.

A grid operator, a hospital, a clearing house and an air wing do not have much in common until something goes wrong. Then they all have the same problem: a consequence that has already happened, and a record that cannot say why.

In our experience the failure is almost never the people. It is one of two gaps, and each of them has a system behind it.

GAP A

The organisation has no executable account of itself.

What exists, how it relates, which states are legal and who may act is split across a scheduling system, a spreadsheet, a regulation and four people who know the exceptions. Nothing can check a rule that is not written anywhere a machine can read.

Olympus→

GAP B

Nobody can prove the software still works.

The estate changes weekly. The evidence that it still does what the safety case, the licence or the operator assumes is a test suite that breaks for reasons unrelated to behaviour, and is therefore no longer believed by the people it was built to reassure.

Argion→

Defence & national security

both

Readiness is six systems disagreeing about what is serviceable and who is qualified to fly it.

Energy & grid

olympus

The switching rule lives in a PDF, a control room habit, and one engineer who is on leave.

Healthcare operations

olympus

Beds, staff and acuity move faster than the morning huddle that is meant to allocate them.

Rail, air & maritime

argion

A safety case written against last year's build, and a release cadence that no longer matches it.

Banking & payments

argion

The control is documented. Whether it still holds after the last deployment is a search problem.

Government & public service

olympus

Case files that outlive the systems holding them, and rules that were never written down anywhere executable.

Manufacturing & industrials

both

The line stops before the dashboard notices, and the dashboard was right about everything it was asked.

Logistics & shipping

olympus

The route is replanned over the phone twenty minutes before the software is told.

Regulated software

argion

Ten thousand passing tests, and no one able to say whether a user can still complete the one journey that matters.

Two systems.One premise.

An institution cannot act faster than it can trust what it is looking at. Olympus is where it writes down what it is. Argion is what proves the software still behaves the way it was written down. Each is useful alone. Together they close the loop.

Olympus

A working model of the institution.

What exists. How it relates. What state it can be in. What may be done, and by whom. And the rules that govern every one of those actions. Olympus is where an organisation writes itself down in a form software can act on.

01Entities, relations, states, actions and rules in one model
02Authored by your people, maintained by agents, ratified by humans
03Every decision carries the rule it was taken under

Open the Olympus file→

OlympusModel / Fleet operations / v4141 ENTITIES24 RULESSYNC 00:00:02Live

Agent

Proposes relation Sortie → Part [consumes] · inferred from 2,481 closed work orders

RatifyReject

Argion

Assurance for software that cannot fail quietly.

Argion drives an application through its own interface — clicking, typing, reading the screen — and holds it to the journeys that matter. Not selectors. Not a coverage percentage. The path a person actually takes to get a thing done.

01Drives the interface your people use — no instrumentation required
02Journeys that survive a redesign instead of breaking on it
03Replayable evidence against a named build, every build

Open the Argion file→Watch the walkthrough02:21

ArgionRun 4118 · build 7c21ea · main6 JOURNEYS48 SURFACES01:12 ELAPSEDLive

Runmatrix · 6 × 4 × 3

ChromeFirefoxSafariEdgeWebViewKioskClerk · en-GBConsultant · en-GBClerk · cyRead-only · en-GB

Completed · 69Degraded · 2Broken · 1

Agent

Confirm moved from the dialog footer to the header · route re-resolved, journey completed, change reported

We do not hand overa system and leave.

Our engineers deploy into the operating core: the systems, the data, and the people who own the call. They are on the floor and at the shift change. When the system ships, it ships into their hands and stays in ours.

A model that nobody maintains and a suite that nobody believes are the same failure arriving by different routes. Both are what happens when the people who built the thing have gone.

01Embed

Engineers on site, in the room where the call is made, for as long as it takes to understand what the call actually depends on.

02Model

What the organisation is gets written down: entities, states, the rules that are applied rather than the ones that are published.

03Deploy

Into the estate as it stands. On-premise, in a sovereign region, or air-gapped, against the systems already in place.

04Assure

Every build is driven through its own interface and held to the journeys that matter, so the evidence is produced rather than assembled.

We stay.

01Embed

Engineers on site, in the room where the call is made, for as long as it takes to understand what the call actually depends on.

02Model

What the organisation is gets written down: entities, states, the rules that are applied rather than the ones that are published.

03Deploy

Into the estate as it stands. On-premise, in a sovereign region, or air-gapped, against the systems already in place.

04Assure

Every build is driven through its own interface and held to the journeys that matter, so the evidence is produced rather than assembled.

We stay.

What we holdto be true.

The institutions of the free world deserve to be as fast as the threats they face. We are not neutral about that.

The last century went to whoever produced more. This one goes to whoever decides faster. That is a race free societies can win.

Open societies deliberate, and that is a strength worth keeping. What it should not cost is the hours between knowing and acting.

The people inside these institutions are rarely the constraint. They decide with whatever reached them in time. Too little does.

Institutions were built for a world where information moved slowly. That world is gone. The designs stayed.

A decision delayed is a decision taken by whoever moved first. Institutions are judged on what they did in time, not on what they knew.

An institution is a labyrinth.It holds everything it needsand cannot find the way through.

We are the thread.

Tell us the decisionthat is going wrong.

Not the roadmap. Not the stack. The call.

hello@rynth.ai