Object storage built for disaggregated systems
Warpdrive is a purpose-built S3-compatible object store focused on workloads that demand high throughput — storage-disaggregated databases, ML training pipelines, and agentic workflows that move computation close to data.
Modern databases, agents, and training systems are building on top of object stores. But historically, high-efficiency systems have never benefited from an opaque storage layer. Object stores were designed for archival and customer file uploads, and that opacity was fine for those use cases. Now latency-sensitive systems are building on the same interface. Through our characterization work we have identified a few early parameters that capture how disaggregated workloads actually use storage, and we expose these so developers can tune them analytically from their own workload behavior. We think both sides benefit when the storage layer is legible and you can reason about its internals, develop against its behavior, and work together toward a system that is genuinely cost-efficient.
Modern databases like Neon, SlateDB, and TidesDB separate their storage layer from compute. They ship their WAL segments, SSTables, and layer files to object storage — and expect it to keep up.
Agents manage state, memory, and tool outputs at runtime. They need fast, consistent object storage with predictable latency — not the eventual consistency and cold-start penalties of cloud S3.
ML training jobs checkpoint model state to object storage continuously. Warpdrive provides the throughput and S3 compatibility to serve as a local or rack-local checkpoint store without changing a line of training code.
A storage layer designed for the systems that need it most.
Drop-in replacement for AWS S3. Any client or library that speaks S3 works without modification — boto3, aws-sdk-rust, the official CLIs.
Built for workloads where throughput and low latency matter: serverless databases, ML checkpointing, and distributed system state storage.
First-class support for storage-disaggregated architectures. Run storage and compute independently, scale them separately, attach either to S3 clients.
Warpdrive ships as a single native binary. Choose your install method below.
# Add the Warpdrive apt repository
curl -fsSL https://releases.warpdrive.dev/gpg \
| sudo gpg --dearmor -o /etc/apt/keyrings/warpdrive.gpg
echo "deb [arch=amd64 signed-by=/etc/apt/keyrings/warpdrive.gpg] \
https://releases.warpdrive.dev/apt stable main" \
| sudo tee /etc/apt/sources.list.d/warpdrive.list
sudo apt-get update && sudo apt-get install -y warpdrive
warp_drive after install.
# Clone and build git clone https://github.com/vitality-ai/warpdrive cd warpdrive/server cargo build --release # Run (must be executed from warpdrive/server/) WARPDRIVE_ADMIN_ACCESS_KEY=mykey \ WARPDRIVE_ADMIN_SECRET_KEY=mysecret \ ./target/release/warp_drive
storage/ and logs/ directory in the working directory. It listens on port 9710 by default.
# Run with Docker
docker run -d \
-p 9710:9710 \
-e WARPDRIVE_ADMIN_ACCESS_KEY=mykey \
-e WARPDRIVE_ADMIN_SECRET_KEY=mysecret \
-v $(pwd)/data:/data \
ghcr.io/vitality-ai/warpdrive:latest
docker-compose.yml is available in the repo for local development.
Quick smoke-test with boto3 after the server is running:
Tested against real production systems using their native S3 clients — no shims, no compatibility layers.
object_store crate (0.14) as the S3 abstraction layer. ISO 8601 LastModified required.
In pipeline: LangGraph · LlamaIndex · Ray · PyTorch Lightning
Measured against real engines running their own real workloads, OLTP and OLAP alike, not synthetic microbenchmarks.
take latencyWarpDrive also runs as a multi-node, erasure-coded cluster with pluggable content-dependent placement: a bucket can opt a workload's own structure (Parquet column chunks, vector-index partitions) into how its bytes are striped and erasure-coded. Measured against established tools, not synthetic benchmarks: DuckDB's official TPC-H (via its own dbgen) and Lance's IVF_PQ vector search.
take latencyWarpDrive's design work feeds back into peer-reviewed research, not just internal benchmarking.
WarpDrive: A Composable Storage Substrate for Disaggregated Data Systems — accepted as a lightning talk at CMDS (Composable Data Management Systems), the VLDB 2026 workshop. Read the position paper →
WarpDial — a case for reconfigurable placement policies and explainability in storage SLAs. Currently under review; we'll link the paper once a decision is in.