For hosted Kimi K3, Kimi Code, Kimi Work, or K3Nova, you do not need a local GPU to use the model. You need a current browser or CLI, stable network, and authorized model access.
For full Kimi K3 self-hosting, treat the project as cluster-scale. The official model data lists 2.8T total parameters, MXFP4 weights, 896 experts, 16 selected experts per token, and a 1M-token context window. A single workstation GPU is not the full-model answer.
AI handoff prompt and permissions
Copy this prompt into Kimi Code, K3Nova, or another AI agent. Keep approval manual for file writes, shell commands, account actions, and secrets.
Copyable AI prompt
Use this to give the agent the task and safety boundary in one message.
You are my AI agent for this task: decide which Kimi K3 use mode I am planning for and produce the hardware, cost, and risk checklist for that mode.
Start by restating the goal and the permissions you need.
Use official docs or the files I provide before making claims.
Give me a direct answer first, then a short table or checklist.
If commands are needed, show exact copyable commands without a shell prompt.
Ask before writing files, running shell commands, deleting or moving data, logging in, spending money, changing account settings, or handling API keys.
Stop and ask me when a step requires secrets, payment, account access, destructive cleanup, or a permission broader than the task.
Recommended AI permissions
Permission
Give AI
Why
Public specs
Allow official model cards, hardware references, and calculator work.
The agent can estimate scale before spending money.
Local system info
Ask before reading local hardware, storage, or process details.
Machine details are private context.
Provisioning
Deny cloud rentals, purchases, DNS, deployment, and paid benchmark runs.
Infrastructure spend needs explicit approval.
Commands
Ask before shell commands, drivers, downloads, or package installs.
Hardware checks can alter the machine.
Hardware checklist by mode
Mode
Local hardware
Main limit
Kimi web, Kimi Code, Kimi Work, or K3Nova
Current device and stable network
Account, quota, endpoint, and request size
Local K3Nova development
Node runtime, browser, and enough RAM for assets
Server config and local port conflicts
One RTX 6000 Ada
48 GB VRAM workstation GPU
Useful for smaller local models, not full Kimi K3
Full self-hosting
Distributed accelerator cluster
Weight memory, context cache, interconnect, and throughput
Evaluation path
Name the mode first
Decide whether you are using hosted Kimi, running the K3Nova web workspace, testing a client against a hosted endpoint, or self-hosting model weights.
Do memory math before shopping
Even low-precision weight estimates land around terabytes before cache, activations, routing overhead, and concurrency.
Check loader support
Do not buy hardware until weights, license, checksums, loader support, and a reproducible serving path are confirmed.
Prototype with the API
Use a hosted endpoint to test quality and prompt shape before committing to hardware.
Limits to keep visible
Hosted use
A normal laptop can use the web product or K3Nova workspace because model inference happens elsewhere.
RTX 6000 Ada
A 48 GB RTX 6000 Ada is a strong workstation card for many local AI tasks, but one card cannot hold the full Kimi K3 weights.
Self-hosting
Plan for multiple accelerators, high-bandwidth interconnect, host RAM, fast storage, cooling, monitoring, and workload-specific evaluation.
FAQ
Do I need a GPU for K3Nova?
No. The web workspace does not load Kimi K3 weights onto your device.
Can an RTX 6000 Ada run full Kimi K3?
Not by itself. Its 48 GB VRAM is far below the full-model weight floor.
What should I test before buying hardware?
Test model quality, prompt length, concurrency, and serving support with a hosted or rented setup first.
K3Nova