Runix, by what your team is trying to do
The stack is the map; this is the other way in. Six kinds of team, the problems each one usually calls about, the layers that address them, and how working together starts. Statuses stay literal on every page.
Every product is also sold on its own; a solution page names the ones that usually fit one team.
Six teams, five layers
- Platform teams
- Runix Router, Runix FS
- Model teams
- Runix Data, Runix Pipeline, Runix Models, Runix FS
- Engineering organisations
- Runix Code, Runix Router
- Studios and creators
- Runix Comic, Runix Router
- Regulated industries
- Runix Router, Runix Data, Runix Models
- Research labs
- Runix FS, Runix Data, Runix Models
02 · Teams
Six teams, one stack
Each page: the situation, the products and their roles, how it starts, what is in writing, reading, and questions.
For platform teams
One endpoint for every model, with the controls your team owns
For the team that owns the integration between the company's products and the model providers. Runix Router puts one OpenAI-compatible endpoint in front of every provider, with key custody, per-key limits and failover beneath it. Where training or inference data lives in object storage, Runix FS gives the GPUs a file system over the bucket.
- Start: Runix Router
- Runix FS
For model teams
Data you can audit, a model you can measure
For teams that train or tune models and have to show where the data came from and whether the result beats what they run today. Runix Data builds training and evaluation sets with provenance per record. Runix Models fine-tunes open-weight models and serves them single-tenant. Runix FS reads it all from the bucket you already have.
- Start: Runix Data
- Runix Pipeline
- Runix Models
- Runix FS
For engineering organisations
AI coding rolled out, not smuggled in
For organisations adopting AI coding across many developers and many repositories, where a pile of personal accounts and no visibility is the current state. Runix Code, in development, is being built so every change lands as a reviewable diff, with seats, per-key limits and attribution by developer. Runix Router gives the model calls one policy and one bill.
- Start: Runix Code
- Runix Router
For studios and creators
A studio for comic dramas, from script to episode
For studios and independent creators making serialised visual stories, comic dramas in particular, where the work is the whole production line and not a single picture. Runix Comic, in development, is being built around pre-production, production and publishing, as an independent agent with its own harness. Runix Router is optional in front of its model calls.
- Start: Runix Comic
- Runix Router
For regulated industries
Written answers for the review that never ends
For finance, legal and security teams that have to answer a reviewer before anything carries traffic. Runix Router puts the data terms, the contracting entity and the failover mechanism in writing. Runix Data applies domain rules for finance, legal and cybersecurity data. Runix Models serves a model single-tenant, in your cloud account, trained on your data and nothing else.
- Start: Runix Router
- Runix Data
- Runix Models
For research labs
Datasets in the bucket, GPUs that stop waiting
For AI for Science and embodied AI groups with datasets in object storage and records that need domain judgement before a model learns from them. Runix FS mounts the bucket as a file system, cached in front of the GPUs. Runix Data applies its rules for antibody, protein and embodied AI records. Runix Models tunes and serves open-weight models.
- Start: Runix FS
- Runix Data
- Runix Models
03 · How to read
How to read these pages
Statuses are literal
Router, FS, Models and Data are in early access; Pipeline, Code and Comic are in development. A solution page that names a product in development says so, and the page describes what is being built.
Nothing is invented
No customer names, no uptime numbers, no certifications. What is in writing is linked to the page that holds it: the terms, the privacy policy, the Security page and the pricing page.
One product is a fine start
The pages describe a path through the stack, not a bundle. Most teams begin with one layer and add the next when the first has earned it.
04 · Questions
Common questions
Do I have to buy the whole stack?
No. Every product works on its own and is bought on its own. A solution page names the products that usually fit one team; most teams start with one.
Which page should I read first?
The one closest to your job. Platform teams own the integration with model providers; model teams train or tune; engineering organisations are adopting AI coding; studios make serialised visual stories; regulated industries answer reviewers; research labs move datasets and models for science.
What if none of these is my team?
Write to us anyway. The pages are the six situations we see most, not a limit; a reply within one business day says which products apply and which do not.
Tell us which team you are
Your stack today, the thing you are trying to change, and the volume. A reply within one business day names the products that apply and the ones that do not.
Contact sales