Docs
Runix Docs
How to integrate and work with each product. Honest about status: Router is available and FS is in early access, and both have quick starts; Data and Models are in early access by engagement; Pipeline, Code and Comic are in development, and their guides describe how an engagement works today.
02 · Guides
Product guides
Unfamiliar terms are defined in the glossary; the questions buyers ask before reading any of this are answered on the FAQ.
05 · Agents
Domain agents, and the harnesses that run them
Runix Code
Rollout guide — how a team adopts Runix Code: what the waitlist cohorts get, how seats and policies are configured, and what the review-gated workflow looks like day to day.
Runix Comic
Workflow guide — the three production stages, what you bring versus what the studio generates, and how waitlist cohorts work with us while the product is being built.
04 · Gateway
One way in to every model
Runix Router
Integration quickstart: base URL and key, model selection by vendor id, streaming, provider errors, list-price billing, limits and data handling. If your code speaks the OpenAI API, you are one config change away.
03 · Models
Open-weight models, tuned and served
Runix Models
Engagement guide: how a fine-tuning engagement runs, from the task and the baseline your current model sets, through tuning and evaluation on held-out examples, to a dedicated endpoint your team takes over or we run.
02 · Data
Domain data, cleaned for training and evaluation
Runix Data
Engagement guide: the sample and target task you send, the scoped plan and quote that come back before any work starts, and the provenance, licence and quality report every delivery carries.
Runix Pipeline
Engagement guide — how a data preparation project runs: scoping, the six pipeline stages, what you receive at delivery, and the quality report that comes with it.
01 · Infrastructure
Storage that keeps GPUs fed
Runix FS
Quick start: start a cluster, attach an S3 bucket, mount it as a directory with FUSE, give Kubernetes pods volumes through the CSI driver, and manage the cache.
A complete API reference ships with general availability. Until then, onboarded teams get documentation and support directly from the engineers: ask us anything.
03 · Reading
Background reading
The engineering blog covers the mechanics behind the products.
Cost
Cost control levers, prompt caching, and attribution per team.