Installation

MinIO Warp is open-source software released under the GNU AGPL v3.

This section guides you through installing Warp in your environment. Warp provides flexible deployment options to match your infrastructure and benchmarking requirements.

Prerequisites

Your environment needs network connectivity to the S3-compatible storage endpoints you plan to benchmark. You must have valid S3 credentials including an access key and secret key for those endpoints. The credentials require permissions to create buckets, upload objects, download objects, list contents, and delete objects.

For exact environment variable names and examples (an alternative to passing credentials on the CLI), see the Environment variables.

See the specific installation page for additional deployment-specific requirements.

Bare-metal deployment

The bare-metal deployment runs Warp as a standalone binary directly on your systems. This approach supports both single-machine testing and distributed benchmarking across multiple systems. Pre-compiled binaries install quickly on most operating systems. Building from source provides access to the latest features and allows customization.

Choose bare-metal deployment when you want direct control over hardware placement or need to avoid container orchestration overhead. This method runs directly on your infrastructure without dependencies on Kubernetes or other orchestration platforms.

For information about distributed bare-metal benchmarking, see the Advanced Features documentation.

See the Bare-metal Installation page for detailed instructions.

RDMA benchmarking

Benchmarking S3 over RDMA needs a different build of Warp. The standard binary speaks S3 over HTTP only, at every version.

From Warp 1.7.0, a separate warp-rdma package ships the binary together with libs3rdma, the library that moves the object payload across the fabric. It is published as a .deb and an .rpm, for amd64 and arm64, and the client host needs its own RDMA adapter on the same fabric as the storage nodes.

Inter-node RDMA between storage nodes needs none of this. That path is driven by any ordinary S3 workload, so the standard Warp binary measures it.

See Install Warp with RDMA support.