Programme overview

Usually the cloud operator or the project sponsor (the company paying for the work). A compute buyer, a system integrator with delivery obligations, or a lead contractor can also commission agreed work. CANUS is appointed under the transaction documents, and the organisations entitled to receive and use its results are agreed at the same time.

Five jobs under one appointment. Scoping what the project needs: customer requirements, timing, existing arrangements and missing pieces. Bringing partners into the programme: the operator's existing partners, plus suitable funding, data-centre, power and installation partners where needed. Coordinating the agreed work: requirements, connected dependencies, responsibilities and outstanding actions tracked in LARUS, our project coordination platform. Independently checking delivery: checking the agreed requirements and issuing signed results to the named organisations in the CANUS Compute Evidence Certificate (CCEC). Supporting expansion and change: establishing what still applies, what additional work is needed and who must decide. The agreed delivery requirements are fixed at the order; the CANUS Register keeps the results and whether they still apply; the Acceptance State API makes authorised result information available to the named organisations.

Bring customer demand; CANUS scopes the project and the partners, and the order, requirements, named organisations and scope of the checks are agreed. Partners finance, supply, build and power the project under their own contracts while CANUS tracks the agreed work in LARUS. CANUS checks the delivery and issues its signed result; the parties apply their own agreements. Later deliveries, additional customers, material changes and agreed replacements re-enter the programme with the required new work and linked records.

Acceptance, funding, funding release, escrow and billing decisions remain with the parties and their agreements. Power approvals remain with the network and other relevant authorities. Build, commissioning and operations remain with the cloud operator and its contractors. Partners keep their financing, design, supply, construction, power and operating obligations. CANUS stands behind its programme work and its independent results, and nothing beyond them.

Programme fees reflect the project's scale, agreed scope and ongoing services. Pricing is agreed before work begins and does not depend on a favourable result or funding approval. No tariff is published.

Bring a real project. Three founding places are open: the CANUS fee for the first agreed trial delivery check is waived, any third-party costs are agreed before work starts, and ongoing programme services are separately scoped and priced. Scope and timing are confirmed privately after qualification.