Tibi News

Where TibiOS Sauron stands against the AI capability frontier.

TibiOS Sauron

TibiOS Sauron announcement

TibiOS Sauron will be our first proprietary AI model, built on top of TibiOS's distributed infrastructure. The goal isn't to compete on size with the large Frontier models from day one, but to demonstrate that a network of small machines can be used to train and later run a large model in a distributed way.

Sauron will be oriented primarily toward professional code generation. Its goal goes beyond writing code from scratch: we want it to have especially strong knowledge of existing code, libraries, frameworks, and available solutions, mostly coming from the open source ecosystem.

The model's philosophy will be:

Reuse → Compose → Create

That is, faced with a development problem, Sauron should first try to reuse an existing solution, then combine already-available components and libraries, and only as a last resort implement new code.

The end goal is for it to produce the correct solution with the least amount of new code possible, while maintaining quality, security, tests, and maintainability.

Training

We won't start from scratch. We'll use an existing code model as a base and run a progressive fine-tuning process.

The first phase will be experimental, using a relatively small model to validate the methodology:

base model → SFT → preference tuning → test-based evaluation → RL

The dataset will be built from real ecosystem code and knowledge:

  • GitHub repositories;
  • libraries and frameworks;
  • documentation;
  • usage examples;
  • issues and pull requests;
  • code paired with tests;
  • programming problems and their solutions;
  • examples where reusing a library beats implementing a custom solution.

Examples that teach the model what NOT to do will be especially important: reinventing functionality that already exists, introducing unnecessary dependencies, or generating hundreds of lines when a mature library solves the problem in a handful.

From a small model to Sauron

The strategy will be incremental:

small model → demonstrate Code-Reuse → larger model → Sauron

We'll first validate that the learned behavior actually improves over the base model. Once proven, we'll carry the methodology over to much larger models, reaching the goal of Tibi Sauron, envisioned as a Frontier-scale MoE model.

In our current theoretical estimates, Sauron is planned around 671B parameters, taking architectures like DeepSeek-V3 and Kimi-K3 as references. Training isn't planned on a single machine, but over a distributed network of TibiBoxes. TibiOS would need to dynamically solve placement, memory, communication, Expert locality, node performance, and fault tolerance.

That's why our current work on:

  • GPU/VRAM-aware scheduling;
  • node performance signals;
  • capacity degradation;
  • placement reasoning;
  • network/locality;
  • network-cost-aware scheduling;
  • Expert locality;

is all part of the same architecture.

The final vision

Sauron represents the first demonstration that the ability to create advanced AI doesn't have to depend exclusively on large, centralized data centers.

A sufficiently large network of small machines can collectively contribute:

memory + compute + network + storage + inference + training.

The hypothesis we want to demonstrate is simple:

A community can build and run its own AI model using a distributed infrastructure of small machines coordinated by TibiOS.

And Sauron would be the first big experiment testing that hypothesis: a proprietary model, specialized in software engineering, trained and later run on a distributed infrastructure designed by us.

What if AI capability didn't depend on a handful of data centers, but on a distributed network of millions of accelerators?

Starting from NIST's CAISI results, we have an interesting reference point: GPT-5.5 scores 1,260 Elo, Anthropic Opus 4.6 999, GPT-5.4 mini 749, and DeepSeek V4 Pro 800. NIST also notes that the US frontier holds roughly an 8-month lead over the PRC frontier. See the original evaluation: NIST — CAISI Evaluation of DeepSeek V4 Pro.

NIST CAISI — Overall AI Capability: comparison of aggregate capabilities over time of the most capable publicly released U.S. and PRC models
Original NIST CAISI chart — comparison of aggregate capabilities over time of the most capable publicly released U.S. and PRC models. Source: NIST.
Overall AI Capability (CAISI Elo Scale): Commercial/US frontier vs PRC/open-weight frontier vs TibiOS Sauron distributed deployment milestones, Sep 2026 to Dec 2029
TibiOS scenario — CAISI Elo scale, Commercial/US and PRC/open-weight frontiers vs TibiOS Sauron deployment milestones.

From that data we built a hypothetical scenario for TibiOS Sauron: a distributed AI architecture running over a network of NVIDIA Orins.

The working hypothesis is simple: each doubling of the Orin network → +200 Elo. This is not a NIST claim — it's our planning scenario.

🟢 M1

Balanced

0.5M Orins (Jun-2027) → 16M Orins (Dec-2029)

🟠 M2

High capacity

1M Orins (Jun-2027) → 32M Orins (Dec-2029)

🟣 M3

Conservative

0.25M Orins (Sep-2027) → 4M Orins (Dec-2029)

Growth hypothesis: reference points, line definitions, TibiOS deployment milestones and frontier-crossing dates for the CAISI Elo projection
Growth hypothesis behind the projection: reference points, milestones and crossing dates (NIST CAISI, May 2026, + scenario extrapolation).

The crossings are especially interesting:

  • M2 crosses the PRC/Open-Weight frontier around May-2027 (~946 Elo) and the US commercial frontier around Apr-2029 (~1,907 Elo).
  • M1 crosses Open-Weight in Jun-2027 (~953 Elo) and reaches the commercial frontier around Dec-2029 (~1,988 Elo).
  • M3 crosses Open-Weight in Aug-2028 (~1,115 Elo), but doesn't reach the commercial frontier before Dec-2029.

The point isn't to read this as a prediction. It's to explore a different question: what happens to AI capability if we can efficiently coordinate millions of distributed accelerators? In that scenario, the question stops being just "which model will we have?" and becomes "how many nodes can we coordinate and turn into useful capacity?"

Source: NIST CAISI + TibiOS scenario extrapolation. Values beyond NIST's measured points are planning hypotheses. — NIST, "CAISI Evaluation of DeepSeek V4 Pro".

TibiOS Console Nodes — turning GPUs into distributed AI nodes

What if your gaming console could become part of a decentralized AI network? This video explores how TibiOS Sauron could transform devices such as Xbox, PlayStation, and Steam Deck into distributed AI compute nodes, turning unused GPU capacity into part of a larger intelligent infrastructure — alongside PCs, NVIDIA GPUs, edge devices, and dedicated AI hardware.

AI Without a Single Point of Failure

What happens when you depend entirely on a centralized AI service and it goes down? A Claude outage is a good reminder that even the most powerful AI platforms can become a single point of failure for the applications, agents, and workflows built on top of them. This is where TibiOS takes a different approach: bringing intelligence closer to the user through a local, distributed, and decentralized AI architecture.