Skip to main content

Who we build for

AI for Research programmes

Research computing has a requirement commercial work does not: the run has to be repeatable. A figure in a paper must be reproducible years later, which means the model version, the parameters and the input set all have to be recorded and pinned rather than silently upgraded underneath you.

That is how we run these deployments. Model versions are pinned for the life of a programme, each run produces a record you can cite in a methods section, and capacity is scheduled so a six-week corpus job does not compete with interactive work. Grant timelines and budgets are fixed, so the sizing is done against your actual corpus before anything is committed, and dedicated capacity is cheaper than metered pricing at the volumes research generates.

Talk to an engineer Pricing

Services that apply

The services research programmes commission most often, grouped by material type. Each links to its own page with the models, hardware and throughput behind it.

{{ filterNote }}

Corpus digitisation

Turning archives, collections and field material into machine-readable data.

Annotation and extraction

Producing the structured data an analysis actually runs on.

Audio and video corpora

Interviews, recordings, broadcast archives and field footage.

Images and observation

Imaging collections, instrument output and observational footage.

Ethics and disclosure

What an ethics committee will ask about before the data can be used or shared.

  • PII detection and redaction

    Anonymising a corpus so it can be shared or deposited, measured on what it misses rather than on average accuracy.

  • Document redaction

    Producing a release copy where removed material is genuinely gone, not hidden under a rectangle.

  • Face detection / face count

    Finding faces so they can be blurred, without identifying anybody — the usual requirement for footage in a publication.

Bring your own model

Research programmes usually arrive with their own model — trained on the group’s own data, published alongside a paper, or inherited from a collaborator. It runs on Super-GPU infrastructure with the same pinned versions and per-run records as our own services.

We help you select the right hardware, containerize and deploy the workload, build the processing pipeline and define the infrastructure required to scale it.

Your model. Your data. Your deployment choice.

Bring your existing GPU containers

We support standard Linux GPU workloads including:

  • Docker
  • OCI images
  • NVIDIA CUDA
  • vLLM
  • TensorFlow
  • PyTorch

and other GPU-enabled environments. Images can be uploaded directly or pulled from registries including AWS ECR, Docker Hub, GitHub Container Registry, Google Artifact Registry, Azure Container Registry, Harbor and private registries.

Where it runs

Funder and ethics conditions usually decide where processing happens, and the options cover the range they require.

On premises, in your AWS account, GCP project or OCI tenancy, on Super-GPU Cloud, or across a hybrid environment that keeps latency-sensitive work local and reaches for cloud GPU capacity when scale demands it. You control where data is processed, stored and retained.

All AI services Pricing