Data a model can actually use
The tooling behind Runix Data: six auditable stages that turn raw, duplicated, half-structured source material into something a model reads without choking, with a quality report at the end.
Want the work done for you? That is Runix Data, the service built on this tooling.
At a glance
- Stages
- Ingest, clean and dedupe, structure, mask, report, deliver
- Deduplication
- Exact, near and semantic
- Extraction
- LLM-assisted, into your schema, validated on the way out
- Masking
- Personal data masked before a model or a training set; fails closed
- Delivery
- Files, a database or an endpoint; batch or continuous
- Role
- The tooling Runix Data engagements run on
- Pricing
- Per project or by volume, quoted first
- Status
- In development, with design partners
02 · Capabilities
Six stages, each one auditable
Every stage produces something you can inspect, so a bad answer downstream can be traced to the record that caused it.
Ingest
Documents, exports, databases and APIs, with the parsing trade-offs written down rather than hidden in a script.
Clean & dedupe
Format normalisation, noise removal, and deduplication at exact, near and semantic levels — with counts you can check.
Structure
LLM-assisted extraction into a schema you define, validated on the way out so malformed records fail loudly.
Mask
Personal data identified and masked before it reaches a model or a training set, failing closed when detection is uncertain.
Report
A quality report per delivery: coverage, duplication rates, extraction confidence, and what was dropped and why.
Deliver
Files, a database, or an endpoint — batch or continuous, whichever your downstream actually consumes.
Nobody's data is generic
Cleaning pipelines fail on the specifics: the one export with a broken encoding, the near-duplicates that are not duplicates, the field that means two different things in two systems. We scope those with you rather than pretending a wizard handles them.
That is also why it is priced per project or volume rather than per seat — you are buying the judgement calls, not a dashboard.
03 · Specifications
The details a review asks for
One table, the same shape on every product page, kept current with the pages it points to.
| Item | Value | Where it is documented |
|---|---|---|
| Stages | Ingest, clean and dedupe, structure, mask, report, deliver: each one leaves something you can inspect | Engagement guide |
| Deduplication | Exact, near and semantic, with counts you can check | This page |
| Extraction | LLM-assisted extraction into a schema you define, validated on the way out so malformed records fail loudly | This page |
| Masking | Personal data identified and masked before it reaches a model or a training set; fails closed when detection is uncertain | This page |
| Quality report | One per delivery: coverage, duplication rates, extraction confidence, and what was dropped and why | Engagement guide |
| Delivery | Files, a database or an endpoint; batch or continuous | This page |
| Pricing | Per project or by volume, quoted before work starts | Pricing |
04 · Works with
The layers on either side
Runix Pipeline hands off to its neighbours in the stack and works on its own. The same block sits on every product page, with the neighbours changed.
Above · 03 Models
Runix Models
Where model-ready data goes next: a model tuned to your task.
Explore Runix Models →Same layer · 02 Data
Runix Data
The service built on this tooling, with the rules for six domains on top.
Explore Runix Data →Below · 01 Infrastructure
Runix FS
Where the raw material is read from: one path over your object storage.
Explore Runix FS →05 · How to start
How to start
Three steps, each with a person on the other end: Runix Pipeline is not self-serve.
01Send a sample and what you need
A slice of the real data, not a description of it, and what has to come out. We reply within one business day.
02Get a scoped plan
Stages, trade-offs and what we will not attempt, with the price, before any work starts.
03Receive the data and the report
Batch or continuous, in the form your downstream consumes, with a quality report every time.
06 · Questions
Common questions
How does Runix Pipeline relate to Runix Data?
Runix Pipeline is the tooling: the six stages every engagement runs through. Runix Data is the service built on it, with the domain rules for code, finance, cybersecurity, legal, embodied AI and AI for Science. If you want the work done for you, start with Runix Data; if you want to run the stages yourself, become a design partner.
Why an engagement, not a self-serve tool?
Because the hard part is never the transform — it is deciding what "clean" means for your data, and that judgement is different every time. We start from a sample of the real thing and come back with a scoped plan, including the parts we think are not worth doing.
What happens to the data we send?
It is processed to do the work you asked for — not used to train models, not sold. The full statement is in the Privacy Policy, and the operational posture in Security.
How is it priced?
Per project or by volume, quoted before any work starts. You see the number and the scope together, so there is nothing to reconcile afterwards.
How do we start?
Pipeline is being built with design partners, so we take on a small number of engagements at a time. Send a sample and what you need out of it — become a design partner and you get a scoped plan back.
Have a pile of data and a deadline?
Send a sample and what you need out of it. You get a scoped plan back, including the parts we think are not worth doing.
Become a design partner