Welcome to OrbiTE

Welcome to OrbiTE#

OrbiTE OrbiTE

A Rust-native transfer engine for AI infrastructure.

Overview#

OrbiTE is the transfer engine for OrbitKV’s KV cache, replacing its earlier Mooncake TENT dependency. It moves bytes between CPU memory, NVIDIA GPUs and local SSDs, within and across machines, so every end-to-end cache path, including GPU↔DRAM and GPU↔SSD, runs through one engine. The design follows Mooncake TENT’s engine, transport, context, buffer, endpoint and worker boundaries, implemented in Rust with no Mooncake C++ dependency.

OrbiTE network transports and the implemented DRAM and GPU paths to local SSD

Updates#

  • Nov 3, 2026: Local file segments support DRAM transfers through io_uring, CUDA staging through pinned DRAM, and GDS through cuFile. The DRAM path is qualified on ext4 and tmpfs in CI. Local storage

  • Nov 3, 2026: Ordered transport policies pick NVLink, RDMA or TCP per request.

  • Nov 2, 2026: FIFO/EDF admission windows, compiled QoS contracts and receiver credit windows.

  • Nov 1, 2026: Bandwidth-aware multirail selection from CUDA/NUMA topology and configured NIC preference tiers; CUDA 13 native batch copies for NVLink groups.

  • Oct 28, 2026: Bounded GPUDirect RDMA, CUDA IPC and remote CUDA staging profiles pass installed H20/RoCE tests.

  • Oct 27, 2026: The bounded host RDMA RoCE profile is independently accepted.

Status#

The source is preparing 0.1.0-beta.1; publication approval remain with the maintainer. Current hardware profiles remain unqualified. Capabilities lists each path and its limits, qualification records the evidence, and the completion plan is the work queue.

Documentation#

API Reference

Troubleshooting