YUIO is an open-source, self-hosted AI model router and control plane for choosing the right model, enforcing budgets before dispatch, and keeping every decision observable. Three focused modules share one operating philosophy: observable, reversible, and owner-controlled.
More on the way. More on the go.
YUIO is the umbrella. Router, Command Center, and Grind keep clear logical ownership. Today they share one compact Rust runtime where that removes failure points; external tools remain short-lived, allowlisted modules rather than resident services.
The model plane
One compatible endpoint in front of multiple model providers and subscription-backed tools. It chooses an eligible route, records the decision, and fails over by failure type.
yuio-control / yuio-core
public MIT repository
The control plane
A private, responsive HTTPS command surface for model status, durable research and non-research tasks, documents, and per-task owner decisions from any device.
yuio-control / yuio-core
one runtime and policy boundary
The value engine
An unattended research worker that turns eligible, expiring model quota into reviewable reports and proposals—without silently publishing or applying generated work.
yuio-control / yuio-core
same Rust safety boundary
Safety is treated as an operating discipline, not a badge. The project favors small, testable boundaries and keeps consequential actions behind explicit authority.
Scoped service keys, private configuration, allowlisted workspaces, and no provider credentials on future remote runners.
Idempotent intake, atomic task state, bounded results, retries, and quarantined outputs survive a browser closing or a worker disappearing.
Agents may prepare work, but applying, publishing, or executing consequential generated changes remains separately gated.
Automated regression suites, build gates, dependency audits, health probes, and real-path checks back each release decision.
YUIO is under active development. Interfaces may change, reliability work is ongoing, and the public endpoints do not currently carry a production SLA.
Router, Command Center, and Grind are logical modules in one public Rust product—not three drifting services. The website and independent status probe stay separate so presentation and monitoring never become control-plane authorities. The public repository is a clean alpha snapshot; private operational history was not published.
github.com/abwebc/yuio-controlRust router and control planegithub.com/abwebc/yuio-sitethis public websitegithub.com/abwebc/yuio-statusindependent public probesMore allowlisted project actions, richer quota evidence, cleaner cross-device handoffs, and an evolving knowledge layer are next—without turning the system into one oversized black box.
Explore the source