GPU compute.
Private AI.

Rent GPUs for a project, reserve capacity for ongoing work, or host a private AI model in the UK or on your premises. For businesses and research teams.

GPU hosting live on Vast.aiHosted in the UK or on your premises

Compute services.

Run your own software on rented GPUs, or ask us to scope a managed deployment.

On-demand compute

Short-term GPU access for experiments, model evaluation, rendering or a fixed project; you run your own software.

Reserved capacity

An agreed single- or multi-GPU allocation, on a defined term, for recurring jobs or a service.

Private AI systems

A private model hosted for you in the UK or run on your premises, from model and hardware choice to deployment, with application integration if you need it.

Typical work: research runs and parameter sweeps, simulation and engineering solvers, LLM serving and supported adapter fine-tuning, internal assistants and document search, training your own computer vision models, and rendering or batch processing.

Prefer to manage your own instance? Our NVIDIA GB10 and RTX PRO 6000 systems are also rented through Vast.ai, at marketplace prices, availability and terms.

GPU configurations.

Choose around the workload: the model you need to serve, the number of simultaneous requests, or the solver you need to run.

RTX PRO 6000, single GPU

96GBper Blackwell RTX PRO 6000 GPU / GDDR7 ECC

LLM hosting, a development environment or a single-GPU job.

Best for LLM hosting, development, model evaluation, supported adapter fine-tuning, computer vision training and GPU rendering.

Discuss a single-GPU setup

RTX PRO 6000, multi-GPU servers

96GB / GPUSeparate memory on each GPU

More independent work, or a model distributed across GPUs.

Best for serving more simultaneous requests (one model copy per GPU), splitting a larger model or training run across GPUs where the software supports it, and running separate experiments, simulations or render jobs side by side.

Discuss a multi-GPU setup

H200 servers

141GBper NVIDIA H200 GPU / HBM3e

Memory-heavy inference and supported scientific workloads.

Best for memory-heavy LLM serving and double-precision (FP64) scientific and simulation software.

Discuss H200 capacity

GPU memory is not a model-size guarantee: the model, its active conversations and the software all need room, and separate GPUs do not pool memory automatically. Test your model or software on the chosen configuration before booking; for H200, confirm the variant, GPU count, interconnect and application support.

These are configuration options, not a live availability list; CPU, system memory, storage and networking are sized alongside the GPUs. Manufacturer specifications: RTX PRO 6000 / H200.

RTX PRO 6000 BlackwellH200 NVLServer Edition / 96 GB GDDR7 with ECC141 GB HBM3e

Edition

Parts list

RTX PRO 6000 Server Edition
  1. Form factor
    Full-height full-length, dual-slot
    Nominal dimensions (height x length)
    111.15 x 266.7 mm; additional installation clearance required
  2. Cooling
    Passive air-cooled; requires qualified ducted server airflow

    Use a server with the forced airflow required for this passive card.

  3. GPU architecture
    NVIDIA Blackwell / GB202
    CUDA cores
    24,064
    Tensor cores
    752 / fifth generation
    RT cores
    188 / fourth generation
  4. Graphics memory
    96 GB GDDR7 with ECC
    Memory interface
    512-bit
    Memory bandwidth
    1,597 GB/s
  5. Total board power
    Up to 600 W; configurable, system and cable requirements apply
  6. Auxiliary power
    1 x PCIe CEM5 16-pin

    Board power is configurable up to 600 W; the supported setting depends on the board, firmware, cabling and host system.

  7. Host interface
    PCIe 5.0 x16
    NVLink bridge
    Not supported
  8. Display connectors
    4 x DisplayPort 2.1b
    Display operation
    Disabled in factory-default display-off mode; display-on requires supported configuration

Parts list

H200 NVL
  1. Form factor
    Full-height, full-length, dual-slot PCIe card
    Nominal card dimensions
    111.15 mm high x 266.7 mm long; dual-slot width

    Allow additional installation space for cabling and airflow.

  2. Cooling
    Passive air-cooled heatsink; forced chassis airflow required

    Passive cooling means server-provided airflow.

  3. GPU
    NVIDIA H200 NVL
    Architecture
    NVIDIA Hopper
    Multi-Instance GPU
    Up to 7 instances; supported profiles depend on the software and platform
    Decode engines
    7 NVDEC and 7 JPEG engines
  4. Memory
    141 GB HBM3e
    Memory bandwidth
    4.8 TB/s
  5. Maximum TDP
    Up to 600 W, configurable within supported platform limits

    TDP applies to the GPU alone.

  6. Check auxiliary power cabling with the server manufacturer; GPU TDP is configurable up to 600 W within supported platform limits.

  7. Host interface
    PCIe 5.0 x16
    PCIe bandwidth
    128 GB/s total bidirectional
  8. GPU interconnect
    NVIDIA NVLink, up to 900 GB/s per GPU total bidirectional
    NVLink configurations
    Supported 2- or 4-GPU bridge configurations; compatible server layout and bridge hardware required

    Each GPU has its own memory; applications must support distributing work across cards to use them together.

LLM hosting & private AI.

Open-weight models for chat, code, documents and search, hosted for you on UK GPUs or run on your premises, for businesses that do not want confidential prompts or documents routinely sent to a public AI service.

What needs to fit in GPU memory
Simultaneous requests
6
Context length
4

A model loading successfully is not the same as serving it well under load. Longer conversations and more simultaneous requests change the memory budget and response time.

Models and serving engines.

Models change quickly. We help you choose from the latest options for your tasks, data, privacy needs and budget; a smaller model may need less hardware.

Before deployment we agree the model, version, licence and limits on conversation length and simultaneous requests, then test answer quality and response speed (time to first token and output speed) on the chosen hardware.

  • Chat, analysis & internal assistants

    Internal chat, summarisation and analysis.

  • Development tools & code assistance

    Code generation, explanation and repair.

  • Document understanding

    Reading text, tables and charts in document images.

  • Embeddings & reranking

    Semantic search: find and rank the documents most relevant to a question, alongside a language model.

We compare vLLM and SGLang on your model, GPU and request pattern rather than assume one is faster.

  • vLLM

    Schedules many simultaneous requests and manages their memory; serves generation and retrieval models.

  • SGLang

    Reuses prompt text that requests share, a candidate for repeated-context work, with distributed options for some models.

UK hosted, or on your premises.

Where your AI could run
UK-hosted deployment. Your team, in your business, reaches compute allocated to you in a UK data centre over an agreed secure connection. The AI model, GPU compute and approved business data sit inside a data boundary; access, tenant isolation, storage, logging, backups and administrator permissions are agreed before confidential information is moved.On-premises deployment. Your team, the local network and your on-site system (the GPU server running the AI model, the approved business data, and their power, cooling and networking) are all within your premises. A line to the outside, for external tools, updates and remote support, needs separate consideration.
UK hostedYour premises
Where the model runs

UK data centre. No server room needed: a selected model runs on compute allocated to you.

Your on-site system. A local model can process prompts and documents within your premises.

Where your data goes

Agreed secure connection. The AI model, GPU compute and approved business data sit inside a data boundary.

Local network. External tools, updates and remote support need separate consideration.

Who is responsible

Define the data boundary. We agree access, tenant isolation, storage, logging, backups, administrator permissions and which documents an assistant can retrieve before confidential information moves.

Plan the physical setup. We scope hardware, power, cooling, networking and handover with you; installation and ongoing management are agreed separately.

A private model alone does not guarantee confidentiality or regulatory compliance.

How we quote.

We already host customer workloads through Vast.ai and are bringing company-owned GPU servers into a UK data centre; you deal directly with Percepta about the hardware, deployment and support you need.

For research budgets and business projects, the useful number is the cost of getting the work done. We scope the resources and term before you commit.

Compute

GPU model and count, CPU allocation and system memory.

Data

Working storage, retention, backups and any transfer costs.

Time

The duration of on-demand compute, or the term of reserved capacity.

Support

Self-managed compute, deployment assistance or an agreed managed scope; support and maintenance are agreed up front.

Have an existing cloud estimate? Send it with your workload and we will compare equivalent resources; any saving depends on utilisation, software, support and data transfer.

A few practical details.

Can I rent for one project rather than a long contract?

Yes. Discuss short-term access with us, or rent one of our NVIDIA GB10 or RTX PRO 6000 systems through Vast.ai. Direct bookings are quoted and confirmed before the allocation starts; availability and minimum terms depend on the configuration. Capacity, maintenance windows, response times and any service level are set in your contract.

Will my simulation or model run faster on a GPU?

Only if the software can use the GPU effectively. We need the application and version, GPU support, licence conditions, precision requirements and a representative workload. Some simulations are CPU-bound or require a different class of accelerator. We can discuss a representative trial before you commit to a longer allocation.

Does private AI mean nobody else can access my data?

No. A local model changes where inference runs, but access permissions, administrator access, logs, external tools, backups and support still matter. We confirm the hosting location and data handling for your deployment, including storage, backups and any external services, and agree the deployment boundary with you; hosted and on-premises options have different responsibilities.

Can you build and install a system for our premises?

We can scope a local AI workstation or server around your use case. Hardware, software licensing, installation, network integration, training and ongoing support are confirmed separately in the proposal.

Are software licences, backups and managed support included?

Do not assume they are included in a GPU rental. Bring details of any commercial software or restricted datasets. Before the work starts, we confirm permitted use, customer responsibilities, any additional storage, backup or support services, and who manages the operating system, models, updates, backups and monitoring. Application work such as integration, document preparation, search indexing and permissions, and ongoing management, is scoped separately from GPU rental.

Tell us what you need to run.

A first conversation does not need a perfect specification: the software, deadline, budget and any data restrictions are a good start.

Contact us