CANUS

What we do

One programme around your project.

We bring the right partners into one programme, connect their commitments, and independently check the delivered system. The partners finance, supply and build; you run the cloud and keep your customers. The programme is one ongoing service: project coordination, independent delivery checks and support through expansion.

See an example

WHAT CANUS DOES

Five jobs.One appointment.

You have customers who want GPU capacity. The funding, the data centre, the power, the equipment and the installation have to come together, and today you hold them together alone. You appoint CANUS once and it stays with the project. The five jobs below describe the work; a real programme moves between them as the project does. The partners keep their own obligations to finance, supply and build.

  1. 01

    Scope

    What is being ordered, by whom, for when, and what is missing
  2. 02

    Assemble

    Your partners, plus the funding, data-centre, power or installation partner you lack
  3. 03

    Coordinate

    Requirements, dependencies and owners, tracked in LARUS
  4. 04

    Check

    Independent delivery checks on each phase, signed for the organisations that use them
  5. 05

    Grow

    The next phase, customer or agreed change of capacity source, with evidence that still applies kept

THE PROGRAMME, END TO END

The programme is the product.

  1. Customer demand
  2. Scope
  3. Partners
  4. LARUS
  5. Fund + build
  6. Check
  7. CCEC
  8. Register
  9. Next phase

Every expansion, change or agreed replacement re-enters the same programme. Evidence that still applies is kept. What has changed is checked again.

The programme is also being designed for pre-agreed replacement options: checking whether capacity from another data centre or cloud operator can meet the same order, what evidence remains usable and what checks and permissions are still needed.

Inside the programme

Two systems.Both ours.

LARUS connects the people, deadlines and requirements. CANUS verification checks the delivered system against what the customer ordered. Both support the project as it expands.

What we do

01 · LARUS · Our project coordination platform

Who does what.What happens next.

See the funding conditions, power approvals, equipment dates and delivery requirements together. Know who is responsible and what a delay affects. Each partner keeps its own systems and obligations.

SITEFUNDING RELEASEEQUIPMENT DATEPOWER APPROVALDELIVERY REQUIREMENTSPHASE 1
  • One map per phase
  • Partners keep their systems
  • Every date has an owner

02 · CANUS verification · Our delivery-check technology

Did the customer get what was ordered?

Our technology checks the delivered GPU system against the agreed requirements. The signed result states what the evidence supports and what remains unresolved. It becomes part of the delivery history in the CANUS Register.

Node count and configurationconsistent
Interconnect and fabricconsistent
Power stage and redundancyconsistent
Storage and network pathconsistent
Thermal envelope under loadconsistent
Consistent · SignedChecking 1 of 5
  • Checked against the agreed requirements
  • Three results, all issued
  • Repeatable on the next phase

Named customers, lenders and other agreed organisations receive the same signed result. Each makes its own acceptance, funding or insurance decision under its agreement.

INDEPENDENT DELIVERY CHECKS

Independent delivery checks at the core.

When a phase is delivered, CANUS's own verification technology checks it against the requirements the parties agreed and signs its result in the CANUS Compute Evidence Certificate (CCEC): CONSISTENT, INCONSISTENT or INSUFFICIENT EVIDENCE. Customer, lender and cloud operator read the same record under their own agreements. Where the contracts reference it, that result supports the customer's sign-off and the start of billing. How CANUS checks stays confidential. What it found, for whom, and within what limits, does not.

CANUS · THE REGISTER

FICTIONAL EXAMPLE

CANUS-EX-001

DELIVERY CHECK

Result

Consistent · Signed
What was checkedThe parties' delivery requirements, fixed at the order
Who can use the resultThe customer, the cloud operator and the participating lender
Later recordsNone yet. Every material change returns as a linked record

CANUS signs the result. The parties apply their own agreements.

  • SIGNED RESULTS FOR NAMED ORGANISATIONS
  • EVIDENCE FOR SIGN-OFF, BILLING AND FUNDING DECISIONS
  • LIMITS AND OPEN QUESTIONS STATED
  • DECISIONS STAY WITH THE PARTIES

PROGRAMME FEES

Paid for the programme.Never the result.

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; rates are confirmed in the appointment.

Bring CANUS in before equipment is ordered.

Today the programme is a development conversation. Bring the project, the customers behind it and the pieces that are missing; we will tell you plainly whether a CANUS programme fits.

How it works