ECOSYSTEM

One control plane.
Several real surfaces.

Yana isn't one single app. This is the full, current list of what actually exists in the repo today — not a roadmap, not an idea.

See Studio See the full architecture

USER-FACING SURFACES

4 ways to touch Yana.

Each surface exposes a different set of permissions — no surface is as powerful as any other.

DESKTOP

Yana Studio 1.5

An Electron app: chat, code editor, a real terminal (PTY), Git, model management, permissions, an experimental Design Canvas.

renderer (React/TS)
host (Electron main)
spawn yana-rt binary

CLI

Runtime CLI (yana-rt)

A Rust binary installed via cargo install yana-rt. Same TurnEngine, same authority chain as Studio — not a separate implementation.

cargo install yana-rt
yana-rt chat

PHYSICAL AI

Yana Wheelbot

A real ESP32-S3 robot with real firmware. It has its own WebSocket/MCP device bridge — not yet verified to go through the same TurnEngine end-to-end.

ESP32-S3
firmware  ● exists
bridge    ◐ evolving

WEB

This website

Static HTML, no framework. The download page calls the GitHub Releases API directly — no Yana server sits in between.

docs/*.html
assets/ecosystem-pages.js
GitHub Releases API

WHAT THEY SHARE

Not 4 separate implementations.
One control plane, 4 doors in.

Studio spawns the exact same yana-rt binary the CLI uses directly — same TurnEngine, same authority chain, same capability manifest. Changing surface never changes the rules.

See Yana Runtime

Studiospawns yana-rt

Runtime CLIyana-rt directly

TurnEngineone shared copy

Wheelbotits own device bridge

YANA PRINCIPLE

4 surfaces. One set of rules.

The model can change, the surface can change — the authority chain, evidence and capability manifest don't change along with them.

Get started with Yana

One control plane.Several real surfaces.