Working with government buyers
Public sector AI infrastructure procurement asks questions commercial procurement does not, and asks them earlier. This page sets out how CoralDC engages with them. Where the infrastructure physically sits, who operates it, what the supply chain is, which certifications it holds, who supports it, and what happens if the vendor fails.
What public buyers ask, and CoralDC's answers
Where is it, physically, and who can reach it. On the buyer's premises, in a location the buyer specifies, with physical access controlled by the buyer.
Who operates it, and can we take that in-house. Either party, and the arrangement is designed to be reversible without replacing hardware or re-architecting the deployment.
What is the supply chain. Disclosed under a mutual non-disclosure agreement to a qualified procurement counterparty during the evaluation process, which is standard practice for infrastructure vendors at CoralDC's stage.
What certifications does it hold. Coral pods are engineered against IEC 62368-1 and the ASHRAE TC 9.9 thermal guidelines. CE, UL and CSA certification are available as configuration options. Certification status for a specific configuration is confirmed in writing during the architecture review. Electrical safety, EMC, seismic and environmental certification are procurement gates rather than differentiators, and CoralDC states its position per certification rather than claiming a general standard of compliance.
Who supports it, and how quickly. Support commitments are set out in the service agreement for each deployment. Consistent with infrastructure vendors serving regulated sectors, CoralDC commits to a defined response time by severity level, with the specific figures set in the agreement rather than published generically, because a response time that is not backed by a sized support organisation is not a commitment.
What happens if the vendor fails. A fair question to ask a young company. The infrastructure is the customer's property, the architecture is documented, and the system is designed to be operable and serviceable by third parties. Continuity provisions such as design-documentation escrow are a reasonable term for a public sector buyer to require and are addressed in the contract rather than asserted here.
Canadian content and domestic capability
Canadian content and domestic supply chain positioning carries genuine weight in Canadian public procurement and in sovereign programmes. CoralDC is a Canadian company, headquartered in Vancouver, British Columbia, with its engineering, systems integration and deployment function based in Canada. Specific domestic content proportions for a given configuration are disclosed to a qualified procurement counterparty during evaluation rather than published, because the figure varies by configuration and a general claim would be less useful than a specific one.
Talk to CoralDC about a public sector deployment
An architecture review is a structured technical assessment for a specific site, covering power, thermal capacity, density, jurisdiction and deployment sequencing.
Direct answers for infrastructure buyers.
Is CoralDC on any government procurement vehicle or standing offer?
Not currently. CoralDC will state any standing offers, supply arrangements or procurement vehicles it holds on this page directly if and when they exist, rather than implying a status it does not hold.
Can CoralDC support a classified or restricted environment?
Requirements vary considerably by jurisdiction and classification level and are addressed case by case rather than claimed generally. CoralDC does not currently hold, and does not claim, any specific security clearance level or Controlled Goods Program registration. Where a programme requires either, that is established through the standard qualification process for that programme.