Skip to content

KVARK Infrastructure

Hardware and operations, under your control.

Run KVARK on LM TEK servers or your own compatible Kubernetes infrastructure, choose its deployment model, and manage its hardware, environments and releases.

Run KVARK on LM TEK servers or your own compatible Kubernetes infrastructure, in the deployment model you choose.

Business value

Dense compute that asks less of your facility

In its specified configuration, the LM TEK server is liquid-cooled inside its chassis. You need no facility water or external cooling distribution unit, and fewer data-room changes. It aims to use less energy and give off less noise and heat, which can lower your costs.

Room to grow on infrastructure you choose

Run KVARK on compatible Kubernetes infrastructure and grow it by adding servers. KVARK places its services and models wherever there is capacity, following placement policies, so your hardware is better used and less needs managing by hand.

The LM TEK server

Put up to eight NVIDIA H200 GPUs to work in one LM TEK 4U server, KVARK’s primary hardware option. Its liquid cooling helps keep chip temperatures stable.

Up to eight NVIDIA H200 GPUs in one liquid-cooled 4U server, KVARK’s primary hardware option.

  • In the specified configuration, the whole server draws about 6 kW.
  • That configuration also supports operation at 30 °C ambient.
  • The facility provides ventilation and heat removal, sized to the installed load.

Fig. 2 · The LM TEK server

Deployment options

Choose where KVARK runs, on LM TEK servers or your own compatible Kubernetes infrastructure, and the deployment model that suits your operational and data requirements.

Choose your deployment model: on premises, private or hybrid cloud, or air-gapped with offline-ready components and integrations.

  • On premises, or in a private or hybrid cloud.
  • Air-gapped: fully isolated, with components and integrations fit for offline use.

Sketch · where KVARK can run

Infrastructure management

Monitor the hardware and systems KVARK runs on and allocate their resources. Get alerts and manage incidents when something goes wrong.

Monitor hardware and systems, allocate resources, get alerts and manage incidents.

  • Administer the infrastructure, with reports and analytics.

Example · hardware monitoring

Environments and releases

Keep development and testing apart from production: run DEV, TEST and PROD, and move changes between them with CI/CD and controlled migration.

Run DEV, TEST and PROD, and move changes between them with CI/CD and controlled migration.

  • Agree system updates with platform administration, to suit operational needs.

Sketch · from DEV to PROD

Business value

Dense compute that asks less of your facility

The LM TEK server’s specified configuration needs no facility water and fewer data-room changes. It aims to use less energy, which can lower costs.

Room to grow on infrastructure you choose

Grow compatible Kubernetes infrastructure by adding servers. KVARK places services and models by capacity and placement policies, so your hardware is better used.

Start with one use case. Run it under your rules.

We show KVARK on your kind of documents, your access rules and your deployment constraints. Most teams start with a four to six week analysis and a six week pilot.

We show KVARK on your kind of documents, access rules and deployment constraints.