Welcome to OrbitTE#
A Rust-native transfer engine for AI infrastructure.
GitHub · Quick Start · Architecture
Overview#
OrbitTE provides owned, batched data movement across CPU memory, NVIDIA host staging and network transports. Its design follows Mooncake TENT’s resource and runtime boundaries, implemented in Rust without a Mooncake C++ dependency.
The engine owns registration, batches and completion. TCP, RDMA and opt-in CUDA IPC are separate payload transports, with a shared control service for peer discovery, grants and receipts. Allocations remain owned until native work has drained.
Getting started#
Run the CPU example, select optional providers with the build guide, and use the Rust API guide to register memory and submit transfers. The RDMA/CUDA guide explains device selection, persistent resources, completion and shutdown.
Development status#
CPU/TCP, persistent host RDMA, multirail slicing and synchronized NVIDIA host staging with owned copy streams/events, and explicit GPU direct RDMA are implemented. Native qualification applies to the exact profiles in qualification. The published alpha reserves the crate name; the source implementation remains under development.
The host RDMA implementation and declared installed cleanup fixtures are complete. Physical rail accounting verifies concurrent parents, shared QP limits and exact native payload bytes. Automatic discovery now passes two-host READ/WRITE against a separately captured PCI, NUMA and route inventory. The P4 exit queue tracks physical-fault, fabric qualification before full acceptance. Source and the bounded RoCE profile passed independent review with four fresh live repeats; P5 CUDA work now proceeds with available hardware. The GPU Direct profile passes 72 installed H20/RoCE cases with an explicit host-wide context inventory limit. The cooperative CUDA IPC/NVLink path is implemented, with 48 installed H20 cases passing. Bounded subbatch import reuse passes 28 additional installed cases on two H20 hosts. OrbitKV integration remains deferred. Capabilities distinguishes current paths from later work, including broader GPU/IPC qualification and full TENT compatibility. For code navigation, use the architecture reading order.
Getting Started
User Guides
Design Documents
API Reference
Troubleshooting