GPU RIGS Private AI systems · UK
Menu
Servers Compare all serversTeam 32Core 48Business 128Sovereign 192Scale 384Specialist Company 64Custom specification
Solutions Private AI serversPrivate chat & RAGAI codingRendering & batchFor legal teamsFor engineering
Why private AI Why own capacity?Private vs cloudSecurity & data controlOpen-source softwareFinance & tax context
Crypto & blockchain Crypto & blockchain overviewGPU mining rigsMining configuration serviceBlockchain infrastructureMining ROI calculatorGPU-mineable tokensMining exit strategiesMining FAQs
Learn Buyer guidesServer sizing toolTCO calculatorAI ownership calculatorElectricity calculatorEvidence methodPrivate AI questions
About Plan your server

A controlled supply boundary

From workload brief to tested handover - without hidden promises.

The initial offer is a configured appliance supplied for collection or pallet delivery with remote onboarding. It is not nationwide on-site installation, open-ended integration or a 24/7 managed service.

Decision in one minute

Proceed when the customer can own the site, network and daily operation. Use qualified partners where electrical, rack, HVAC or local hands are required.

Diagram showing an approved request, a local service, an approved store and a policy-controlled data path
Diagram showing an approved request, a local service, an approved store and a policy-controlled data path
A private deployment starts with the permitted data path, access policy and logging boundary. Original explanatory plate. It sets out a decision method, not a measured result.
A private deployment starts with the permitted data path, access policy and logging boundary.

Operational ownership

The handover should make responsibility easier to see.

01 / Owner
Name who controls updates, access, recovery and incidents.
02 / Record
Make versions, tests and handover evidence visible.
03 / Exit
Keep portability and supplier boundaries written down.
GPU server remote management dashboard with system status, access logs and sensor monitoring panels
GPU server remote management dashboard with system status, access logs and sensor monitoring panels
Supplier screenshot of the platform management interface. The final management features and access policy depend on the ordered system. OEM supplier reference image. Written reuse permission pending.
Supplier screenshot of the platform management interface. The final management features and access policy depend on the ordered system. OEM supplier reference image. Written reuse permission pending.

Ten visible steps

Fit check, recommendation, representative proof, exact quote, deposit, procurement, configuration, verification, handover and optional care are recorded as separate stages.

The order identifies where responsibility changes hands and what evidence is expected at acceptance.

Change record

A controlled change leaves an evidence trail

  1. Request Reason, owner and affected service.
  2. Test Focused acceptance and rollback plan.
  3. Approve Named person accepts the change.
  4. Record Version, date and result retained.
Silent model, runtime or access changes make later assurance harder. Decision aid for: Ten visible steps

Look behind the claim at the operating record.

Management, recovery, evidence and physical serviceability make responsibilities easier to inspect at handover.

Diagram showing approved documents moving through a searchable index to an answer with a source citation
Diagram showing approved documents moving through a searchable index to an answer with a source citation
A retrieval workflow should connect each useful answer to approved source material and defined refusal behaviour. Original explanatory plate. It sets out a decision method, not a measured result.
A retrieval workflow should connect each useful answer to approved source material and defined refusal behaviour. Original explanatory plate. It sets out a decision method, not a measured result.
Diagram of an evidence pack containing an asset schedule, burn-in record, health readings, workload test and admin guide
Diagram of an evidence pack containing an asset schedule, burn-in record, health readings, workload test and admin guide
A credible handover records the supplied assets, checks, operating evidence, instructions and unresolved items. Original explanatory plate. It sets out a decision method, not a measured result.
A credible handover records the supplied assets, checks, operating evidence, instructions and unresolved items. Original explanatory plate. It sets out a decision method, not a measured result.

Verification before dispatch

The exact build receives a serialised BOM, firmware/version record, minimum 24-hour GPU/CPU/memory/storage stress, temperature and error evidence, boot/reboot and remote-management checks, drive/network tests and agreed model/runtime smoke tests.

Performance claims are published only after the reference configuration has corresponding conditions and results.

Recovery boundary

Recovery spans equipment, configuration and business data

  1. Equipment Hardware fault and warranty route.
  2. System Build record, settings and secrets.
  3. Data Backup, retention and restore authority.
  4. Service Fallback, incident and return to use.
A backup claim is incomplete until restoration ownership and a test route are clear. Decision aid for: Verification before dispatch

What delivery does not include

Building electrical work, rack/UPS/HVAC, structured cabling, customer-data migration, every application integration, continuous monitoring and 24/7 response are excluded unless separately quoted.

This protects the customer from an ambiguous project and protects the price from unbounded delivery work.

Exit path

Ownership should preserve a practical route out

Export Data, settings and useful records.
Rebuild Documented components and versions.
Replace Alternative runtime or supplier route.
Close Deletion, access removal and asset handling.
Portability still needs testing. Open components do not remove migration work. Decision aid for: What delivery does not include

Optional care remains scoped

Proposed annual plans can cover periodic health reviews, update advice, tested windows and defined business-hours support. Their capacity and margin must be validated before sale.

Hardware warranty, software support and data-controller responsibility are always described separately.

Questions answered

Straight answers to common questions

Do you install servers anywhere in the UK?

The initial offer does not include national on-site installation. Collection, pallet delivery and remote onboarding are the defined baseline.

What happens before dispatch?

The exact agreed build is configured, burn-in tested and documented, with model/runtime smoke tests defined in the order.

Is support included?

Remote onboarding and a 30-day configuration-defect window are proposed. Ongoing support plans are separate and subject to final capacity and terms.

Continue the decision

Useful next steps

Configure a brief

Start with workload and site conditions.

 Security responsibilities

Know what changes at handover.

 Compare packages

See the proposed inclusions and constraints.

Put the claim to work

Turn this guidance into a testable requirement.

The brief asks about workload and operating conditions - not just budget.

Plan your requirements Compare proposed systems