A modular data center is compute capacity that arrives on a truck. The enclosure, racks, power distribution, and cooling are built and commissioned in a factory, delivered as a unit, and connected to power, water or ambient air, and network at the destination.
For recovery planning, this changes what is possible. Standing up conventional capacity in a leased or owned facility is a construction project measured in months. A modular unit compresses the build portion into manufacturing time that can run in parallel with everything else, and reduces the on-site work to placement and connection.
That compression is real, but it moves the constraint rather than eliminating it. The limiting factor becomes the site.
When Does a Modular Data Center Make Sense for Recovery?
In four situations.
Recovery capacity at a secondary location. An organization with a primary facility and no real secondary can place a modular unit at an owned property — a distribution center, a manufacturing site, a corporate campus — and have recovery capacity under its own control rather than in a shared provider environment.
Bridging a migration. When a destination facility is not ready and the source lease is expiring, a modular unit provides somewhere for the equipment to live that is not a storage warehouse. It runs, it is monitored, and it can be migrated from later on a schedule you control.
Capacity that has to exist where facilities do not. Edge sites, remote industrial operations, and temporary large-scale events all need compute in places with no data center and no reason to build one.
Density the existing building cannot support. Older facilities frequently cannot cool modern high-density racks within ASHRAE TC 9.9 thermal guidelines. A purpose-built modular unit designed for that density sidesteps a retrofit of the main building.
What Does the Site Need Before a Modular Unit Arrives?
Everything the factory does not build, the site has to provide.
Power is the most common blocker. A modular unit needs a service of the right capacity and voltage, delivered to the pad. If the utility service at the location cannot support it, you are in a utility upgrade — which has its own lead time, frequently longer than the unit itself.
Foundation and placement means a prepared pad rated for the unit's loaded weight, with crane or transport access to set it. Soil conditions, grading, and drainage all get evaluated. So does whether a crane can physically reach the position.
Network requires the same carrier lead times as any other facility. Fiber to a pad behind a warehouse is not necessarily faster to provision than fiber to a building.
Cooling support depends on the design. Air-cooled units need clearance and unobstructed airflow. Units with water-based rejection need a water supply and a place to discharge, which brings its own permitting.
Permits and approvals are the item that surprises people. Depending on the jurisdiction, a modular unit may be treated as a permanent structure, requiring zoning review, building permits, electrical inspection against the National Electrical Code (NFPA 70), and sometimes a variance. Some municipalities process this quickly. Some do not, and the review can exceed the manufacturing lead time.
Start the site work concurrently with the order, not after delivery. The unit arriving before the pad is ready converts an asset into a storage problem.
Deployment Realities
Transport is oversize. A container-format unit moves as a heavy haul with route surveys, possible oversize and overweight permits, and in some corridors escort requirements. Bridge ratings, overhead clearances, and turn radii determine the route, and the route determines whether the unit can reach the intended position at all.
Set and connection is a coordinated day. Crane, rigging, electrical, mechanical, and network trades all converge, and they have to converge in a defined order. A missing licensed electrician holds up everything behind them.
Commissioning on site is still required even though the unit was commissioned at the factory. Transport is a stress event. Power-on, load test, cooling verification, and monitoring integration all get repeated at the destination before anything production-bearing goes inside.
What Are the Tradeoffs of Modular Capacity?
Modular units are constrained by their form factor. The rack count, power envelope, and cooling capacity are fixed at manufacture. Growing means adding units, and adding units means repeating the site work.
Cost per rack is generally higher than conventional construction at scale. Modular wins on speed, on locations where building is impractical, and on projects small enough that conventional construction overhead dominates. It does not usually win a straight cost comparison against a large purpose-built facility.
Serviceability differs. Working inside a container-format unit is working in a confined space with limited aisle width. Routine maintenance is fine. Large-scale rework is awkward.
Vendor dependency is real. The unit is an integrated product, and the specialized components — cooling, power distribution, controls — come from the manufacturer. Support terms and parts availability deserve the same scrutiny as any other single-source dependency in a recovery plan.
Fitting It Into a Recovery Strategy
A modular unit is capacity, not a recovery plan. It still needs data replicated to it, systems configured on it, and procedures that have been tested against it.
The failure pattern is treating delivery as completion. A unit that is powered, cooled, connected, and never exercised is an untested recovery site with better packaging. It needs the same failover testing, the same runbook validation, and the same periodic exercise as any other standby environment — because the question during an incident is never whether the capacity exists, but whether anyone has successfully run production on it.