CANUS

HOW CANUS WORKS

Put it together.Carry it through.

You have customers who want GPU capacity. The funding, the data centre with power, the equipment and the installation have to come together. CANUS works out what the project needs, brings the partners into one programme, tracks the work in LARUS, independently checks each delivery and stays for the next phase. The partners finance, supply and build. You keep your cloud and your customers.

What we do

THREE MOMENTS

Before equipment is ordered.At delivery.After changes.

  1. 01

    Before equipment is ordered

    What the project needs, who is already involved and who is missing. Delivery requirements, the scope of the checks and who may use the results are agreed while the design can still change.
  2. 02

    At delivery

    CANUS tracks the work in LARUS while partners finance, supply and build under their own contracts. When a phase is delivered, CANUS checks it against the agreed requirements and signs the result for the named organisations. The customer decides whether to accept delivery; billing and any funding release follow the relevant agreements.
  3. 03

    After changes

    Expansion, replacement, correction or a material change re-enters the programme. CANUS establishes what still applies, what needs checking again and who decides; the Register links the new result to what came before. Nothing is erased; nothing out of date stays current.

Commissioning proves the facility works for its owner. CANUS issues the signed evidence the parties' agreements use.

THE PROGRAMME FLOW

One programme.The parties' own decisions.

  1. 01

    Scope the project

    A cloud operator brings real customer commitments. CANUS establishes what is being ordered, by whom, for when, what is already arranged and what is missing.
  2. 02

    Bring partners in

    CANUS works with the operator's existing partners and helps engage the funding, data-centre, power or installation partner that is missing, each under its own contract. The delivery requirements become the agreed scope of the checks before equipment is ordered.
  3. 03

    Coordinate the work

    Requirements, connected dependencies, responsible people and open actions are tracked in LARUS while partners finance, supply and build under their own contracts.
  4. 04

    Check delivery

    When a phase is delivered, CANUS independently checks it against the agreed requirements.
  5. 05

    Sign the result

    CANUS signs its result for the named organisations: CONSISTENT, INCONSISTENT or INSUFFICIENT EVIDENCE.
  6. 06

    The parties decide

    The customer decides whether to accept delivery. Billing and any funding release follow the relevant agreements. CANUS decides none of them; it signs the result they use.
  7. 07

    The next phase

    For the next phase, customer or change, CANUS establishes what still applies, what needs checking again and who decides. The Register keeps results, the organisations that may use them, questions and corrections linked.

ONE CONTINUING PROGRAMME. EVERY CONSEQUENCE REMAINS WITH THE CONTRACT.

THREE LANES

Their power facts.Our result.

  1. 01

    External authorities

    Decided by others.

    Planning approval, the grid connection process, market performance standards, commissioning and permission to energise. The parties supply them; CANUS records them as connected requirements and decides none of them.
  2. 02

    Operating systems

    Operates, monitors, reports.

    Data-centre monitoring, building and electrical management, control systems, equipment telemetry and the customer's own tests. They give context for the check; they are not the result. CANUS replaces none of them.
  3. 03

    Independent delivery checks

    Agree. Check. Sign. Keep.

    The evidence needed is agreed before equipment is ordered. CANUS independently checks the delivered system when a phase is delivered, signs one result, and links every later record to it.

CANUS DOES NOT APPROVE CONNECTIONS, VERIFY NETWORK CAPACITY, AUTHORISE POWER SWITCH-ON OR DECIDE ANY GRID MATTER. NOTHING HERE MONITORS ANYTHING: PARTIES SUPPLY; CANUS RECORDS.

CANUS does not replace your operating systems.The parties stop having to take those systems' word for delivery.

ACCOUNTABILITY

Independent evidence.Direct accountability.

  1. 01

    Agreed requirements

    The standard we check against comes from the parties' own agreement, fixed before delivery. CANUS designs the check, never the standard.
  2. 02

    Programme fees

    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. CANUS holds no position in any transaction it checks and moves no money.
  3. 03

    A direct duty to answer

    Under the CANUS appointment, each organisation named to use the result can ask us to explain the evidence for its agreed use, without the payer's permission or first proving an error. We must respond, correct the record where needed, and identify unresolved questions or further work. The history is preserved.
  4. 04

    A continuing history

    Every signed result enters the CANUS Register. Later deliveries, changes and replacements receive linked records. Nothing is erased.

The company paying for the programme cannot veto a named organisation's right to question our evidence.

BOUNDARIES

What CANUS is.And is not.

CANUS IS

  • 01The programme around a cloud operator's AI infrastructure project
  • 02Scoping, bringing partners in and coordination in LARUS
  • 03Independent delivery checks with a scope set by the contract
  • 04Signed results for the organisations named to use them
  • 05A Register of what was delivered and what still applies

CANUS IS NOT

  • 01A replacement for DCIM, BMS or EPMS
  • 02A continuous utilisation dashboard
  • 03A general performance benchmark
  • 04A commissioning contractor
  • 05A financier, supplier or builder of what it coordinates
  • 06A marketplace, a token or a cloud of its own
  • 07A lender, insurer, escrow agent or rating agency
  • 08A system that guarantees payment or delivery
  • 09A grid connection adviser, or the applicant's engineer
  • 10An electricity supplier or grid operator
  • 11An authority that approves connections or permission to energise

The operator remains responsible for operations. CANUS is authoritative only for its own signed evidence.

Putting a project together?Start here.

Bring CANUS in while the design and the partners can still change: scoping, partners and requirements are far easier to agree before equipment is ordered.

See an example