Where Runix is, and what comes next
Seven products in five layers, at deliberately different stages. The statuses on this page are the ones used everywhere else on the site: Router, Models, Data and FS are in early access; Pipeline, Code and Comic are in development. What each status means, what general availability adds, and how the order is decided, without dates.
Drawn from the same product definitions as the home page and the header, so this page cannot say one thing and the stack another.
Seven products today
- Early access
- Runix Router, Runix Models, Runix Data, Runix FS
- In development
- Runix Code, Runix Comic, Runix Pipeline
- Dates
- None published. Cohorts and design partners set the order.
02 · Board
The board
One row per product: its status, what a team can do with it today, and the next thing that changes.
03 · Shipped
What has shipped, with the date
The dates the site already publishes, in order. A state is published when it is reached.
- July 8, 2026Runix announced; the gateway, now Runix Router, enters early access. Introducing Runix
- August 2, 2026Documentation for every product: the Router quickstart with streaming, failover semantics and the error envelope with request ids. The docs
- September 29, 2026Runix FS enters early access, built on the open-source Curvine project; the Security page is updated. Introducing Runix FS
- September 30, 2026Runix Models and Runix Data enter early access; the Router models catalogue at public list prices; the stack is drawn in five layers under the mission Rebuild AI Unix. Rebuild AI Unix
- October 7, 2026Solutions by team, the Agents layer by domain, this roadmap, and the blog grouped by layer. Solutions by team
04 · At GA
What general availability adds
General availability is a state, not a date. On this site it means these three things exist.
A complete API reference
A complete API reference ships with general availability; until then, onboarded teams get documentation and support directly from the engineers.
A published service level for Router
A service level for Runix Router is published at general availability, with a contract behind it; during early access the mechanism is documented and no number is.
Self-serve signup and checkout
Self-serve signup and checkout arrive with general availability; until then accounts and keys are set up by the team after a short intake.
05 · How it is run
How the roadmap is run
Statuses are literal
Early access and in development mean the same thing on every page of the site, and none of them is aspirational. A product changes status when the thing changes, not when the copy does.
No dates are published
A date on a roadmap page is a promise the engineering has not made yet. The site says what is running, what is being built and what general availability adds, and leaves the calendar out.
Cohorts set the order
Waitlist cohorts and design partners decide what lands next by what they run into. The order follows their traffic and their data, not a launch plan.
Early access
Early access means a product you can use today, set up by the team rather than bought off a shelf. There is no self-serve signup: accounts and keys are issued after a short intake, and a reply comes within one business day. You evaluate before you pay: Runix Router issues evaluation credits on request with no card required, and Runix FS, Runix Data and Runix Models are scoped per engagement, with the plan and the price agreed before any work starts. No service level is published during early access; the failover mechanism is documented instead, and if your procurement needs a guarantee, say so at intake and we will say plainly whether early access fits.
In development
In development means the product page describes what is being built, not a shipped product. Runix Code and Runix Comic are built with waitlist cohorts, invited in order, who get access as capabilities land and whose feedback sets the order of what comes next. Runix Pipeline is built with design partners, the teams whose data runs through its stages first. None of the three is generally available, and nothing on their pages is a promise of a date.
06 · Questions
Common questions
When will a product be generally available?
No date is published for any product. The site states the status a product has reached and what general availability adds; a status changes when the thing changes.
Can we use a product that is in development?
Through its waitlist or as a design partner, in cohorts invited in order. Access arrives as capabilities land, and the product page says what is being built rather than what is finished.
Does early access mean beta?
It means set up by the team rather than bought off a shelf: a short intake, evaluation or scoping before any payment, and no published service level. The failover mechanism is documented instead of a number.
Ask about the product you are waiting for
Tell us which product and what you would do with it. We reply within one business day with where it is and what you could use today.
Contact sales