Skip to main content Skip to navigation Skip to footer
FOR DEVOPS ENGINEERS

Clone prod in a minute. Roll back in five. Stop filing tickets.

CLI-first infrastructure that clones production in 60 seconds, rolls back in under five minutes, and runs on hardware you control. No tickets. No waiting. Your data stays yours.

$ rdc repo fork production
Snapshotting production (btrfs CoW) .. done
Replicating 8 containers + databases .. done
Mounting encrypted storage (380 GB) .. done
Running health checks ......... 8/8 passed
✓ Clone ready: feature-auth-v2.internal
Time: 52s    Containers: 8    Size: 380 GB    Disk used: 1.8 GB (CoW)

Illustrative output; actual runs may include extra logs.

60s
Clone creation time
<5 min
Full disaster recovery
0
Ops tickets needed
THE PROBLEM

You automate everything. Except getting a test environment.

Your CI/CD pipeline deploys in minutes. Your IaC provisions in seconds. But when you need a test environment with real data, you file a ticket and wait three days. Meanwhile, staging is shared, flaky, and nothing like production.

69% of developers lose 8+ hours weekly to tooling inefficiencies Atlassian 2024 [1]
3 days average wait time for a new environment in enterprise teams Industry survey [2]
$50K/yr lost per developer to context switching Industry composite [3]
The old way
Mon File ticket
Tue Ops reviews
Wed Provision server
Thu Configure env
Fri Doesn't match prod
With Rediacc
rdc ceph snapshot create
52s
Done
HOW IT WORKS

One command. Full production clone.

1

Clone

Run rdc ceph snapshot create production. Btrfs CoW gives you a sub-second snapshot of everything: app, database, config.

2

Work

Start coding immediately against production-identical data. Push a branch, get a fresh clone.

3

Recover

Something breaks? Roll back in seconds. Immutable snapshots mean you never lose data.

Production Running
nginx :443
api-server :8080
postgres :5432
redis :6379
Clone
52s
feature-auth-v2 Cloned
nginx :443
api-server :8080
postgres :5432
redis :6379
UNDER THE HOOD

Why 60-second clones are possible

Rediacc uses btrfs copy-on-write snapshots at the filesystem level. A snapshot of a 380 GB production environment completes in sub-seconds and consumes zero additional storage initially. As the clone diverges, only changed blocks use new space.

Traditional approach
Rediacc (btrfs CoW)
Docker volume copy: full data copy, minutes to hours
Metadata-only snapshot: sub-second, any size
pg_dump 380 GB: 12-36 hours, one DB engine at a time
Any database cloned in one atomic operation
10 clones = 10x storage (3.8 TB)
10 clones share blocks via CoW (~15 GB delta)
Rollback: restore from backup (30+ min)
Rollback: btrfs snapshot switch (<5 min)
Cloning a Kubernetes cluster: re-provision, redeploy, re-seed data
rdc cluster fork copies it, data included. 46 seconds in our lab
WHY IT MATTERS

Built for engineers who automate everything

60-second environments

From request to working environment in under a minute. Full stack: OS, containers, databases, configuration.

CLI-first, scriptable

Everything is a command. Integrate with CI/CD, Git hooks, or your own automation. No GUI required. Kubernetes included: a namespace forks like any repo.

Instant rollback

Btrfs immutable snapshots mean you can roll back any environment in seconds. No data loss. No downtime.

Try it yourself

Install the CLI. Clone your first environment. Start your 14-day free trial, no sales call.

Start free trial
$ curl -fsSL https://www.rediacc.com/install.sh | bash