V4D

Volumes for Docker

The complete data management platform for Docker. Block-level protection, cross-host recovery, and compliance reporting — backed by S3, on any Linux host.

Get StartedSign In

Your Docker Data Is at Risk

Docker hosts running stateful workloads have no practical disaster recovery. A single disk failure, accidental deletion, or ransomware event means total data loss.

$5,600/min
Average downtime cost
83%
Never tested their DR
<1 min
MTTR with V4D
5 min
RPO per application

What V4D Delivers

Nightly rsync scripts & hope
5-minute RPO, every application
Manual host migration — days
Cross-host recovery in minutes
No audit trail for DR tests
PDF reports for compliance & audits
Enterprise backup tools — $$$
S3 storage costs only
Locked to one storage backend
Portable across Ceph, ZFS & LVM

How It Works

V4D automates the entire protection pipeline — from volume discovery to point-in-time recovery.

1
Manage
Discover volumes
2
Snapshot
Capture state
3
Diff
Changed blocks only
4
Protect
Replicate to S3
5
Recover
Restore any point
Ceph RBD
Block-level snapshots via rbd export-diff for efficient incremental backups.
ZFS
Native send/receive streams for consistent, incremental volume replication.
LVM Thin
thin_delta differencing — works on any Linux host with an extra disk.

Key Features

Volume Lifecycle Management

Automatic discovery, tracking, and management of every Docker volume across your fleet.

Per-Application RPO

Set individual RPO targets per application. V4D ensures each volume meets its protection SLA.

App-Level Recovery

Recover any application to any point in time. Cross-host, cross-backend, with full data integrity.

PDF Reports & Dashboard

Compliance-ready PDF reports and real-time dashboard for protection status, RPO adherence, and fleet health.

Recovery in One Command

Browse your journal, pick a target time, and let V4D handle the rest.

v4d-cli
$ v4d apps
NAME          STATUS    RPO     LAST PROTECTED  SKEW
postgres-db   healthy   5m      2 min ago       0s
redis-cache   healthy   5m      3 min ago       12s

$ v4d recover --app postgres-db --target prod-host-02
Recovering postgres-db to prod-host-02...
 Snapshot located (2 min old)
 Volume restored from S3
 Container started on prod-host-02

Recovery complete in 47 seconds.

Performance at Scale

5 min
Recovery Point Objective
<5s
Snapshot Skew
<4 min
Protection Cycle Time
<10 min
Full Recovery Time
<50 MB
Agent RAM Usage
<1%
Agent CPU Overhead

Works on Any Linux Host

Storage Backends

  • Ceph RBD
  • ZFS
  • LVM Thin

S3 Targets

  • AWS S3
  • MinIO
  • Backblaze B2
  • Wasabi
  • Any S3-compatible

Platforms

  • Ubuntu 22.04+
  • Debian 12+
  • RHEL 9+
  • Rocky / Alma Linux

Deployment

  • Bare metal
  • VMware / KVM / Hyper-V
  • Cloud (EC2, GCE, Azure)
  • Edge / IoT

Simple, Transparent Pricing

All editions use S3-compatible storage — you pay only your cloud storage bill. No per-GB licensing fees.

Community

Freeforever
  • Up to 2 protected hosts
  • 1-hour RPO
  • LVM backend
  • Cross-host recovery
  • Community support
Get Started
Coming Soon

Pro

Coming Soon
  • Unlimited hosts
  • Custom RPO targets
  • Priority support
  • PDF compliance reports
  • Fleet dashboard
  • V4D Portal access
Stay Tuned
Coming Soon

Enterprise

Coming Soon
  • Everything in Pro
  • Warm DR standby
  • Dedicated support & SLA
  • Custom integrations
  • On-premise deployment
Contact Sales

Join the Community

Excited to try V4D? Join our Discord community to get early access, share feedback, ask questions, and connect with other users and the development team.

Join our Discord

Get Started in Minutes

One binary. One config file. One systemd service. Install to working DR in under 30 minutes.

quickstart
# Install the V4D agent
$ curl -fsSL https://get.v4d.sh | sudo bash

# Register with the V4D Portal
$ v4d register --token <your-registration-token>

# Start protecting your volumes
$ v4d protect --all --rpo 5m