What MatrixAI Studio does

Upload your CSV and several engines compete for the best model for your data

  1. You upload your table A CSV with what you want to predict.
  2. Several engines compete Gradient-boosted trees and networks, measured the same way on your data.
  3. You keep the best one With its receipt: what competed, what won and why.

Depending on what you want to predict, the model is one of these three kinds:

Examples:

Will this machine fail? The network looks at its temperature and its vibration.

Epoch0
Test errorTest0.781Training errorTraining0.831

Each square shows what one neuron sees over the plane of the data, and the thickness of each line, the weight of that connection: violet when it adds, amber when it subtracts. While it trains, one data point travels through the network, layer by layer, and the map marks which one.

Runs fineFailslearns (100)checks (100)

It gets 39 of the 100 test points right.

Press Train to watch it learn.

An illustrative simulation running in your browser: a small network learns from 200 made-up points. It is not the MatrixAI engine, it sends nothing anywhere and it does not create any model.

  • On your PC or your server
  • Training spends no tokens
  • Your data stays in your infrastructure

It is not a cloud chat answering from what it already knows: it is your own model, trained and measured on your data. The engine that validates best wins, whether it is a tree or a network. How we measure →

Build auditable AI models
on your own machines

Download the Studio and run it on your own infrastructure: your data never leaves it, except what you choose to send to your own LLM. Say what you want to predict and MatrixAI makes several engines compete — gradient-boosted trees and our own neural network — under a rule written before measuring, picks the best one with cross-validation and keeps the test set for the final figure. Every decision states its reason, and the choice is written in a receipt — what competed, what won and under which rule — that travels with the study.

What that means — and what it does not
24,662 tests passing
Docker · CPU or GPU

Check a risk score you already use

Does it work here?

A risk score, or a vendor’s model, was built on another population. This check measures whether it ranks cases well, whether its risk is right, what happens at the threshold you use and who it fails. Here, on a made-up case.

The case: 2,400 made-up admissions with two scores for readmission within 30 days, a vendor’s risk (a probability) and a 0 to 10 points scale. We planted that the vendor overestimates the risk and does worse in patients over 80.

Simulation · made-up data
  • Does it rank well?

    Calculating…
  • Is its risk right?

    Calculating…
  • At today’s threshold

    Calculating…
  • Who does it fail?

    Calculating…
  • Against another score

    Calculating…

A simulation: this page calculates it with JavaScript, not the MatrixAI core. Made-up data. It is not a clinical validation.

In the demo, your CSV leaves your computer for the demo server, is processed in memory and is discarded (up to 10,000 rows or 5 MB). Do not upload patient data or personal data to it. In the downloadable Studio, everything is local: the check runs on your machine and the CSV does not leave it.

How it works, in 4 steps

  1. 01

    Download it and install it on your machines

    One package with Docker, for CPU or for GPU. It runs on your own equipment: your data does not leave it, except what you choose to send to your own LLM.

    The study framing screen, after “Try the study” on the home page, with saved studies and examples to start from
  2. 02

    Open your CSV in the Studio and choose what to predict

    You confirm the column to predict and the kind of task: yes/no, several classes or a number.

    The study setup form: the column to predict, the problem type, the positive class and the unit of observation, with the confirm button
  3. 03

    The engines compete and the best mean is chosen

    Several engines are measured with the same cross-validation. The best average wins, and the test set is kept for the final figure.

    The Results screen: the champion engine, why it was chosen and its figure on the held-out test
  4. 04

    Use your model and take it with you

    Predict with it, row by row or a whole CSV, and download the package. Save the study: it carries its receipt of what competed and why it won.

    The Use screen: trying a row with the chosen model, with a field for each column

Measured against the reference engines

38 / 40
datasets within 2 points of the best engine
23
datasets where it is the best engine

On 40 public datasets, with a protocol written before measuring, MatrixAI’s network (its architecture starts from TabM, Yandex Research; the adaptation, the protocol and the measurement are ours) lands within 2 points of the best on 38 of 40 — and is the best on 23 — against 6 engines, with their default values:

EngineWithin 2 points of the bestBest on
MatrixAI network38 / 4023
LightGBM26 / 402
CatBoost25 / 408
scikit-learn HGB25 / 402
XGBoost24 / 403
scikit-learn (linear)13 / 402
Baseline (dummy)0 / 400

These figures are from Phase 0, not what you get in the product. This network has been in the Studio since v2.8: it competes in the study, in both packages, as one more engine, and wins where it is the best.

Measured in the Studio’s study, on 13 public datasets, without a GPU and with 6 GB of memory for the container. CPU package: The champion improves on 2 of 13 datasets (difference in points of its test score: dresses-sales +4.4, pc1 +1.6), drops on none and none stops completing. On 2 the study did not end with a champion, with the network or without it. On 2 the estimated memory exceeded the container’s and the network did not compete (Allstate_Claims_Severity: 15.3 GB estimated against 6 GB; KDDCup09_appetency: 7.8 GB estimated against 6 GB).

GPU package: The champion improves on 3 of 13 datasets (difference in points of its test score: dresses-sales +4.4, house_16H +1.8, pc1 +1.6), drops on none and none stops completing. On 3 the study did not end with a champion, with the network or without it. This run was also done without a GPU: what it does on a GPU has not been measured.

And since v2.9 you can choose it in the expert mode, as a single-engine study measured against the reference. It is recommended for tables after a confirmation run on 8 datasets: it came within 2 points of the best of the three networks in 7 of them (the exception: climate-model-simulation-crashes, where the network of the core study beat it by 2.1 points). Its time is measured, not promised; the time limit cut 1 of the 22 measured folds (mfeat-factors).

This is how we measure every engine that competes in the study. How we measure →

The records of this measurement →

Works onTables (CSV)Yes/no, several classes or a numberA text column you declare
A declared text column competes as one more engine in the study.
Auditability

The choice is written down with its reason

Every decision of the study — which engines competed, which one won and under which rule — is written in a receipt that travels with the study. In the Studio you download it comes unsigned unless you configure your own key; “The proof” explains what each level holds up.
Honest measurement

The test set is kept for the end

The engines compete with cross-validation on the development rows. The test rows are kept for the final figure, so the number you read was not used to choose the winner.
On your machines

Your data stays with you

You download the package and run it with Docker, on CPU or on GPU. Your data never leaves your machines, except what you choose to send to your own LLM. The online demo uses sample data.
Portability

Take the model with you

Export the winner with its preparation recipe and the program that predicts (predict.py; it needs the Studio engines). The full study, with its receipt, is downloaded separately. When LightGBM wins a binary classification with its decision chosen and no date columns, you can also generate a page that predicts in the browser, in ONNX.
predict.pyFull study (.zip)ONNX (LightGBM, binary, no date columns)

The engine is free. The Studio package is €12.

The core engine is open source and always will be. The Studio package removes all setup friction so your team is productive from minute one.

MatrixAI Core

Free
Open source · AGPL v3
  • ✓Full engine · production ready
  • ✓CLI interface
  • ✓REST API + Swagger
  • ✓ONNX / WASM export of the core networks
  • ✓GPU optional · Docker ready
  • ✓AGPL v3 — fully open source
View on GitHub ↗

MatrixAI Studio

Recommended
€12one-time · VAT included
Pre-configured · Ready in minutes
  • ↳Everything in Core
  • ✓Studio pre-configured out of the box
  • ✓One-click Docker Compose setup
  • ✓CPU and GPU packages, image included
  • ✓Licence for 3 machines · 3 downloads
  • ✓Opens on the study. Also includes expert mode, the classic interface and the Workbench
No account needed · credentials sent by email · Stripe
14-day refund — full money back within 14 days, unless you have already started your first download. You accept that when you download, and your licence stays valid meanwhile.
The core engine will always be free and open source. · The €12 funds continued development.

Financial

Regulatory traceability
The problem
The regulator asks why that model was chosen and with what evidence. Today the answer is a spreadsheet and a prayer.
The solution
MatrixAI Studio leaves each study with its receipt: which engines competed, which one won and why, and under which rule it was measured. The audit answer is that choice written in a receipt with its reason.
↗ Every model choice is written down with its reason

Healthcare

Justified choice
The problem
The model predicts high risk. The committee asks why this model and not another. The black box has no answer.
The solution
The study compares several engines with the same cross-validation and keeps the test set for the final figure. Every decision states its reason. And your clinical data never leaves your machines, except what you choose to send to your own LLM.
↗ The model choice with its reason written down, on data that stays in your centre

Healthcare

Local check of a risk score
The problem
The hospital uses a risk scale built on another population, or a vendor’s model. Nobody has checked whether it works on its own patients.
The solution
With the outcome the hospital already records, MatrixAI measures whether the score ranks cases well, whether its risk is right, what happens at the threshold of use and who it fails, and compares it with another score. In the downloadable Studio the CSV does not leave your machine.
↗ A local second opinion on a score already in use — not a clinical validation
Try it with an example case →
24,662
Tests passing
0
Failing
10,087
Core engine
8,279
Studio
511
Real browser
5,785
Product backend
Automated test suites — 24,662 tests0 failed