
What arrives, across 2 cabinets, racked, cabled and burned in before it ships. The nearest single server we sell is the Fusion Rack Data 300, shown in the photograph, with every part listed.
Twelve 4U nodes with 36 bays each, 6.3 petabytes raw and 4.6 usable. Eight-plus-three erasure coding, with metadata moved off the 12 onto 3 additional all-NVMe MDS nodes. Client and replication traffic run on separate 100GbE networks, so a rebuild does not take the service down with it.
Made for your workflow
Explore the hardware, shared capacity and connections that bring your cluster together.
Each square represents one node. Final capacity and cabinet layout are sized to your site.
A distributed storage cluster spreads data across nodes, so capacity, speed and redundancy all grow as you add hardware. Ceph, Lustre and MinIO coordinate where data lives, how it is accessed and how it recovers, and keep serving while individual drives or whole nodes are missing. Processing power matters most during erasure coding and recovery, and metadata performance is what usually limits a real workload, so metadata is kept apart from bulk capacity here.
Both sizes of distributed storageThese are the figures the design was specified and tested to, not figures computed from a parts list. A cluster is a network, a filesystem and a node count, and no single build expresses that. The final numbers come from sizing it to your room, your power and your work, and every node in it is measured the usual way.