Docs
author + run a simulation, connect via SDK/MCP, read the API — everything in one placeWhat Сверх Симолёт is
Сверх Симолёт gives you a base environment (a simulator or runtime — MuJoCo, PyBullet, CUDA Python, OpenFOAM, real PX4) and runs your own code on it, on a compute node contributed to the pool.
Nothing is hardcoded: you decide what to install, what to run, what to feed in and what to get out. No baked-in task, no fixed metrics. See the run contract for the universal shape.
The core loop is always the same: author a run → submit → poll → pull artifacts. Everything else (pipelines, interactive pods, git, quotas) layers on top of that one loop.
Your first run
1 Open Run and pick a base (e.g. MuJoCo), or start from a ready example.
2 Give it your code — paste it, point at a git repo, or upload a zip.
3 Set the run command (python main.py), optional setup (pip install …), inputs/outputs and resources.
4 Launch. Watch live logs + metrics, then download whatever your code wrote to /outputs.
The one trick: emit a metric
Logs always stream. Want live charts? Just print a line — Симолёт parses ##metric key=value [step=n] and draws it:
print(f"##metric loss={loss} step={i}")No metrics? You still get logs and downloadable artifacts. Full detail in the run contract.
Run contract →
How every run works: /work, config, ##metric, outputs
Runs & pipelines →
Layered RunSpec config → resolved runs, and DAG pipelines
Sessions & pods →
Interactive multi-service pods you drive live (teleop)
Simulator guides →
Per-base docs + runnable examples (live catalog)
Repo-first & git →
Run from a commit, push-to-run, commit-status mirror
Teams & orgs →
Identity, org members, and cross-org node sharing
Policy & quotas →
Layered caps, the reservation ledger, and 429 limits
SDK & CLI →
Submit programmatically (Python / Node / curl)
AI / MCP →
Drive the platform from Claude over MCP
Embedded views →
Read-only, branded iframe of one run (LMS)
API reference →
Browsable REST + SSE surface