

0 / 2 embers
0 / 3000 xp
click for more info
Complete a lesson to start your streak
click for more info
Difficulty: 3
click for more info
Not enough gems
Cost: 6 gems
1: Providers and Models
incomplete
2: Model Costs
incomplete
3: Open-Weight Models
incomplete
4: Self-Hosting Models
incomplete
5: Reasoning Models
incomplete
6: Payment Strategies
incomplete
7: Cost Effectiveness
incomplete
Back
ctrl+,
Next
ctrl+.
This lesson's interactive features are locked, please to keep using them
You don't have to use a provider like OpenCode Console. You can be your own provider by self-hosting an LLM. But running an LLM on your machine is a bit harder than self-hosting most "normal" software. The upside is privacy, control, and no per-token billing. The downside is more setup, weaker models (usually), and hardware constraints.
The biggest practical bottleneck is usually VRAM, your GPU's memory. Model weights have to fit somewhere, and bigger models with large context windows increase memory pressure fast.
You'll hear models described as "X billion parameters." That's a (very) rough indicator of model capacity, but it's not a true quality score. For example, here are two open-weight models:
| Model family | Public parameter info |
|---|---|
| Kimi K2.6 | 1T total / 32B active (source) |
| Qwen3 Coder | 480B total / 35B active (source) |
At 16 bits per parameter, 1 billion total parameters requires about 2 GB of memory... so Kimi K2.6's 1 trillion parameters would require about 2 TB just to store the weights, before any additional inference overhead.
So you can see why most self-hosters run smaller models, often quantized to use less memory.
Don't treat "VRAM required" as one fixed number. It depends heavily on quantization, context length, batching, and inference engine settings.
In OpenCode, local/self-hosted usage is often done via:
The most practical route is usually a dedicated inference server on your local network, likely on a different machine from your dev box. That machine runs the model and exposes an API endpoint through something like LM Studio. Then you point OpenCode at that endpoint:
{
"$schema": "https://opencode.ai/config.json",
"providers": {
"lmstudio": {
"settings": {
"baseURL": "http://<gpu-host>:1234/v1",
},
},
},
}
Replacing <gpu-host> with your inference server's hostname or IP address.