DeepSeek R1 Self-Hosting Cost per Million Tokens (2026 Guide)

Executive Summary

Self-hosting DeepSeek R1 is not a single price point, it is a hardware decision that happens to produce a cost per million tokens. The full 671 billion parameter model, of which only 37 billion parameters activate per token in its Mixture-of-Experts (MoE) design ^[1], needs roughly 700GB of memory in native FP8 precision or about 1.4TB if converted to BF16 ^{[2] [3]}. NVIDIA documents the full 671B R1 model running on a single server with eight H200 GPUs. The H20 is a distinct 96GB GPU, not a 141GB GPU, so it should not be presented as an interchangeable eight-GPU option without workload-specific validation of weight placement and KV-cache headroom ( NVIDIA NIM ( NVIDIA GPU support table.

Benchmarked, independently measured cost per million tokens for self-hosted inference varies enormously with batching strategy. SemiAnalysis's InferenceX benchmarking tool puts DeepSeek R1 inference on NVIDIA H100 at $1.365 per million tokens in a low-latency, low-batch configuration, rising to $4.864 at moderate concurrency and $15.692 at maximum interactivity per user, while the newer NVIDIA B200 cuts those figures to $0.113, $0.544, and $1.088 respectively at the same three operating points ^[4]. Renting the hardware itself runs from about $2.89 per hour for an H100 PCIe on RunPod ^[5] to $4.76 per GPU per hour on CoreWeave's HGX H100 nodes ^[6], up to $55.04 per hour for an 8x H100 AWS p5.48xlarge instance on-demand (Source: instances.vantage.sh), meaning a dedicated 16-GPU self-hosted cluster for the full model can run into the tens of thousands of dollars per month before any inference has occurred.

Against that backdrop, buying tokens from an application programming interface (API) looks inexpensive. DeepSeek's own API originally priced R1 (accessed via the deepseek-reasoner model name) at $0.55 per million input tokens (cache miss) and $2.19 per million output tokens, with cache hits falling to $0.14 per million tokens ^{[7] [8]}. Critically, as of the July 22, 2026 publication date of this report, DeepSeek has announced that the deepseek-chat and deepseek-reasoner model name aliases will be retired on July 24, 2026, rerouted to the newer deepseek-v4-flash thinking mode ^[9], a two-day window from this article's publication that makes the underlying question, whether to keep renting an API alias or to self-host the original open-weight model permanently, more urgent than usual. Third-party hosts of the original R1 weights show wide dispersion: prices vary up to 6.1x across providers, with DeepInfra the most affordable at $0.56 per million tokens and Together AI the most expensive at $3.40 per million tokens ^[10].

The verdict this report reaches is scale-dependent. A documented case study from LiftOff LLC found that self-hosting smaller distilled R1 variants on AWS cost $414 per month per GPU instance, dramatically more expensive than $20 per user per month for ChatGPT Plus at their under-100-user scale ^[11]. Self-hosting the full 671B model only becomes cost-competitive at high, sustained utilization, precisely the regime where SemiAnalysis benchmarks show B200-class hardware delivering sub-$0.15-per-million-token economics ^[12]. This report walks through the API baseline, the GPU hardware math, provider-by-provider pricing, and named real-world deployments to answer, precisely, what it costs to run DeepSeek R1 yourself.

Introduction and Background

DeepSeek R1 is an open-weight large language model released by the Chinese AI startup DeepSeek in January 2025, built on the DeepSeek-V3 base model and trained with large-scale reinforcement learning to produce step-by-step reasoning chains before answering ^[13]. Both the model weights and the accompanying code repository are released under the permissive MIT License, which explicitly allows commercial use, modification, and distillation into other models ^[14], a commitment DeepSeek reiterated at launch by describing the release as "open for the community to leverage model weights & outputs" ^[15]. That licensing is precisely why "self-hosting cost per million tokens" is a question worth asking at all: unlike a closed model such as GPT-4 or Claude, there is no contractual requirement to buy tokens from the original vendor. Anyone with sufficient hardware and the technical capacity to run inference software such as vLLM or SGLang can download the weights and operate the model indefinitely, even after DeepSeek itself changes its own hosted product line.

That last point has immediate relevance. As of this report's July 22, 2026 publication date, DeepSeek's official pricing page confirms that the deepseek-reasoner model alias, the API name that has always pointed to R1 reasoning behavior, will be deprecated on July 24, 2026 and rerouted to the "thinking mode" of the newer deepseek-v4-flash model ^[9]. That does not delete the original R1 weights from Hugging Face, where they remain permanently downloadable, but it does mean that anyone relying on DeepSeek's hosted API to get R1-specific behavior will soon be served a different underlying model whether they intend that or not. For teams that specifically need R1's original reasoning traces, whether for reproducibility, benchmarking, or regulatory documentation, self-hosting the archived weights is the only way to guarantee the exact same model continues to run after the API cutover.

The economics of that choice hinge on two separate cost curves that this report treats as distinct: the price of buying tokens from DeepSeek's own API or from a third-party host, and the price of renting or owning the GPU capacity to run the 671B parameter model (or one of its smaller distilled variants) on one's own infrastructure. DeepSeek's own technical report states the full model needs 2,048 NVIDIA H800 GPUs for training over roughly two months (Source: dev.to), a figure unrelated to inference but illustrative of the model's scale. Inference is materially cheaper than training but still demands a dedicated multi-GPU cluster for the full-size model, which is the central hardware constraint this report quantifies section by section, covering API pricing, GPU requirements, cost-per-million-token math drawn from independently benchmarked data, and named deployments that have actually attempted the self-hosting calculus in production.

DeepSeek R1 API Pricing: The Baseline Before You Self-Host

Before evaluating whether self-hosting makes sense, it is necessary to establish what DeepSeek itself, and the ecosystem of third-party hosts, charge for R1 tokens through a standard API. At its January 2025 launch, DeepSeek priced R1 access (via the deepseek-reasoner model parameter) at $0.14 per million input tokens on a cache hit, $0.55 per million input tokens on a cache miss, and $2.19 per million output tokens ^{[16] [8]}. For context on how aggressive that pricing was, OpenAI's directly comparable reasoning model at the time, o1, was officially priced at $15.00 per million input tokens, $7.50 per million cached input tokens, and $60.00 per million output tokens ^{[17] [18]}, meaning R1's output pricing undercut o1's by more than 27x at list price, a gap independent analysis has also confirmed ^[19].

That original pricing, however, is now a historical artifact of the API rather than a permanent commitment. DeepSeek's current pricing documentation states plainly that the deepseek-chat and deepseek-reasoner model names will be deprecated on July 24, 2026 at 15:59 UTC, with both names remapped to non-thinking and thinking modes of deepseek-v4-flash respectively for backward compatibility ^[20]. Current-generation deepseek-v4-flash pricing sits at $0.14 per million input tokens on a cache miss and $0.28 per million output tokens, with cache hits as low as $0.0028 per million tokens ^[21], while the larger deepseek-v4-pro model runs $0.435 input (cache miss) and $0.87 output per million tokens ^[22]. Both current models expose a 1 million token context window with a maximum output of 384K tokens ^[23].

Because the open-weight R1 model remains downloadable regardless of what DeepSeek's own API serves, a secondary market of third-party hosts continues to offer the original architecture at independently set prices, and this is where the "R1 vs GPT-4 cost comparison" and "DeepSeek R1 open source pricing" questions actually get resolved in the market. Artificial Analysis, which benchmarks API providers directly, found 6 providers actively serving "DeepSeek R1 0528," the most recent open R1 checkpoint, with blended pricing (a 7:2:1 cache-input-output ratio) ranging from DeepInfra at $0.56 per million tokens to Together AI at $3.40 per million tokens, a 6.1x spread ^[10]. DeepInfra's specific input and output rates are $0.50 per million input tokens and $2.15 per million output tokens, the lowest of the tracked providers ^{[24] [25]}. Notably, Together AI's current public pricing page no longer lists a standalone DeepSeek R1 entry at all, offering only the newer DeepSeek V4 Pro at $1.74 per million input tokens and $3.48 per million output tokens ^[26], a sign of how quickly the hosted-model landscape consolidates around newer releases even as the original R1 weights remain independently available. Microsoft Azure's Foundry Models catalog lists DeepSeek R1 Global at $1.35 per million input tokens and $5.40 per million output tokens on a pay-as-you-go basis ^[27], and aggregator OpenRouter reports a weighted average input price of $0.794 and output price of $2.67 per million tokens across its connected providers over the past 30 days ^{[28] [29]}. This dispersion, driven by different hardware, quantization, and margin choices among hosts, is the direct market signal that self-hosting is attempting to arbitrage.

GPU Hardware Requirements for Self-Hosting DeepSeek R1

Self-hosting DeepSeek R1 begins with a memory problem before it becomes a cost problem. The full model has 671 billion total parameters, of which 37 billion activate per token thanks to its Mixture-of-Experts architecture ^[1], but inference still requires the entire parameter set resident in accelerator memory because any token can route to any expert. DeepSeek trained the model natively in FP8 (8-bit floating point) precision, so on GPUs with hardware FP8 support, memory usage approximates the raw parameter count: roughly 700GB for 671 billion parameters ^[2]. On GPUs that lack FP8 tensor cores, such as the widely deployed NVIDIA A100, the model must be converted to BF16 (16-bit brain floating point), roughly doubling memory needs to approximately 1.4TB ^[30].

That memory footprint dictates concrete GPU counts. NVIDIA demonstrates the full 671B R1 model on a single server with 8x H200 GPUs (141GB each). An H20 has 96GB of memory, so it is not interchangeable with H200 in that configuration; its required card count and usable context capacity depend on the serving stack and KV-cache allocation ( NVIDIA NIM ( NVIDIA GPU support table. Independent community estimates converge on similar figures: one GPU-requirements guide puts the full model's VRAM need at approximately 1,543GB and recommends 16x A100 80GB GPUs ^[31], while another places it at ~1,342GB with the same 16x A100 recommendation (Source: dev.to). Enterprises standardized on Huawei's Ascend accelerators instead of NVIDIA hardware face a comparable calculation: DeepSeek's full model needs just 2 Atlas 800I A2 servers (8x64GB each) under W8A8 quantization, or 4 such servers for unquantized BF16 operation ^[32], an option DeepSeek and Huawei have jointly documented ^[33].

Rental market data corroborates this hardware picture from the demand side. Vast.ai's live marketplace, which aggregates GPU capacity across more than 40 data centers ^[34], lists NVIDIA H100 SXM units at a median price of $1.92 per hour ^[35], while A100 SXM4 units, the workhorse for BF16-only inference of the full R1 model, list at a median of $0.77 per hour ^[36]. CoreWeave's dedicated A100 80GB instances price similarly, at $2.21 per hour for either PCIe or NVLINK-connected cards ^[37], underscoring that even the cheapest viable full-model configuration, 16 A100 GPUs, carries an hourly hardware bill well into double digits before any inference software or engineering overhead is added.

Table 2 below consolidates verified GPU rental pricing against the vendor-recommended GPU counts for running the full 671B parameter model, translating the hardware requirements above into concrete hourly costs.

As Table 2 shows, the theoretical minimum-hardware entry point for self-hosting the full model starts near $2.89 per GPU hour on commodity H100 clusters, but scales past $4 per GPU hour once enterprise-grade managed platforms or newer accelerators like H200 and B200 are involved. Multiplying these per-GPU rates by the 8 to 16 card counts vendor guidance requires is what produces the tens-of-thousands-of-dollars-per-month figures discussed elsewhere in this report, and it is why the SemiAnalysis-benchmarked cost-per-token figures cited throughout treat GPU generation as the single biggest lever an operator controls.

Quantization meaningfully changes this math. One hardware guide finds that reducing the DeepSeek-R1-Distill-Qwen-32B checkpoint to a full-precision deployment still needs roughly 82GB of VRAM, achievable on a multi-GPU consumer setup such as four NVIDIA RTX 4090 cards rather than a single data-center accelerator ^[44], while reducing the full 671B model itself to 4-bit precision cuts VRAM needs to roughly 436GB, bringing the requirement down to 6x A100 80GB GPUs rather than sixteen ^[45], though at a documented quality cost that most production teams accept only reluctantly. For teams unwilling to run the full 671B model at all, DeepSeek also released six openly licensed distilled models, ranging from 1.5B to 70B parameters, built by fine-tuning existing Qwen2.5 and Llama3 checkpoints on reasoning traces generated by full R1 ^[46], and DeepSeek's own benchmarks show DeepSeek-R1-Distill-Qwen-32B outperforming OpenAI's o1-mini across math, code, and reasoning benchmarks ^[47], a meaningful data point for teams weighing distillation against the full model's hardware burden.

Calculating Self-Hosted Cost per Million Tokens

The central question this report answers, "what does self-hosting cost per million tokens," resolves into a benchmarking problem rather than a simple arithmetic one, because inference cost per token depends heavily on batching and target latency (how many concurrent users a single GPU serves before responses slow down). SemiAnalysis's InferenceX benchmarking platform provides the most direct, independently measured answer available. Interpolated from real benchmark data across three operating points ranging from low to high interactivity per user, NVIDIA H100 delivers DeepSeek R1 inference at $1.365, $4.864, and $15.692 per million tokens as interactivity demands rise, while NVIDIA B200 achieves $0.113, $0.544, and $1.088 per million tokens at the same three points ^[4]. The underlying throughput driving those costs ranges from 266.3 tokens per second per GPU on H100 down to 23.3 tokens per second per GPU at the highest-interactivity setting, versus 4,791.6 down to 497.5 tokens per second per GPU on B200 ^[48]. In practical terms, an operator willing to accept slower per-user response times in exchange for higher batch throughput can push the effective cost per million tokens on H100 down close to API-comparable levels, while an operator demanding instant, low-latency responses for every concurrent user pays roughly 11x more per token on the same hardware.

That benchmarked cost per token has to be paired with the hourly price of the GPUs themselves. Verified on-demand hourly rental rates as of July 2026 span from RunPod's H100 PCIe at $2.89 per hour ^[5] and H100 SXM at $2.99 per hour ^[49], through Lambda's single H100 SXM at $3.99 per hour ^[50], to CoreWeave's H100 PCIe at $4.25 per hour ^[51] and its 8-GPU HGX H100 node at $4.76 per GPU per hour ^[6]. At the high end, AWS's on-demand p5.48xlarge, an 8x H100 instance, starts at $55.04 per hour, or roughly $6.88 per GPU per hour (Source: instances.vantage.sh), with one-year reserved pricing dropping to $23.777 per hour for the full instance (Source: instances.vantage.sh). For the newer H200, RunPod prices on-demand access at $4.39 per hour ^[39], while Microsoft's Azure AI Foundry Managed Compute tier lists H100 access at a flat $8 per compute hour for dedicated, fully managed GPU infrastructure ^[52].

Multiplying those two variables out produces the real answer to "how much does it cost to run DeepSeek R1." A minimally viable 16x H100 cluster at CoreWeave's HGX rate of $4.76 per GPU per hour costs approximately $76.16 per hour, or roughly $54,835 per month run continuously (24 hours a day, 30 days), before accounting for the fact that idle capacity between requests is still billed. Against that fixed cost, the SemiAnalysis-benchmarked $1.365 to $15.692 per million tokens on H100 only becomes cheaper than buying tokens from a third-party host, such as DeepInfra which is confirmed the most affordable tracked provider at $0.56 per million tokens ^[53], once utilization is high and sustained enough to amortize that fixed hourly cost across a very large token volume. For comparison, DeepSeek's newer, non-reasoning V4 Pro model can be purchased through Together AI at $1.74 per million input tokens and $0.20 per million cached input tokens, with output at $3.48 per million tokens ^[26], a useful anchor for gauging how much of R1's self-hosting cost premium is attributable to the reasoning architecture specifically versus general model-serving overhead. This is precisely the dynamic that led one AWS-based case study, detailed later in this report, to conclude that self-hosting is not economical below roughly 100 concurrent internal users ^[54].

Comparative Context and Market Positioning

Placed against the broader large language model (LLM) market, DeepSeek R1's cost structure, whether accessed via API or self-hosted, sits at the aggressive end of the pricing spectrum. It is worth remembering that R1 itself was built by applying reinforcement learning on top of the DeepSeek-V3 base checkpoint ^[55], so any self-hosting cost calculation for R1 inherits the same 671 billion parameter, 37 billion activated MoE footprint as V3 itself ^[1]. OpenAI's current flagship reasoning-capable model prices at $5.00 per million input tokens and $30.00 per million output tokens, with cached input at $0.50 ^[56], while its legacy o1 model, R1's direct 2025-era competitor, remains listed at $15.00 input and $60.00 output per million tokens ^{[17] [18]}. Even DeepSeek's own successor models undercut that historical o1 pricing substantially: current-generation deepseek-v4-flash costs $0.14 input (cache miss) and $0.28 output per million tokens ^{[21] [22]}.

Table 1 below summarizes verified per-million-token pricing across the major hosted channels for DeepSeek R1, alongside comparable closed-model reference points, all captured as of July 2026.

Table 1 separates two different measures: published API input/output rates and workload-specific self-hosting TCO. The SemiAnalysis figures cannot establish a direct API-price comparison because they are owning-hyperscaler TCO normalized by output tokens under specified benchmark settings, rather than retail input/output token prices. A self-hosting decision should therefore compare a deployment's measured utilization, latency target, idle capacity, and operating costs with the buyer's actual API token mix and service requirements.

Data Analysis and Evidence

Quantifying DeepSeek's own economics helps calibrate expectations for what self-hosters are attempting to replicate. DeepSeek's technical report for the V3 base model, on which R1 was subsequently built through reinforcement learning, states that pre-training required 2.664 million H800 GPU hours, context extension 119,000 GPU hours, and post-training 5,000 GPU hours, for a total of 2.788 million GPU hours ^[59]. Assuming a rental price of $2 per H800 GPU hour, the paper states total training costs came to only $5.576 million ^[60], a figure that generated significant industry debate. SemiAnalysis's own analysis cautions that this number reflects only the final training run's compute cost and excludes research, ablation experiments, and prior infrastructure spend, estimating DeepSeek's actual total server capital expenditure at approximately $1.6 billion, with a further $944 million in associated operating costs ^[61]. The same analysis estimates DeepSeek and its parent hedge fund, High-Flyer, have access to roughly 10,000 H800 GPUs and about 10,000 H100 GPUs ^[62], a compute base that dwarfs what any individual self-hosting team would deploy.

A key architectural reason DeepSeek can offer such low inference pricing is Multi-head Latent Attention (MLA), an innovation SemiAnalysis credits with reducing the amount of key-value (KV) cache memory required per query by approximately 93.3% versus standard attention mechanisms ^[63]. Because KV cache size directly determines how many concurrent requests a fixed pool of GPU memory can serve, this reduction is a major driver of DeepSeek's favorable cost-per-token economics relative to attention-heavy architectures, and it is a factor any self-hoster inherits automatically simply by running the same architecture, regardless of which hardware vendor supplies the GPUs. The cost gap between DeepSeek's reasoning and non-reasoning model lines is itself informative for self-hosting decisions: Azure's own catalog prices the non-reasoning DeepSeek V3 Global at $1.14 per million input tokens and $4.56 per million output tokens ^[64], meaningfully below R1's $1.35 and $5.40 on the same platform, and the newest DeepSeek-V4 Flash Global at just $0.19 input and $0.51 output per million tokens ^[65], a gap attributable almost entirely to the additional inference-time compute R1 spends generating reasoning tokens before its final answer.

Independent throughput benchmarking illustrates how quickly the frontier moves. In March 2025, inference provider Avian.io announced achieving 303 tokens per second running DeepSeek R1 on NVIDIA's then-new Blackwell B200 architecture in collaboration with NVIDIA, describing it as "world leading inference performance" for the model ^[66]. Provider-level benchmarking from Artificial Analysis shows current-generation output speeds for the R1 0528 checkpoint varying from 164.9 tokens per second at Google Vertex, the fastest tracked provider, down to 31.6 tokens per second at DeepInfra, a 5.2x spread attributable to differing hardware allocation and batching strategy rather than any change in the model itself ^[67]. This spread matters directly for cost-per-token math, because a provider serving more tokens per second per GPU can spread the same fixed hourly hardware cost across a larger token volume, lowering the effective price it can profitably charge, exactly the lever self-hosters must also pull to make their own infrastructure investment pay off.

Case Studies and Real-World Examples

LiftOff LLC: Self-Hosting on AWS as a ChatGPT Plus Alternative

LiftOff LLC, a startup, conducted a documented evaluation of self-hosting DeepSeek R1 distilled models (1.5B, 7B, 8B, and 16B parameters) on AWS EC2 GPU instances using Docker, Ollama, and OpenWebUI, explicitly testing the approach as a potential replacement for paid AI coding assistants ^[68]. The team found a single g5g.2xlarge instance running continuously cost approximately $414 per month, versus $20 per user per month for ChatGPT Plus ^[11]. Beyond the direct hardware bill, the team identified significant hidden costs, including setup time, DevOps overhead, and the engineering effort required for optimization and troubleshooting, that widened the economic gap further ^[69]. Their conclusion was direct: self-hosting only becomes economically sensible at much larger scale, or where privacy, customization, or regulatory requirements independently justify the added complexity ^[70].

Perplexity AI: Sovereign Hosting for Data-Residency Reasons

When search engine Perplexity AI integrated DeepSeek R1 into its product in January 2025, it did not simply call DeepSeek's own API. Perplexity announced that R1 access through its platform is "hosted exclusively in US & EU data centers, your data never leaves Western servers," explicitly to isolate user queries from the Chinese vendor's infrastructure ^[71]. This is a case of self-hosting driven not primarily by per-token cost arbitrage but by data-sovereignty requirements, illustrating that the "self-hosting cost per million tokens" question is frequently inseparable from a parallel compliance question: the open MIT license is what made this sovereign re-hosting legally straightforward in the first place.

Italy's Garante and the Regulatory Case for Self-Hosting

On January 30, 2025, Italy's data protection authority, the Garante, ordered DeepSeek to block its consumer chatbot application in the country after the company failed to adequately address the regulator's questions about personal data handling, including whether user data was stored in China ^[72]. Regulators in Ireland and France opened parallel inquiries around the same period ^[73]. For European enterprises, this episode may make a deployment that keeps processing within a chosen region or infrastructure boundary worth evaluating. That choice can reduce reliance on DeepSeek's hosted service and may help address data-residency objectives, but it does not by itself establish GDPR compliance. Controllers remain responsible for the processing, including an appropriate legal basis, security measures, processor arrangements, and any applicable international-transfer analysis; organizations should obtain jurisdiction- and deployment-specific privacy and legal review.

Microsoft Azure AI Foundry: Enterprise Managed Self-Hosting

Rather than leaving enterprises to build their own GPU clusters from scratch, Microsoft added DeepSeek R1 to its Azure AI Foundry model catalog, describing it as joining "a diverse portfolio of over 1,800 models" available for enterprise deployment ^[74]. Azure's Managed Compute tier lets customers run R1 on dedicated A100, H100, H200, or MI300 GPU infrastructure without directly managing the underlying hardware, billed at $4 per compute hour for A100 80G and $8 per compute hour for H100, scaling automatically with traffic ^{[75] [52]}. Enterprises requiring guaranteed capacity rather than pure pay-as-you-go billing can instead reserve Provisioned Throughput Units (PTUs), with DeepSeek R1 Global requiring a minimum of 100 PTUs priced at $1 per PTU-hour ^[76], a third pricing model that sits between fully self-managed infrastructure and pure metered API consumption: the enterprise pays a premium over raw GPU rental for managed provisioning, patching, and scaling, but retains more control over data flow and model version than it would through the pay-as-you-go tier alone.

A Community-Scale Self-Host Attempt (Hypothetical Example)

Consider a hypothetical mid-sized software company evaluating whether to self-host DeepSeek R1 for roughly 50 internal engineers with moderate, overlapping usage, a scenario closely mirroring a real discussion thread in the r/selfhosted community where a poster asked exactly this question with a $10,000 budget ^[77]. Community responses converged on the view that reasonable quality at that scale requires either the full model, quantized to roughly IQ4_XS precision across 16 consumer GPUs such as RTX 3090s or 4090s, at an estimated $4,000 in non-GPU server costs alone before purchasing the GPUs themselves ^[78], or a smaller distilled 70B checkpoint requiring at least 40GB of VRAM, achievable on two to three consumer-grade GPUs ^[79]. Another commenter in the same thread was blunter, replying simply that self-hosting at that scale was "probably not worth it" given the slow performance quantized full-size deployments deliver ^[80]. This scenario illustrates the practical middle ground many organizations actually occupy: too small to justify a data-center-grade H100 cluster, but large enough that consumer GPU workarounds introduce real reliability and quality trade-offs.

Implications and Future Directions

The trajectory of DeepSeek's own product roadmap suggests the self-hosting calculus will keep shifting under practitioners' feet. The imminent July 24, 2026 retirement of the deepseek-reasoner API alias in favor of deepseek-v4-flash ^[9] is itself evidence that vendors treat hosted model names as disposable, while the underlying open-weight checkpoints, protected by the MIT license, persist independently of any single company's roadmap decisions ^[81]. Organizations with compliance or reproducibility requirements around a specific model version, rather than "whatever DeepSeek's API currently serves," have a structural reason to prefer self-hosting regardless of near-term cost, because it is the only way to guarantee model behavior does not silently change underneath them.

Hardware economics are also moving quickly in self-hosters' favor. The SemiAnalysis benchmarking data shows NVIDIA's B200 delivering roughly 12x lower cost per million tokens than H100 at equivalent interactivity settings ^[12], an advantage rooted in native FP8 tensor-core support that older architectures like A100 simply lack ^[82]. NVIDIA's own H200 specification sheet confirms nearly double the memory capacity of H100 (141GB versus 80GB) at meaningfully higher bandwidth (4.8 terabytes per second) ^[38], directly reducing the GPU count needed for the full 671B model. As newer accelerator generations reach cloud rental markets at competitive hourly rates, the utilization threshold at which self-hosting beats API pricing should continue to fall, though it will likely never reach zero given that idle GPU-hours remain a fixed cost that API consumption avoids entirely.

Regulatory pressure represents a second, independent force reshaping this decision. Following Italy's block and parallel inquiries from Ireland and France ^[73], a growing number of European and regulated-industry organizations appear willing to accept a self-hosting cost premium specifically to avoid any data transit through DeepSeek's own infrastructure, a pattern already visible in Perplexity's sovereign-hosting approach ^[83]. For such organizations, the relevant comparison is not self-hosting versus DeepSeek's own API at all, but self-hosting versus a compliant third-party rehoster such as Azure, meaning the effective "cost of self-hosting" should be benchmarked against Azure's $1.35 to $5.40 per million token managed pricing ^[27] rather than DeepSeek's own historical rates.

Frequently Asked Questions (FAQs)

What is DeepSeek R1's API pricing per million tokens? At launch, DeepSeek priced R1 access at $0.55 per million input tokens on a cache miss, $0.14 per million input tokens on a cache hit, and $2.19 per million output tokens ^{[7] [8]}. That specific deepseek-reasoner alias is scheduled for deprecation on July 24, 2026, after which it will route to deepseek-v4-flash pricing instead ^[9].

What GPU hardware does self-hosting DeepSeek R1 require? NVIDIA demonstrates the full 671B R1 model on a server with 8x H200 GPUs (141GB each). H20 is a separate 96GB product, not a 141GB equivalent, so its deployment must be sized for the specific precision, context length, and KV-cache requirement rather than assumed to match H200 ( NVIDIA NIM ( NVIDIA GPU support table. Smaller distilled models, from 1.5B to 70B parameters, can run on single consumer or professional GPUs instead ^[46].

What is a typical cost per million tokens for a self-hosted LLM (large language model) generally? For DeepSeek R1 specifically, benchmarked self-hosted costs on H100 range from $1.365 to $15.692 per million tokens depending on batching and latency targets, versus $0.113 to $1.088 on the newer B200 accelerator ^[4].

Is there a reliable self-hosted LLM cost calculator? No single authoritative calculator exists; the underlying variables (GPU hourly rate, batching efficiency, and target latency) vary too much by deployment to reduce to a single number. Aggregators such as OpenRouter report weighted average prices that shift over time as providers adjust capacity ^[84], underscoring why a static calculator cannot substitute for benchmarking a specific workload against the ranges this report documents.

How does DeepSeek R1 compare to GPT-4 on cost? DeepSeek R1's launch API pricing of $0.55 input and $2.19 output per million tokens ^[7] undercut OpenAI's contemporaneous reasoning model o1, officially priced at $15.00 input and $60.00 output ^[17], by well over an order of magnitude, and continues to undercut OpenAI's current flagship pricing of $5.00 input and $30.00 output ^[56].

Is DeepSeek R1 genuinely open source, and can it be used commercially? Yes. Both the model weights and code repository are released under the MIT License, which explicitly permits commercial use, modification, and distillation into other models ^[14]. Note that the smaller distilled variants inherit separate licenses (Apache 2.0 for the Qwen-based distills, Meta's Llama license for the Llama-based distills) from their respective base models ^[85].

Does self-hosting make sense for a small team? Documented evidence suggests no, below a certain scale. LiftOff LLC's case study found self-hosting distilled R1 models cost roughly 20x more per user per month than ChatGPT Plus at under-100-user scale, once instance costs alone were compared ^[11], a conclusion echoed by community discussion threads weighing similar trade-offs at a comparable scale ^[80].

Conclusion

Self-hosting DeepSeek R1 can be justified by sustained utilization or specific compliance and reproducibility requirements, but it is not automatically cheaper than buying API tokens. An 8- to 16-GPU full-model deployment can create tens of thousands of dollars in monthly fixed hardware cost regardless of usage. InferenceX's owning-hyperscaler TCO benchmark ranges from $0.113 to $15.692 per million tokens for its selected B200 and H100 operating points; it is not an input- or output-token price, nor a retail-rental quote. Using RunPod Pods rates of $5.89 per B200 GPU-hour and $2.89 per H100 PCIe GPU-hour, the rental-only calculation is GPU hourly rate × 1,000,000 ÷ (throughput in tokens/s/GPU × 3,600). At the cited B200 throughput endpoints of 4,791.6 and 497.5 tokens/s/GPU, that yields $0.34 and $3.29 per million tokens; at the cited H100 endpoints of 266.3 and 23.3 tokens/s/GPU, it yields $3.01 and $34.45, respectively. These estimates exclude idle capacity and operating overhead ( RunPod Pods pricing ( InferenceX benchmark. API options avoid those fixed infrastructure costs but must be compared using the buyer's actual input/output mix, traffic pattern, and service-level requirements ( InferenceX benchmark ( RunPod pricing.

The decision therefore comes down to three factors this report has documented directly: sustained utilization, data-residency or reproducibility requirements, and organizational scale. Self-hosting can provide greater control over where a deployment processes data and over the model version in use, but it is not automatically required for compliance and does not itself establish compliance. Organizations handling personal data should evaluate their specific processing, security, processor-contract, and transfer obligations with appropriate privacy and legal review. DeepSeek deprecated the deepseek-reasoner alias on July 24, 2026, while mapping it to deepseek-v4-flash thinking mode for compatibility; it remains accessible but no longer identifies the original R1 behavior ( DeepSeek API documentation. Teams that require the original model's exact behavior should preserve and run the released weights where appropriate. For most teams, the practical next step is to start with a hosted API, benchmark actual token volume and latency needs, and invest in dedicated GPU infrastructure only when measured utilization supports it.