Skip to main content

Distributed Compute

Coming Q1 2026 — Distributed Compute is currently in development. This documentation is a design preview. Request early access to be notified when it’s available.

Overview

Distributed Compute enables AI training and inference across hybrid Earth-space infrastructure. Coordinate federated learning, partition models optimally, and synchronize through bandwidth-constrained orbital links.

Federated Learning

Train models across Earth and orbital nodes with gradient compression

Model Partitioning

Optimal layer placement across Earth and space infrastructure

Sync Scheduler

Ground station pass planning and priority-based queuing

Space Mesh

ISL routing for orbital node communication

Why Earth-Space Distributed Compute?

Large AI models don’t fit on any single node. Training and inference must span infrastructure. But space introduces unique constraints:

Architecture

Your training job connects to RotaStellar Distributed Compute, which coordinates workloads across ground and orbital infrastructure:
1

Distributed Compute Layer

The core coordination layer includes Federated Learning (gradient compression and aggregation), Model Partitioning (optimal layer placement), and Sync Scheduler (ground pass planning).
2

Space Mesh

Inter-Satellite Link (ISL) routing enables orbital nodes to communicate with each other and relay data to ground stations.
3

Infrastructure

Ground Nodes provide high-bandwidth terrestrial compute. LEO Nodes run solar-powered orbital compute, connected via ISL and synchronized during ground passes.

Key Capabilities

Gradient Compression

Reduce bandwidth by 100x with minimal accuracy loss:

Async Aggregation

Handle intermittent connectivity with async federated averaging:
  • Nodes train independently during eclipse/no-contact periods
  • Gradients sync during ground station passes
  • Central aggregator handles out-of-order updates
  • Convergence guaranteed despite variable latency

Intelligent Partitioning

Split models optimally across Earth and orbital nodes:
  • Minimize data transfer at cut points
  • Account for per-node compute capacity
  • Adapt to changing orbital geometry
  • Balance latency vs throughput

Quick Start

Performance

Timeline

Get Notified

Request Early Access

Be the first to know when Distributed Compute is available.