Docs
Roadmap
Status separates available source and reproducible CPU contracts from hardware qualification. This roadmap promises neither a release date nor measured fleet capacity.
| Status | Capability | Boundary |
|---|---|---|
| CPU/TCP available | Identity, lifecycle, MemoryStore/FileStore, TCP ACL and reader admission | Synthetic tests; trusted network boundary, no mTLS. |
| CPU/TCP available | Bounded shard clients, membership updates and epoch fencing | Operator-managed routing; no distributed consensus or fleet-size certification. |
| Mock contract available | G4 manifest v3, bounded sink, refill and retention | Live RustFS: NOT_RUN_HARDWARE. Orphan collection is not automatic. |
| CPU simulation available | DPU messages, fault injection and functional TCP comparison | No device offload, zero-copy, throughput or TCO evidence. |
| Fake-block spike available | EngineBlockContract and engine-spike | Real vLLM export/import: NOT_RUN_HARDWARE; GPU/model run: NOT_RUN_BUDGET. |
| In development | Real RDMA, GDS, BlueField-3 / DOCA and SPDK | NOT_RUN_HARDWARE. Optional features remain unlinked and fail closed. |
Next evidence gates
Qualify a real engine with authorized GPU/model resources, then measure hardware paths against the appropriate paired baseline. Keep TCO_UNKNOWN and NOT_EVALUATED until that evidence exists. Source availability does not establish an installable release or production readiness.
Preserved boundaries
RustFS remains off the hot path. G3.5 loss leads to recompute; no hot erasure coding or durability replicas are planned. Scaling requires bounded shards, fencing and clean misses, not a verified 10,000-GPU claim.
Related documentation
Quick start · Architecture · Scaling and deployment boundaries · CPU_COMPLETION.md