
How to run DeepSeek V4 Pro
Bedrock, Vertex AI, or your own GPUs · Checked November 21, 2026
DeepSeek V4 Pro has 1.6T parameters, so it needs about 3,840GB of GPU memory at full precision and about 1,920GB at FP8. A practical starting point is 4-bit quantized on 8x 141GB GPUs.
You have three ways to run it: a managed host that already serves it, your own GPUs in your cloud, or both behind one endpoint. Then you point your agents at it. Here is what each path takes.
DeepSeek V4 Pro hardware requirements
| Precision | Memory needed | Smallest setup that fits |
|---|---|---|
| BF16 (full precision) | ~3,840GB | Multiple 8x H200 nodes (about 4) |
| FP8 | ~1,920GB | Multiple 8x H200 nodes (about 2) |
| 4-bit quantized | ~960GB | 8x 141GB GPUs (one H200 node) |
Our estimates: 1.6T parameters times bytes per parameter, plus 20% for the KV cache and the serving runtime. Using the full 1M-token context needs more. Check the model card for the precision the weights ship in and any recommended settings.
Where to run DeepSeek V4 Pro
01Amazon Bedrock
Not confirmed as of November 21, 2026We could not confirm DeepSeek V4 Pro in the Bedrock model catalog. To keep it in AWS anyway, serve it yourself on GPU instances in your account (EC2 or SageMaker) with the setup below, and check the Bedrock catalog again: new open models are added often.
02Google Cloud Vertex AI
Not confirmed as of November 21, 2026We could not confirm DeepSeek V4 Pro in Vertex AI Model Garden. To keep it in Google Cloud, serve it yourself on GPUs in your project (GKE or Compute Engine) with the setup below.
03Self-host on your own GPUs
vLLM and SGLang support confirmedDownload deepseek-ai/DeepSeek-V4-Pro-0813 from Hugging Face and serve it with an inference server that exposes an OpenAI-compatible endpoint. vLLM and SGLang support it. Start with 4-bit quantized on 8x 141GB GPUs (one H200 node), then load-test with your real prompts before you size for production.
- Keep the endpoint private to your VPC, so prompts and payment data never leave your cloud.
- Read the MIT license, which allows commercial use.
- Run two replicas or keep a hosted model as a fallback, so agents keep working during an upgrade.
Run DeepSeek V4 Pro with Runtime
Serving the model is half the job. The other half is giving agents a safe place to use it. Runtime is the AI agent harness for payment and fintech teams, and it is model-neutral: connect DeepSeek V4 Pro from Bedrock, Vertex AI, or your own endpoint, and your agents use it next to Claude, GPT, or Gemini.
- In your cloud. Runtime runs in your AWS, GCP, or Azure account or fully self-hosted, next to the model.
- Routed by evals. Evals show which steps DeepSeek V4 Pro handles as well as a frontier model, so routine work moves to the cheaper model.
- Fallbacks. If your endpoint is down or slow, agents fall back to another model instead of stopping.
- Guardrails. Agents start read-only, wait for approval before money moves, and every run is recorded.
Harnesses that can drive DeepSeek V4 Pro on Runtime:
Running DeepSeek V4 Pro: FAQ
How much GPU memory does DeepSeek V4 Pro need?
+
About 3840GB at BF16, 1920GB at FP8, and 960GB at 4 bits. These are our estimates: the weights plus 20% headroom. Long contexts need more memory for the KV cache.
What is the cheapest way to self-host DeepSeek V4 Pro?
+
Start with 4-bit quantized on 8x 141GB GPUs (one H200 node). Quantizing further saves memory but can cost accuracy, so test it on your own tasks first.
Is DeepSeek V4 Pro available on Amazon Bedrock?
+
As of November 21, 2026, we could not confirm DeepSeek V4 Pro in the Bedrock model catalog. You can still run it in your AWS account on your own GPU instances (EC2 or SageMaker) with vLLM and SGLang.
Is DeepSeek V4 Pro available on Google Vertex AI?
+
As of November 21, 2026, we could not confirm DeepSeek V4 Pro in Vertex AI Model Garden. You can still run it in your Google Cloud project on your own GPUs (GKE or Compute Engine) with vLLM and SGLang.
Can I use DeepSeek V4 Pro with Runtime?
+
Yes. Runtime is model-neutral. Serve DeepSeek V4 Pro from Bedrock, Vertex AI, or your own endpoint, connect it to Runtime, and agents use it through a harness like Claude Code. Your data stays in your cloud, and evals tell you which steps it can take over from a more expensive model.