Decision model from H2O.ai, a full fine-tune of nvidia/NVIDIA-Nemotron-3.5-Bolt-74B-A9B-24GB. It answers typed decision questions about a record or an image: pick one of up to 255 named options, give the probability that a statement is true, or return an ordinal score with its probability distribution. It has 74B parameters with 9B active and runs on one NVIDIA RTX PRO 6000 96GB card with vLLM and b12x kernels. Weights are gated and released under the H2O Model Non-Commercial Licence v1.1, so non-commercial, non-production use only. It scores 65.51 on the Decision Index.
A workable 74B-parameter MoE decision model from H2O.ai. Treat the modality benchmarks above as the leading indicator of fit — composite scoring across modalities is still maturing.
Generated from this model’s benchmarks and ranking signals. Editor reviews refine it over time.
Access model weights, configuration files, and documentation.
The top devices for this model at 4-bit, ranked by fit and speed.
| Device | Grade | VRAM |
|---|---|---|
| Acer Veriton GN100 AI MiniAcer | SS | 43.7 GB |
| AI TOP ATOM ATAGB10-9003Gigabyte | SS | 43.7 GB |
| AMD Instinct MI300XAMD | SS | 43.7 GB |
| AMD Instinct MI325XAMD | SS | 43.7 GB |
| AMD Instinct MI350PAMD | SS | 43.7 GB |

Explore the Provider
Aggregate stats, leaderboard, release timeline, and benchmark coverage across every H2O.ai model we track.
Benchmark data sourced from: Hugging Face, Arena.ai, Artificial Analysis.
H2O-Lightning-Bolt-74B v1.1 is a specialized decision model developed by H2O.ai, built as a full fine-tune of nvidia/NVIDIA-Nemotron-3.5-Bolt-74B-A9B-24GB. Unlike generative conversational models that output conversational text, this model functions as an automated evaluation and classification engine. It operates on a Mixture of Experts (MoE) architecture with 74 billion total parameters and 9 billion active parameters per forward pass, earning a score of 65.51 on the Decision Index benchmark.
The model is engineered to resolve typed decision questions against structured records, text transcripts, and policies. Rather than generating multi-token prose explanations, it outputs exact probabilities across predefined categories: selecting from up to 255 discrete options, evaluating the truth value of a statement, or returning an ordinal score alongside its full probability distribution. Because it outputs calibrated logprobs rather than descriptive text, inference bypasses standard autoregressive decoding bottlenecks.
The model weights are gated on Hugging Face under the H2O Model Non-Commercial Licence v1.1. This restricts deployment strictly to non-commercial research, academic evaluation, and local experimentation. For engineers looking to run H2O-Lightning-Bolt-74B v1.1 locally, it provides high-capacity routing and decision-making without the compute penalty typical of dense 70B-class models.
The architecture of H2O-Lightning-Bolt-74B v1.1 balances deep parameter capacity with low runtime compute via sparse expert routing. Built directly upon NVIDIA's Nemotron-3.5 MoE architecture, the network maintains 74B total parameters distributed across specialized feed-forward layers, but routes each token to just 9B active parameters during execution.
This split delivers notable H2O-Lightning-Bolt-74B v1.1 MoE efficiency. While the model retains the broad representational capacity of a 74B network, the memory bandwidth and compute required during the forward pass match that of a compact 9B dense model.
Key technical characteristics include:
IQ2_XXS 2-bit quantization on the routed experts, while preserving BF16 precision on the dense self-attention layers and activations.b12x kernels designed specifically to accelerate low-bit expert selection and matrix multiplication.H2O-Lightning-Bolt-74B v1.1 is not a conversational chatbot or a code generator. It is designed specifically for automated document triage, policy enforcement, and record classification.
The model handles three primary query types:
Practical local use cases include:
Deploying this model locally requires an understanding of its unique runtime dependencies. Because the experts are quantized to 2-bit using custom layouts, standard GGUF loaders like unpatched llama.cpp or default Ollama builds cannot run the native weights without prior conversion.
The raw model weights occupy roughly 32.2 GiB of memory. However, operational VRAM requirements depend heavily on context length and concurrency:
If you are wondering how to run 74B model on consumer GPU setups, running the native IQ2_XXS checkpoint on a single 24GB RTX 4090 is impossible due to the 32.2 GiB weight size. You must pool at least two 24GB cards or run an offloaded quantization on high-RAM Apple Silicon (such as an M3 Max or M4 Max with 64GB or 128GB of unified memory).
The native release uses the b12x library with specialized vLLM kernels. The upstream release includes an execution script (serve.sh) and a lightweight Python shim (lightning_bolt_shim.py) that exposes two local endpoints:
POST /v1/systemone: Internal raw decision endpoint.POST /v1/decisions: An OpenAI-compatible endpoint accepting decision schemas.For users seeking the best quantization for H2O-Lightning-Bolt-74B v1.1 in non-vLLM stacks, community GGUF conversions (typically Q4_K_M or Q3_K_L) are standard. A standard Q4_K_M quant would push the total model size closer to 42-45 GiB, which requires at least 48 GB to 64 GB of unified system memory or dual enterprise GPUs. If community GGUF quantizations become accessible in your environment, Ollama offers the quickest route for local testing, provided your machine has the memory to handle a 74B-class model.
Because the model outputs only 1 token per question, traditional H2O-Lightning-Bolt-74B v1.1 tokens per second metrics do not reflect how the system behaves. Instead, performance is measured in requests per second (RPS) and latency:
Evaluating H2O-Lightning-Bolt-74B v1.1 against alternative models requires separating generative text engines from structured decision systems.
Meta's Llama 3.1 70B is a dense conversational model. Running Llama 3.1 70B requires computing all 70 billion parameters for every single token generated. If you prompt Llama 3.1 70B to evaluate a record and output JSON, it generates dozens of tokens explaining its answer, introducing latency, high VRAM consumption, and potential parsing errors.
H2O-Lightning-Bolt-74B v1.1 activates only 9 billion parameters per token. It outputs the classification logprobs directly in a single step, yielding lower latency and eliminating parsing failures. However, Llama 3.1 70B is licensed for commercial use and can write open-ended text, whereas Bolt-74B cannot generate open-ended answers and is strictly non-commercial.
Mixtral 8x22B is an open-weights MoE model containing roughly 141B total parameters and activating approximately 39B per token. Mixtral provides strong reasoning, multilingual capabilities, and standard chat functionality, but requires roughly 80 GiB of VRAM even at 4-bit quantization, with much higher FLOP requirements during generation.
Bolt-74B v1.1 is significantly smaller in memory footprint (32.2 GiB on disk) and vastly cheaper to compute (9B active parameters). As a local AI model 74B parameters 2026 release, Bolt-74B is the superior choice for deterministic triage and automated categorization pipelines on workstation hardware, provided the commercial license restrictions fit your research requirements. Choose Mixtral or dense Llama variants if you require narrative summaries, coding, or commercial deployment.
Cheapest current cloud rentals with at least 44 GB VRAM, refreshed hourly.
Advertising disclosure: we earn commissions when you shop through the links below.
| Option | Cost / GPU-hour |
|---|---|
NVIDIA A100 80GB PCIeVast.ai · Spot · 80 GB VRAM | $0.29 |
NVIDIA RTX A6000RunPod · Community · 48 GB VRAM | $0.33 |
NVIDIA RTX PRO 5000 BlackwellVast.ai · Spot · 48 GB VRAM | $0.40 |
NVIDIA A100 80GB SXMVast.ai · Spot · 80 GB VRAM | $0.40 |
NVIDIA L40Vast.ai · Spot · 48 GB VRAM | $0.40 |
Per-GPU rate across RunPod, the Vast.ai marketplace, DigitalOcean, and Vultr.
Spot tier is interruptible. Plan for restarts when comparing against on-demand prices.