AI Inference,
25–32% Less Energy,
33% More Capacity.

vert-suite autonomously co-optimises CPU and GPU power on bare-metal servers and in the cloud (validated on AWS EC2), achieving energy savings without changes to your software or hardware. Every watt saved is either cash back or extra capacity: fit around a third more GPUs into the power budget you already have.

−32%
Energy per token, CPU+GPU (bare metal)
+33%
GPUs on the same power budget (bare metal)
−25%
GPU energy per year on AWS EC2
Zero
App changes required
GPU+CPU Efficiency · Empirical Benchmarks

Proven Savings
at Scale

Bare-metal results are measured at the server wall-socket with a UNI-T UTE9811+ power analyser. Cloud results (AWS EC2) come from GPU power readings via nvidia-smi and cover the GPUs only.

41%
Peak Server Power Reduction (case study, measured at wall-socket)
2,418 kWh
Saved per GPU per Year · CPU+GPU, Eager profile · NVIDIA Blackwell
Bare Metal
AWS EC2 g7e
Validated on-premises and in the cloud · vLLM 0.26 · llama.cpp
Measured at Wall-Socket
On bare metal, whole-server Watt-second readings are taken at the wall-socket with a power analyser, not estimated from TDP. On AWS, where the plug is out of reach, GPU energy is sampled 10× per second via nvidia-smi.
Out-of-Band Validation
Independent telemetry path verifies results separate from the vert-suite control plane, so no figures are self-reported.
Like-for-Like Baselines
Every result compared against an unoptimised, state-of-the-art baseline on identical hardware under identical load.
Live Toggle Verification
Savings confirmed by enabling/disabling vert-suite mid-run and observing real-time power and throughput transitions.
Open-source data collection · verticular/ute9811-mqtt-bridge
The software used to sample power readings from the analyser is publicly available, giving full transparency on how the data was collected.
The Challenge

AI Inference Is Energy-Hungry

On cutting-edge Blackwell GPUs, each generated token carries a significant energy cost. With millions of tokens processed daily, that adds up fast. And without active optimisation, both CPU and GPU hardware are left running at full speed regardless of actual workload demand. Below: three production models on two GPUs, at 30 concurrent sessions per GPU, with and without vert-suite.

Bare Metal · CPU + GPU · Measured at Wall-Socket

2× RTX Pro 6000 Blackwell Workstation Edition with an Intel Xeon w7-3455 host, vLLM 0.26. Whole-server energy per generated token, without vert-suite (SotA) and under the Base and Eager profiles.

Gemma 4 31B
DP 2 · TP 1 · 30 sessions per GPU
SotA
1.27
Ws / token
 
20.80
tps / user
 
Base
0.97
Ws / token
−23.1%
20.25
tps / user
−2.7%
Eager
0.86
Ws / token
−31.8%
18.56
tps / user
−10.8%
Qwen 3.6 27B
DP 2 · TP 1 · 30 sessions per GPU
SotA
1.11
Ws / token
 
23.67
tps / user
 
Base
0.81
Ws / token
−26.8%
23.15
tps / user
−2.2%
Eager
0.76
Ws / token
−31.9%
21.44
tps / user
−9.4%
Laguna S 2.1 NVFP4
DP 1 · TP 2 · DFlash speculative · 60 sessions · CPU left at default
SotA
0.37
Ws / token
 
76.01
tps / user
 
Base
0.31
Ws / token
−17.3%
71.52
tps / user
−5.9%
Eager
0.30
Ws / token
−18.6%
69.72
tps / user
−8.3%
Cloud · AWS EC2 g7e.12xlarge · GPU Only

2× RTX Pro 6000 Blackwell Server Edition, vLLM 0.26. On AWS only the GPUs are optimised and measured (nvidia-smi); host and cooling savings are not included.

Gemma 4 31B
DP 2 · TP 1 · 30 sessions per GPU
SotA
0.73
Ws / token
 
19.30
tps / user
 
Base
0.57
Ws / token
−21.1%
18.68
tps / user
−3.2%
Eager
0.55
Ws / token
−24.5%
18.32
tps / user
−5.1%
Qwen 3.6 27B
DP 2 · TP 1 · 30 sessions per GPU
SotA
0.64
Ws / token
 
21.54
tps / user
 
Base
0.50
Ws / token
−21.2%
20.98
tps / user
−2.6%
Eager
0.48
Ws / token
−25.1%
20.54
tps / user
−4.6%
Laguna S 2.1 NVFP4
DP 1 · TP 2 · DFlash speculative · 60 sessions
SotA
0.23
Ws / token
 
64.33
tps / user
 
Base
0.19
Ws / token
−17.3%
61.03
tps / user
−5.1%
Eager
0.18
Ws / token
−21.1%
59.34
tps / user
−7.8%
Scaling Under Load · Earlier Single-GPU Study
Throughput & Energy Efficiency vs. Parallel Requests

In an earlier study on a single GPU, vLLM serving Gemma 4 31B was targeted with 1–60 concurrent requests.† Every data point is the average of 20 independent runs, and energy per token fell by 27–33%. vert-suite operates under a self-imposed SLA of no more than 10% throughput reduction vs. the unmanaged baseline.

% Reduction: With vert-suite vs. Without vert-suite
Without vert-suite
With vert-suite
Throughput per Session (tokens / sec)
Energy per Token (Watt-seconds / token)

* Model cards: vLLM 0.26, open-ended coding prompts, max_tokens 500; figures are means, percentages against the SotA default on identical hardware (AWS: means over 100 runs). Bare metal: whole-server energy at the wall-socket, attributed per GPU. AWS: GPU-only energy via nvidia-smi. Laguna uses tensor parallelism over a non-NVLink interconnect, so vert-suite deliberately leaves the host CPU at its default setting.
† Scaling chart test system: NVIDIA RTX Pro 6000 Blackwell (96 GB VRAM), 24-core workstation, 128 GB RAM, 2,050 W PSU; all Watt-second readings at the server wall-socket.
  Results generated with vLLM version 0.20.1 (CUDA 13.0), request's max_tokens set to 500 to prevent queuing, thus focusing on the specifics of the GPU scaling behaviour.

The Solution

vert-suite

A production-ready software platform for autonomous GPU/CPU efficiency orchestration. It is inference engine agnostic and needs no hardware changes, application changes or manual tuning.

Autonomous CPU/GPU Optimisation

Autonomous bare-metal GPU and CPU management for AI/LLM workloads. Empirically validated energy savings of over 30% per token, with no changes to your application or inference stack.

Continuous SLA Spectrum

Specify your maximum acceptable throughput reduction. vert-suite automatically scans the GPU/CPU operating envelope and locks in the profile delivering the deepest energy savings within your constraint.

Green & Cost-Efficient

Reduce OpEx, extend platform lifespan, and lower your infrastructure's carbon footprint, without replacing or upgrading hardware.

Deep Monitoring with eBPF

Leverage eBPF for deep system observability with minimal operational disruption, complemented by physical out-of-band telemetry for independent power validation.

Zero-Trust, Kubernetes-Native

Least-privilege agents, just-in-time capabilities, and mTLS-secured control-plane traffic. Transparent telemetry with out-of-band validation for full auditability.

Seamless Integration

Inference engine agnostic: validated on vLLM and llama.cpp, and compatible with other leading engines. One inclusive library, cross-platform, cross-Linux/K8S distribution, deployable in minutes with no operators, scheduler extensions, or YAML modifications.

vert-suite does not need permanent root access

Tools that tune hardware settings usually run with permanent root access to the kernel, drivers and hardware. vert-suite runs its everyday components unprivileged and grants elevated access only briefly, for a fixed set of tasks.

Zero-Compromise Security Architecture

vert-suite is built on a strict principle of minimal authority. Instead of deploying a privileged monolith, the architecture is physically split: a standard unprivileged worker that requests just-in-time access only when needed, and only for the exact duration required.

vert-suite zero-trust security architecture
Secure Entry

Public key at a terminal: signature verification before any agent is admitted.

Restricted Access

Main agent operates as a standard worker within an unprivileged boundary; CAP_SYS_RAWIO and CAP_SYS_ADMIN never granted permanently.

Just-in-Time

A Security Escort briefly unlocks the required resource, completes the exact task, and immediately relocks, leaving no standing privileges.

Secure Comms

All control-plane traffic is encrypted via mTLS tunnels, with no plaintext communication between components.

Minimal Authority

Digital identity verification prevents any component from operating outside its authorised scope.

How it works
1

Install vert-suite

No YAML changes, no Kubernetes operators, no code modifications to your inference stack.

2

Set Your SLA

Tell vert-suite your maximum acceptable throughput reduction. It autonomously scans the full GPU/CPU operating envelope.

3

Savings Start Immediately

Real-time CPU/GPU co-optimisation locks in the deepest energy savings within your constraint.

Performance SLA Spectrum

You Set the Constraint.
We Find the Optimum.

vert-suite does not offer a fixed menu of profiles. It offers a continuous spectrum. Simply tell the software the maximum throughput reduction you can accept (say, no more than 5% or 10%) and it automatically identifies the optimal GPU/CPU operational mode to deliver the deepest possible energy savings within that constraint.

Less energy savedMore energy saved
Base
~5% TPS impact
Eager
~10% TPS impact

Two benchmarked profiles; any point on the spectrum is achievable

Base · 5 ± 2% TPS target

Minimal Impact

Keeps throughput within a few percent of baseline. Measured cost across three models on bare metal and AWS: 2–6% of tokens per second.

22–28%CPU+GPU energy saved per year · bare metal
22–24%GPU energy saved per year · AWS EC2
Eager · 10 ± 2% TPS target

Deeper Savings

A slightly larger throughput budget unlocks markedly deeper reductions. Measured cost: 5–11% of tokens per second.

25–39%CPU+GPU energy saved per year · bare metal
27–29%GPU energy saved per year · AWS EC2

Ranges span Gemma 4 31B, Qwen 3.6 27B and Laguna S 2.1 NVFP4 at 30 concurrent sessions per GPU, vLLM 0.26. Looser constraints push savings further (see the single-GPU llama.cpp benchmarks below).

Benchmark Results

Comprehensive Model Benchmarks

Multi-GPU vLLM benchmarks on bare metal and AWS EC2, plus single-GPU llama.cpp benchmarks across five open-weight models. Every result is compared against an unoptimised SotA baseline on identical hardware.

Technology Stack
RTX Pro 6000 Blackwell Intel Xeon w7-3455 AWS EC2 g7e.12xlarge vLLM 0.26 Llama.cpp vert-suite
Multi-GPU · vLLM 0.26 · Energy per GPU per Year

2× RTX Pro 6000 Blackwell at 30 concurrent sessions per GPU. Annual energy is what a GPU draws when left running for a year, including its share of the host CPU on bare metal.

Annual energy reduction (higher is better)
Base 
Eager
Gemma 4 31B
SotA: 6,925 kWh/yr per GPU (CPU+GPU, bare metal) · 3,690 kWh/yr per GPU (GPU only, AWS)
DP 2 · TP 1
Bare metalBase · CPU+GPU
−25.11% 5,186 kWh / GPU / yr
1,739 kWh saved / yr
−2.66% throughput
Bare metalEager · CPU+GPU
−39.17% 4,213 kWh / GPU / yr
2,712 kWh saved / yr
−10.76% throughput
AWS EC2Base · GPU only
−23.64% 2,818 kWh / GPU / yr
872 kWh saved / yr
−3.21% throughput
AWS EC2Eager · GPU only
−28.34% 2,645 kWh / GPU / yr
1,046 kWh saved / yr
−5.12% throughput
Qwen 3.6 27B
SotA: 6,915 kWh/yr per GPU (CPU+GPU, bare metal) · 3,599 kWh/yr per GPU (GPU only, AWS)
DP 2 · TP 1
Bare metalBase · CPU+GPU
−28.37% 4,953 kWh / GPU / yr
1,962 kWh saved / yr
−2.18% throughput
Bare metalEager · CPU+GPU
−38.33% 4,264 kWh / GPU / yr
2,651 kWh saved / yr
−9.41% throughput
AWS EC2Base · GPU only
−23.24% 2,763 kWh / GPU / yr
836 kWh saved / yr
−2.60% throughput
AWS EC2Eager · GPU only
−28.59% 2,570 kWh / GPU / yr
1,029 kWh saved / yr
−4.64% throughput
Laguna S 2.1 NVFP4 (DFlash)
SotA: 7,463 kWh/yr per GPU (CPU+GPU, bare metal) · 3,909 kWh/yr per GPU (GPU only, AWS)
DP 1 · TP 2 · speculative, 7 tokens
Bare metalBase · CPU+GPU
−22.21% 5,805 kWh / GPU / yr
1,657 kWh saved / yr
−5.90% throughput
Bare metalEager · CPU+GPU
−25.35% 5,571 kWh / GPU / yr
1,892 kWh saved / yr
−8.28% throughput
AWS EC2Base · GPU only
−21.58% 3,065 kWh / GPU / yr
844 kWh saved / yr
−5.13% throughput
AWS EC2Eager · GPU only
−27.22% 2,844 kWh / GPU / yr
1,064 kWh saved / yr
−7.75% throughput

* Bare metal: 2× RTX Pro 6000 Blackwell Workstation Edition, Intel Xeon w7-3455; whole-server energy at the wall-socket, attributed per GPU. AWS: g7e.12xlarge, 2× RTX Pro 6000 Blackwell Server Edition; GPU-only energy via nvidia-smi, excluding host and cooling. On Laguna (tensor parallelism without NVLink) the host CPU is deliberately left at its default setting.

Single GPU · llama.cpp · Energy per Token
Energy per token (Ws/token) reduction (energy saved, higher is better)
≤10% 
≤15% 
≤20% TPS impact
Model
Quantisation
Llama-3-70B-Instruct
Baseline: 39.15 Ws/token · 20.56 tps · Q8_0 · 75 GB
70B params
≤10% TPSConservative
−28.83% 27.87 Ws/token
19.97 tps
−2.87% throughput
≤15% TPSBalanced
−33.84% 25.90 Ws/token
19.50 tps
−5.17% throughput
≤20% TPSAggressive
−35.99% 25.06 Ws/token
18.02 tps
−12.34% throughput
Qwen2.5-72B-Instruct
Baseline: 40.84 Ws/token · 19.96 tps · Q8_0 · 77.5 GB
72B params
≤10% TPSConservative
−29.60% 28.75 Ws/token
19.39 tps
−2.86% throughput
≤15% TPSBalanced
−34.30% 26.83 Ws/token
18.94 tps
−5.11% throughput
≤20% TPSAggressive
−36.52% 25.93 Ws/token
17.48 tps
−12.42% throughput
Qwen3-32B
Baseline: 18.52 Ws/token · 42.04 tps · Q8_0 · 34.8 GB
32B params
≤10% TPSConservative
−28.07% 13.32 Ws/token
39.86 tps
−5.17% throughput
≤15% TPSBalanced
−32.58% 12.49 Ws/token
38.38 tps
−8.72% throughput
≤20% TPSAggressive
−33.75% 12.27 Ws/token
34.18 tps
−18.70% throughput
Qwen3.5-27B
Baseline: 26.99 Ws/token · 27.76 tps · BF16 · 50.7 GB
27B params
≤10% TPSConservative
−26.59% 19.82 Ws/token
26.13 tps
−5.88% throughput
≤15% TPSBalanced
−31.16% 18.58 Ws/token
25.32 tps
−8.80% throughput
≤20% TPSAggressive
−31.49% 18.50 Ws/token
22.82 tps
−17.81% throughput
Qwen3.5-35B-A3B
Baseline: 5.23 Ws/token · 114.58 tps · BF16 · 69.4 GB
35B MoE params
≤10% TPSConservative
−19.25% 4.22 Ws/token
103.11 tps
−10.01% throughput
≤15% TPSBalanced
−20.16% 4.18 Ws/token
99.28 tps
−13.36% throughput
≤20% TPSAggressive
−20.65% 4.15 Ws/token
94.82 tps
−17.25% throughput

* All Watt-second readings measured at the server wall-socket on a single NVIDIA RTX Pro 6000 Blackwell GPU server.

Case Study

Optimising Autonomous AI Agents

Continuous, zero-intervention AI agent loops create a sustained, demanding inference load. We validated vert-suite in exactly this scenario, using Claude Code acting as an autonomous coding agent running non-stop research iterations on a dedicated GPU server.

Technology Stack
Claude Code RTX Pro 6000 Blackwell vLLM Gemma 4 · 31B vert-suite
Average Server Power (measured at server wall-socket)
Without vert-suite 781 W
781 W
With vert-suite 459 W
459 W
~32%
Energy per token saved
~41%
Power Reduction with vert-suite on our testing server
~12%
Throughput reduction
What's happening
The Local Agent
Claude Code running locally, pointing to a GPU server: an RTX Pro 6000 Blackwell running vLLM and Gemma 4 (31B).
The Problem
Running an autonomous coding agent is power-hungry. The server was drawing 800 W+ to keep Gemma running at 19–22 tokens/sec.
The Fix
vert-suite applied. Power dropped to ~450 W, a ~41% reduction. Throughput only fell by 10–14%.
The Agent Loop
An extension of Karpathy's Autoresearch pattern: modify → evaluate → measure → keep or revert → repeat. Zero human intervention.
Click to Play Key moments
Optimisation ON: power usage drops sharply
Optimisation OFF: power climbs back to baseline
Optimisation ON again: confirms repeatability
What's on screen
Top Left
vLLM Logs
Right Half
Claude Code
Bottom Left
Agent Loop
Bottom Right
Power Trace

What 30% energy savings means in practice

Average UK commercial electricity rate: 25.5p/kWh · 24/7 continuous operation · Savings scale linearly with fleet size

£0 £5K £10K £15K £20K £23K
Workstation
2.5 kW · £5,585/yr
saves £1,675
per year
Mid-Range Server
6.25 kW · £13,961/yr
saves £4,188
per year
Enterprise Server
10 kW · £22,338/yr
saves £6,701
per year
Annual cost after savings
Saved with vert-suite (30%)
News & Recognition

Recognised by Industry Leaders

UKRI Logo

Innovate UK 'New Innovators' Grant

Verticular has secured the 'Growth Catalyst Early Stage' grant to advance EPIC (Energy-efficient Processing for Intensive Computing), using AI to dynamically manage both CPU and GPU power and cut energy costs for AI data centres without performance trade-offs.

NVIDIA Inception Logo

Member of NVIDIA Inception

We are proud members of the NVIDIA Inception programme, giving us early access to the latest GPU ecosystem and enabling us to optimise AI workloads at the deepest hardware level.

Partnering with

NVIDIA Inception Nokia MK Stadium Real Wireless Madevo UKRI Weaver Labs Hiro University of Bristol NVIDIA Inception Nokia MK Stadium Real Wireless Madevo UKRI Weaver Labs Hiro University of Bristol
The Team

Built by Industry Experts

Verticular was founded by two tech leaders who spent careers engineering at the frontier of wireless networks and AI systems, and who saw first-hand the cost and energy problem coming.

Dr Dan Warren
Dr Dan Warren
Chief Executive Officer
  • Former Director of Advanced Network Research at Samsung Research UK
  • Creator of the VoLTE standard at GSMA
  • dan@verticular.uk
Dr Andrea Tassi
Dr Andrea Tassi
Chief Technology Officer
  • Former Chief Engineer at Samsung Research UK
  • IEEE Senior Member · 50+ publications · Multiple Best Paper Awards. Specialist in System Design/Simulation
  • andrea@verticular.uk
"

Our mission is to solve the dual problem of rising cloud costs and the massive energy footprint of AI by building deep, chip-level software that lowers OpEx, maximises hardware ROI, and meets sustainability goals without compromising SLAs.

Contact Us

See Your Savings.
Live. On Your Hardware.

Book a 30-minute call and we'll show you wall-socket power measurements on a real GPU server, before and after vert-suite, so you can see the savings for yourself, not just take our word for it.

Calendar not loading? Book on cal.com