Skip to content
Shinro Studio

Roadmap & Status

Shinro is pre-MVP. MVP target is late May 2026. The Studio frontend and the Backend Kernel are two parallel workstreams; integrating them end-to-end is the immediate critical path.

The buckets below are honest about that. We’re not going to hide what’s still on paper.

Architected & demoed internally

  • Zig Backend Kernel
  • Module system (descriptors)
  • Hot-swap module deployment
  • Shared-RAM inter-module communication
  • Module store / registry
  • Deployment to Android, Linux, Windows, ESP32, Jetson, Raspberry Pi
  • Debugger module integration
  • Self-hosting build (Shinro builds Shinro)
  • Arduino hardware discovery
  • Shinro Studio shell — Blueprint Editor on React Flow, embedded Monaco IDE, 3D viewer with Three.js + Rapier physics

Active development

  • Frontend ↔ Backend Kernel integration — the single biggest lift, and the gate on everything that wires user actions in the Studio to outcomes on the robot
  • Marketplace backend and contributor community
  • MuJoCo integration as a simulator module
  • Recursive hardware discovery beyond Arduino
  • Hugging Face AI-model integration
  • Error visualization in the UI
  • Articulated-robot demo (open-arm)
  • CrazyFly quadcopter demo
  • Deployment Manager UX

Architected, not yet built

  • Community stores beyond local
  • Formal-verification integrations (Mununu and alternatives)
  • Full ROS2 black-box integration
  • Multi-simulator selection at the Studio level (Gazebo, Isaac Sim, and others)
  • Audit / certification platform

Parked

  • Deep ROS2 message-level introspection — deliberately deferred. Too costly relative to current value.
  • A deterministic-by-default Studio Runtime Layer — deferred in favor of letting users opt into developer-controlled determinism per module.

Out of scope

  • Shinro does not sell hardware.
  • Shinro does not build robots.
  • Shinro does not aim to replace ROS or other primitive communication layers.
100%