UMA Companion
Permanent project archive2025 - 2026

UMA Companion

A year of tools, experiments, and engineering for Umamusume trainers.

After roughly a year of development, active development of UMA Companion has come to an end. Official Umamusume updates increasingly overlap with some of the areas external companion tools traditionally covered, so continued investment no longer makes sense for this project.

Archived app

-

Data pack

-

Status

Preserved

UMA Companion collection dashboard

To everyone who used the app, tested beta builds, reported bugs, suggested features, shared feedback, or simply followed along: thank you. Your attention and patience gave this project a reason to exist.

A change in the calculation

Why UMA Companion was sunset.

UMA Companion was created to provide useful guidance outside the game: planning runs, understanding support cards and skills, preparing for races, and making complex information easier to work with.

What changed

The official game kept expanding its own guidance.

During 2026, updates announced for the Japanese version increasingly added in-game information and training guidance, including Trainer Guide features and race-specific recommended skills. Read the official announcement

What did not change

UMA Companion was not simply replaced.

These official additions do not include everything UMA Companion built. Its advanced deck optimisation, collection-aware analysis, experimental Live Run workflow, OCR, and broader desktop approach remain distinct in important ways.

Why stop now

The overall reason to maintain a separate app became weaker.

Maintaining the desktop application, Rust systems, optimizer, OCR, databases, synchronization, data pipelines, website, and release infrastructure against a changing live-service game required substantial ongoing work. As the official game moved further into the territory UMA Companion was designed to supplement, continuing that investment became harder to justify.

The game improving its own guidance is good for players. The sunset was not a claim that UMA Companion became useless, or that Cygames added the entire project to the game. The project's reason for continuing changed; the work itself still matters.

The work

What UMA Companion became.

The project grew from a card manager into a connected desktop workspace for collection, analysis, planning, and experimentation.

01

Collection to deck

Owned-card tracking, saved decks, borrow slots, notes, wishlists, and a six-card building workflow.

02

A real optimizer

A deterministic, bounded beam-search engine with scenario, target-stat, race, and skill-aware scoring.

03

Planning tools

Race schedules, course context, track details, training scenarios, skills, cards, events, and searchable reference data.

04

Live Run experiments

Windows capture, OCR, training-run state, event lookup, and an in-game companion workflow built as an experimental system.

A visual history

From a Python tool to a desktop platform.

The project passed through two distinct generations: an original V1 application, then a Tauri/Rust V2 built around a richer local data model and more ambitious analysis workflows.

Read the project history
UMA Companion V2 interface concept

Under the hood

A serious project, preserved.

The archive is also a snapshot of the systems that made the companion possible.

Desktop

Tauri 2

Frontend

SolidJS + Vite

Backend

Rust

Core engine

uma-core

Vision

uma-vision

Data

SQLite + sync pipelines

Website

Next.js + React

Downloads retired

The final build is preserved, not distributed.

The desktop installer and data packs are no longer offered because the application is no longer maintained for current game updates. The project history and showcase remain available here.

Archived app

-

Archived catalog

-

Distribution closed