CANUS

FOR LENDERS, INVESTORS AND INSURERS

Agreed conditions.Independent evidence.

For lenders, equipment-finance companies, infrastructure investors and insurers assessing an AI infrastructure project. CANUS coordinates agreed project requirements and provides independent delivery evidence for the decisions you identify. You retain your credit, investment or insurance decision.

Your institution owns the credit decision. CANUS remains accountable for its evidence.

See an example Record

We are developing the programme with prospective lenders and investors. Nothing on this page is an offer of available finance.

The build you would fund · drag, jump or play · pauses at the funding decision and the check

01The customers

It starts with signed customers.

AI companies with a real order. Kept separate from day one.

A cloud operator brings customers who have committed to buy computing power from this build. Each customer's order is kept separate from the start, so a strong total never hides a weak one.

StartGrow

WHO DOES WHAT

Evidence from canus.Decisions with you.

One agreed scope of checks, one signed record. And a clear line between what CANUS supplies and what your institution decides.

Evidence supplied by CANUS

  • 01Project coordination in LARUS
  • 02An agreed scope of checks and signed results
  • 03Who can use the result, for which decisions, and the delivery history
  • 04A direct duty to explain and correct our evidence

Decisions retained by the institution

  • 01Credit approval and repayment assessment
  • 02Security, advance rate and funding availability
  • 03Funding release and other conditions
  • 04Servicing, remedies and workout decisions

The decisions on the right never follow automatically from a result. A CONSISTENT result is evidence, not a credit approval.

CANUS · INSTITUTIONAL USE

FICTIONAL EXAMPLE

CANUS-EX-001

DELIVERY EXAMINATION

Result

Consistent · Signed
What was checkedExample delivery requirements for a contracted GPU capacity delivery
Agreed useDefined in the engagement terms for each named organisation
Earlier related recordNone. First delivery on this Register entry

Who can use the result

Reads the signed result against the agreed delivery requirements. The contract with the customer determines sign-off and billing.

EXAMPLE API RESPONSE
{
  "example": true,
  "record": "CCEC-EXAMPLE-0001",
  "segment": "EXAMPLE-PHASE-01",
  "event": "DELIVERY EXAMINATION",
  "state": "CONSISTENT",
  "scope": "Agreed delivery requirements",
  "predecessor_record": null,
  "permitted_use": "As specified in the appointment"
}

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

BEFORE COMMITMENT

Evidence first.Money second.

Define the projects, the questions each decision-maker needs answered, whether those questions can be checked at delivery, who may use the results, and the specific work the programme would supply. This does not prescribe your underwriting policy. It fixes what evidence exists when you apply it.

  1. 01

    Types of project

    The equipment, locations and delivery patterns the programme would cover.
  2. 02

    Questions per decision-maker

    What credit, security and servicing each need established. Named before any build.
  3. 03

    Can it be checked

    Whether each question can be checked at delivery, agreed with the parties in advance.
  4. 04

    Who can use the result

    Who may use the record, for which decision, and how they can question it.

DEFINED USES

One appointment.Every use defined.

The record states its result, what was checked and who may use it. Who can use the result and for which decisions, delivery of every result, correction rights and any agreed integration follow the appointment. Where an integration or capability is proposed rather than available today, it is labelled proposed.

CANUS can supply an agreed delivery-evidence task alongside your existing engineers and advisers. The programme defines what each answers.

DIRECT ACCOUNTABILITY

Accountable to you.Whoever pays.

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.

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

Start with the projects you fund.

Start with the types of projects you fund, the equipment and locations you consider, and the technical checks you already use. We will tell you plainly whether a CANUS programme fits.

See an example

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.