Vast.ai runbook · model rank #9

Stand up Kimi K3
on Vast.ai.

The planning floor exceeds one provider node; choose a cluster-capable provider. Cost-sensitive dedicated containers when you can evaluate marketplace hosts yourself.

Vast.ai setup, in the order that matters

A Docker template attached to a matching GPU marketplace offer. Use the provider console for infrastructure and the pinned runtime block for the model server.

  1. 01

    Do not force this onto one node

    Kimi K3 needs a planning floor of 3072GB. Vast.ai is represented here as an up-to-eight-GPU single-host path.

  2. 02

    Choose a cluster-capable provider

    Use Lambda 1-Click Clusters, SageMaker HyperPod, a multi-node Google/Azure setup, or OCI OKE, then follow the model author's distributed recipe.

  3. 03

    Keep this page for comparison

    The runtime command, storage estimate, model card, and agent prompt remain useful inputs for the alternative deployment.

Runtime seedSGLang · latest
export MODEL_ID="moonshotai/Kimi-K3"
export INITIAL_CONTEXT="32768"
export MIN_TOTAL_VRAM_GB="3072"

# This model exceeds a single 8-GPU node.
# Use the linked official model recipe with the provider's cluster path.
# Keep the initial context conservative until a short smoke test passes.

This is a reproducible starting block. Cluster paths still need the model author's distributed recipe and the provider's orchestration layer.

Smoke testOpenAI-compatible request
curl http://127.0.0.1:8000/v1/chat/completions \
  -H "Content-Type: application/json" \
  -d '{
    "model": "kimi-k3",
    "messages": [{"role": "user", "content": "Reply with: deployment healthy"}],
    "max_tokens": 32
  }'

Run this only after logs show the model loaded. A successful HTTP response is not a latency or quality benchmark.

Quota, license, and storage

  • Confirm At least 3072GB across multiple Vast.ai GPU nodes is actually available in the selected region.
  • Read the Kimi K3 license terms and accept any gated-model conditions.
  • Budget at least 3800GB for weights, cache, and container layers.
  • Keep HF_TOKEN in the provider secret store—not in scripts or templates.

Memory, format, and shutdown

  • Record idle/free VRAM after the model loads and after a representative prompt.
  • Validate the official chat template, reasoning parser, and tool-call parser.
  • Add authentication and TLS in front of port 8000.
  • Verify the provider's stop/delete action actually ends compute billing.

Hand this runbook to Claude Code or Codex

Open a terminal in the repository where you want the deployment files, start claude or codex, then paste this prompt. It asks the agent to verify sources and stop before it creates billable infrastructure.

Deployment prompt
Deploy Kimi K3 (moonshotai/Kimi-K3) on Vast.ai. Use this guide as the starting context: https://www.getflops.ai/models/kimi-k3/vast-ai. Use a planning floor of 16x 192GB GPUs, 3800GB storage, sglang latest, and an initial context limit of 32768 tokens. Open every linked primary source and flag any mismatch instead of guessing. Create a deployment folder containing README.md, .env.example with no secrets, a pinned start script or infrastructure manifest, and smoke-test.sh. Make the endpoint OpenAI-compatible where the runtime supports it. Run local/static validation, estimate the billable resources, and stop before provisioning paid infrastructure until I approve.
Guardrails included No secrets in files · verify primary docs · approval before spend

The two sources to check first

Checked 2026-07-27. This page separates sourced facts from the planning baseline; verify current runtime support and capacity before spending.

Compare Kimi K3 elsewhere