CANUS

Why decentralised

Decentralised AI infrastructure buildout.

The next wave of AI capacity will not be built by a handful of companies that own everything. It will be built by many independent clouds, each close to its customers and its power, each putting a project together with partners it does not own. CANUS exists to make that kind of project workable: partners connected, delivery independently checked, and the operator's cloud kept its own.

  1. 01

    Demand is local. Capacity should be too.

    Customers want capacity where their data, their latency and their regulators are. Independent clouds are already there. The programme lets them build where the demand is, rather than where a balance sheet happens to be.

    See the project open on demand
  2. 02

    Nobody has to own the whole chain.

    The data centre, the power, the equipment, the money and the installation belong to different businesses. That is not a weakness to be integrated away. It is how infrastructure has always been financed. It needs coordination, not consolidation.

    See LARUS connect the partners
  3. 03

    Separate contracts. One programme.

    Each partner keeps its own contract and its own credit decision. CANUS connects them: what the project needs, in what order, with which evidence. One programme per project. Nothing pooled.

    See the arithmetic of a project
  4. 04

    Delivery proof. A clear route to billing.

    A lender that funds the equipment and construction needs to know the system works. Customers need to know before they pay. An independent check against requirements agreed before equipment is ordered turns delivery into a fact every party can use under its own agreement.

    See the cost of waiting
  5. 05

    Growth happens in stages.

    A second customer, a second phase, an equipment upgrade. Each on its own commitment and its own result, linked in one Register, so a strong total never hides one customer's shortfall.

    See the allocation blocks
  6. 06

    The operator keeps the cloud.

    Participating partners finance and deliver the project; CANUS coordinates its agreed work and checks delivery. The cloud, the brand and the customer relationships stay with the operator. CANUS owns none of it.

    See who brings what

Many operators.Separately owned partners.One programme per project.Independent delivery checks at the core.

Separately owned partners should not mean disconnected delivery evidence. We are developing agreed replacement options that let alternative capacity able to meet the same customer requirements be checked against them, while each capacity source keeps responsibility for its own service.

See how delivery choice continues

Bring the project.We bring the programme.

Today the programme is a development conversation with a small number of founding cloud operators and lenders. If you run an independent cloud with customers waiting on capacity, start there.

How the programme works