Runink CORECORE · Control · Orchestration · Resilience · Enforcement

Your software, your AI and your data, on machines you own.

Runink CORE keeps your company’s software healthy, governs the AI models and agents that work inside it, watches your own data, and turns a written brief into a working application. Its AI model runs on those same machines. No outside AI service is called.

A product in its own right, sold separately · in English, Spanish, French and Portuguese

Runink COREOne console, five parts. Each answers one question.

  • OverviewIs anything wrong, and where do I go next?
  • DevExIs the platform running, and did our changes ship?
  • DataExWhat may our models and agents do, and can we trust their work?
  • IntelligenceWhat does our data hold, and where do money or controls slip?
  • FORGEHow does a written brief become a working application?
It asks before it acts.

Where does our information go? To a machine you own, and it stays there.

5 partsOverview, DevEx, DataEx, Intelligence and FORGE, on one menu
1 commandbrings the whole platform up on one workstation
your modelthe assistant, the helpers and FORGE all run on your hardware
every actionrecorded with a name, in a record anyone signed in can verify
Three habits on every page

It says what it knows. It asks before it acts.

Most companies now run more software than any one person understands. CORE gives every application the same foundations once: somewhere to run, one way to prove who you are, a way to reach company data, one place to look, and a way to get changes made.

How the console is arranged →
  • Not known is not zero. A figure the console could not read is shown as not known, never drawn as a zero, so nobody decides on a reading nobody took.
  • A person approves. The automated helpers propose. Nothing is filed, changed or published until someone with the right to decide says yes.
  • A second opinion. Where a finding matters, an independent assessor reads the evidence first. It can agree, disagree or say it could not judge.

What each part of the console does

Every page opens the same way: one status line, a headline, and where the reading came from and when it was taken.

overview

Start the day in one look

Headline readings, then a Needs attention list, worst first, each item linking to the page that deals with it. Ask CORE, the assistant, does a task in plain words and shows every step it took.

devex

Know what shipped

GitOps shows whether what is running matches what was written down. Deploy lineage shows whether a change reached production. Press Verify now on the Audit chain and it names the first record that was altered.

dataex

AI you can answer for

Model cards list each model’s source, version, licence and test evidence, checked against what is live. Autonomy is a setting you choose for each kind of action, and every kind starts with a person approving each act.

intelligence

See what your data holds

Dashboards for the analyst, the finance lead and the programme office, built on one set of figures. Data quality, capital spending, business rules and lineage, each computed from your own records or shown as absent with the reason.

resolve

An inventory read, not remembered

Resolve maps which systems hold which data and how they connect, when an administrator asks. It keeps structure and counts only, never a value, and marks each link as declared, inferred or a guess.

forge

From a brief to an application

Describe what you want in plain words. The company’s own model proposes the steps on a canvas, and nothing is filed until a person approves. The brief never leaves your hardware.

See it on your own hardware

CORE runs on one machine, from one downloaded file, with one command. The version on your workstation is the version that runs on your machines.

  1. In an afternoon

    Open Overview and notice which readings say they have not been measured. Open the Harness and read a remedy. Open the Audit chain and press Verify now.

  2. In a day

    Add one real data source. Try to change it as somebody who is not on the permitted list, and read the record that refusal leaves.

  3. In a week

    Put it on machines you own. Have somebody outside the platform team request a deployment, and watch it remove itself when its lease ends.

Read the detail

Bring one system you would like to stop worrying about.

Half an hour, with whoever owns it in the room. We will show you what CORE reads from it, what it keeps, and who can change it.

Data You Can Trust. Decisions You Can Defend.

runink.org/products/core/