Skip to content
GOMYROBOT
Menu

Technology

Six platforms. One stack.

Physical intelligence infrastructure for space. Each platform ships real artifacts; the platforms ship to work together.

Engineering

Systems engineering infrastructure: requirements, MBSE, simulation, digital twins and verification, with the engineering AI that connects them. The point is not another requirements platform; it is connecting the engineering model to the system that actually inter-operates, acts autonomously and operates in orbit.

Interface

The interoperability platform. Space system interfaces made explicit, machine readable, testable and interoperable across four stable ESA servicing categories: rendezvous and GNC, grappling and docking, fluid couplers, power and data ports. The compatibility model asks six questions: physical, communication, software, semantic, operational and temporal. Outcomes are structured verdicts with the reasoning: Compatible, Partially compatible, Incompatible or Unknown.

Autonomy

Physical intelligence for space: perception, estimation, planning, decision, control and recovery as one pipeline. The goal is systems that sense, reason, act and recover under real mission constraints, not an "AI on spacecraft" pitch.

Flight

Deployable flight technology: flight software, BSPs and drivers, RISC-V and FPGA compute, communications, timing, security and fault management. Technology independent by design: RTEMS, RISC-V and FPGA are choices inside the kit, not the identity of it.

MissionOps

The operational layer: telemetry, commanding, mission planning, FDIR, fleet management, ground integration and space traffic support, in the environment the systems actually live in.

Reference Robotics

The physical validation environment: engineering to simulation to flight to the reference robot to SIL and HIL to mission demonstration. The full stack is proven on hardware before any flight mission.

Properties, not platforms

Interoperability, safety, security, assurance and sustainability are not one of the platforms. They are the properties every platform must hold at the same time. Security, specifically, is part of interoperability: the question moves from "can A talk to B" to "can A safely and legitimately interact with B under this configuration and mission state".

  • Interoperability
  • Safety
  • Security
  • Assurance
  • Sustainability

One measurable milestone

ServiceReady is the first integrated proof: each of the five commercial platforms ships one concrete proof artifact on a 12-18 month horizon, and the artifacts are integrated on the reference robotics environment. One testable milestone instead of five open roadmaps, one mission-proven capability at a time.

The development sequence follows from there:

  1. Engineering, Interface, Flight and Reference Robotics

  2. Autonomy and MissionOps

  3. ServiceReady with RPO and Docking

  4. Servicing, refueling and fleet

  5. Logistics and in space assets management

  6. Orbital infrastructure

See the products behind each platform

Every platform is backed by deliverable products with a public horizon. Browse the catalog by family, or start talking about a specific system you are working on.