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.

One of six solution pages. Statuses are literal: the products named below are in early access or in development, as marked.

The stack for regulated industries

Runix Router
One compliant endpoint for every model · early access
Runix Data
Domain data for training and evaluation · early access
Runix Models
Fine-tune and serve open-weight models · early access

02 · Situation

The situation

Three things this team is usually dealing with when it calls.

Where do the prompts go?

The first question in every review, and the one most teams cannot answer hop by hop. A vendor's answer has to name the entity, the data terms and what is retained, in a document the reviewer can file, not a slide.

Data with rules of its own

Filings, contracts and vulnerability records each have a definition of clean that a general-purpose pipeline does not know. Personal data has to be found and masked before anything reaches a model, and a record that cannot be cleared has to be held back rather than passed through.

A shared model is a shared tenant

Fine-tuning on internal data raises the question of where the weights live and who else is served from the same deployment. The honest answer has to be in the contract, before training starts.

03 · Stack

The products, and the role each plays

Each one works on its own; together they are one path through the stack.

Runix RouterLayer 04 · GatewayEarly access
One OpenAI-compatible endpoint with central key custody and, per key, quotas, rate limits and allowed models. The data terms are written: content is processed to serve the request and never used for training, operational metadata is kept for billing and support, and a request id comes back on every response.
Runix DataLayer 02 · DataEarly access
Domain data for finance, legal and cybersecurity, each with its own rules and the public standards they follow. Every record carries its provenance and licence; personal data is masked before a training set and detection fails closed; evaluation is split from training by source.
Runix ModelsLayer 03 · ModelsEarly access
Fine-tuning of open-weight models, licence checked first, served dedicated and single-tenant behind an OpenAI-compatible API, in your cloud account or on capacity arranged per engagement. Your data trains and evaluates the model you commission, and nothing else; weights and access are set in the contract before training starts.

04 · Start

How it starts

A person on the other end at every step; nothing here is self-serve.

01Bring the review to the intake

Send what you are building, the expected volume and what the reviewers will ask for: the MSA and DPA, availability requirements, where data may travel. We reply within one business day and say plainly whether early access fits.

02Evaluate Router before paying

Router accounts are set up after a short intake, with evaluation credits issued on request and no card required. Transport is TLS with the obsolete versions refused, and every response carries a request id.

03Scope Data and Models per engagement

Data engagements are quoted per project or by volume before any work starts, with the checks each record has to pass written into the plan. Models engagements are quoted after scoping and before training, with weights, access and serving set in the contract.

05 · In writing

What is in writing

The parts a review asks for, stated once and linked to the page that holds them.

Data terms

Content sent through Runix Router is processed to serve the request and never used for training, and operational metadata is kept for billing and support. The data you give Runix Models trains and evaluates the model you commission, and nothing else.

Contracting and billing

The contracting entity is Runix AI Inc; an MSA and a DPA are available on request. Billing is usage-based in USD, itemised, on a prepaid balance or by invoice.

What is not claimed

No service level is published during early access; the failover mechanism is documented instead. Where your procurement requires a guarantee, say so at intake and we will say plainly whether early access fits.

07 · Questions

Common questions

Can we sign an MSA and a DPA?

Yes, on request. The contracting entity is Runix AI Inc, and the documents are reviewed per engagement.

Is there a service level agreement?

Not during early access. Runix Router's failover fires mid-request with streaming preserved, and the mechanism is documented; a published number would need a contract behind it.

Is our data used to train anything?

Content sent through Runix Router is never used for training. With Runix Models, your data trains and evaluates the model you commission, and nothing else; weights and access are fixed in the contract before training starts.

Bring your reviewers' questions to the intake

Tell us what you run today and what you are trying to change. We reply within one business day with a concrete plan, and we say which parts we would not do.

Talk to sales