Deployment
How a Coral deployment proceeds, from the first technical conversation to production workloads. Durations below are indicative for self-contained modular infrastructure of this class and are confirmed per site during the architecture review. Six stages: architecture review, site assessment, factory build and acceptance testing, installation and integration, commissioning and handover, then operation retained in-house or delegated to CoralDC.
Architecture review
A structured technical assessment covering the intended workload and hardware, available electrical capacity, floor loading, thermal conditions, water availability, acoustic constraints, network requirements, jurisdiction and compliance obligations, and access for installation. It produces a specific architecture recommendation, and where the answer is that CoralDC is not the right fit, it says so.
Typically one to three weeks from first conversation to written recommendation, depending on how quickly building information is available.
Site assessment
A physical survey confirming what the architecture review established on paper: electrical service and protection coordination, structural capacity at the intended location, delivery route and access clearances, plant space for the outdoor cooling unit, pipe and cable routing, and any permitting or building consent required.
Typically one to two weeks, including any structural or electrical engineering sign-off the building owner requires.
Build and factory acceptance
The pod is built, filled, run and tested before it leaves the factory. Factory acceptance testing covers thermal performance, pump redundancy changeover, control and interlock function, leak integrity and instrumentation. The customer is invited to witness.
Lead time depends on configuration and component availability and is confirmed at order.
Installation and integration
Delivery, positioning, electrical connection, fluid connection to the outdoor cooling unit, network integration and control system integration with the building where required.
Typically days rather than weeks, because the system is self-contained. This is the stage a conventional build replaces with data hall construction.
Commissioning and handover
Site acceptance testing repeating the factory tests in situ, thermal performance verification against the architecture review, control system tuning, documentation handover including as-built drawings and operating procedures, and operator training.
Typically one to two weeks.
Operation
Retained by the customer, or delegated to CoralDC under Coral Compute, with the ability to transfer between the two.
Request an Architecture Review
A structured technical conversation about power, thermal capacity, density, jurisdiction and deployment sequencing for a specific site. If the answer is that CoralDC is not the right fit, it says so.
Direct answers for infrastructure buyers.
How long does a deployment take from order to production?
For self-contained modular infrastructure of this class, order to production is typically measured in weeks to a small number of months rather than the quarters or years a conventional build requires, with the variable being component lead time rather than construction. The structural advantage is that a self-contained system removes data hall construction from the critical path. A specific timeline is established per site during the architecture review.
What happens if the architecture review concludes we do not need Coral?
Then it says so. An architecture review that only ever recommends the vendor conducting it is a sales call, and it is not useful to anyone.