llmrun
apodexQwen3_5ForConditionalGeneration

Apodex 1.0 4B SFT — Hardware Requirements & GPU Compatibility

ChatFunctions

Apodex 1.0 4B SFT is a 4.7B-parameter open language model from apodex. It supports a context window of up to 262,144 tokens. At BF16 it needs about 9.79 GB of VRAM — see which GPUs and Macs can run it below.

4.7B params · dense262K contextApache 2.0231 downloads17 likes
Based on Qwen3.5 4B
S

Runs great on a 24 GB GPU

Runs from12 GB BF16 · 64KBest on24 GB BF16 · ~67 tok/s · 256KMacs from16 GB BF16 · ~14 tok/s

Apache 2.0

Reference GPU · RTX 4090 24 GB

Estimates, ±20% · how we estimate

Run Apodex 1.0 4B SFT

One recommended way. Every other method, OS and quant is in the step-by-step guide.Each way opens a step-by-step guide for your OS and quant.

Recommended

vLLM
one command · needs vLLM installed
$vllm serve apodex/Apodex-1.0-4B-SFT --max-model-len 16384

vLLM repo with its own quantisation

Download: Weights on Hugging Face

install, OS, other quants

Ways to runOther ways

each opens step-by-step

Run in cloud

Runs on RTX 3080 Ti (12 GB) (2 GB headroom) · BF16

Generation speed
~61 tok/s
generation speed
Cost per 1M output tokens
$0.56
per 1M output tokens

How Much VRAM Does Apodex 1.0 4B SFT Need?

Select a quantization level; the listed hardware adheres to it.

QuantizationVRAM+32KOn RTX 4090 (reference)
9.8 GB10.3 GB16-bit · bfloat — Brain floating point 16 — preferred for trainingFits: 256K context · ~67 tok/s
est.calculated, no published file yet

Selected BF16

Brain floating point 16

10.0GBat 16K context

Weights
9.3 GB
KV cache
0.3 GB
Overhead
0.3 GB

Fits RTX 4090 (reference) · 14.0 GB free · ~67 tok/s

≥50 tok/s needs ≥752 GB/s · RTX 5090 ~119, RTX 3090 Ti ~67

Which Hardware Can Run Apodex 1.0 4B SFT?

BF16 · 9.8 GB

Apodex 1.0 4B SFT (BF16) requires 9.8 GB of VRAM to load the model weights. For comfortable inference with headroom for KV cache and system overhead, 13+ GB is recommended. Using the full 262K context window can add up to 5.2 GB, bringing total usage to 15.0 GB. 40 GPUs can run it, including NVIDIA GeForce RTX 5090, NVIDIA GeForce RTX 3090 Ti, NVIDIA GeForce RTX 3080 Ti. 150 devices with unified memory can run Apodex 1.0 4B SFT, including Mac Studio (M3 Ultra, 256GB), Mac Studio (M3 Ultra, 512GB), Mac Mini M2 Pro (16 GB).

By VRAM tier · typical GPUs and Macs at BF16
8 GB · RTX 4060Doesn't fit — smallest quant needs 10 GB8 GB tier →
12 GB · RTX 3060 12GBBF16 · 10 GB · ~24 tok/s · 64K12 GB tier →
16 GB · RTX 5060 Ti 16GBBF16 · 10 GB · ~30 tok/s · 256K16 GB tier →
24 GB · RTX 4090referenceBF16 · 10 GB · ~67 tok/s · 256K24 GB tier →
Mac 32 GB · Mac Mini M4BF16 · 10 GB · ~9 tok/s · 256KMacs →
Mac 64 GB · Mac Studio M4 MaxBF16 · 10 GB · ~39 tok/s · 256KMacs →

Alternatives to Apodex 1.0 4B SFT

Similar models

4
ModelScoreVRAMtok/sWhy it is similar
Qwen3.5 4BAlibaba98.53.4 GB~201same size
Molmo2 4BAllen AI—4.7 GB~193same size
Qwen3 VL 4B InstructAlibaba—4.5 GB~208same size
Qwen3.6 27B MTPLX Optimized SpeedYoussofal—4 GB~185same size

Specifications

Publisher
apodex
Parameters
4.7B
Architecture
Qwen3_5ForConditionalGeneration
Context Length
262,144 tokens
Vocabulary Size
248,320
Release Date
2026-06-07
License
Apache 2.0

Frequently Asked Questions

How much VRAM does Apodex 1.0 4B SFT need?

Apodex 1.0 4B SFT requires 9.8 GB of VRAM at BF16. Full 262K context adds up to 5.2 GB (15.0 GB total).

VRAM = Weights + KV Cache + Overhead

Weights = 4.7B × 16 bits ÷ 8 = 9.3 GB

KV Cache + Overhead ≈ 0.5 GB (at 2K context + ~0.3 GB framework)

Fit ratings and hardware model lists check this model with room for a 16K-token context, which needs a little more memory.

KV Cache + Overhead ≈ 5.7 GB (at full 262K context)

VRAM usage by quantization

9.8 GB
15.0 GB

Learn more about VRAM estimation →

Can I run Apodex 1.0 4B SFT on a Mac?

Yes — Mac Mini M2 Pro (16 GB) and 133 other Macs can run Apodex 1.0 4B SFT. Apple Silicon uses unified memory, so the model shares RAM with the system. At BF16 you need at least 9.8 GB of usable unified memory (RAM minus macOS overhead).

Can I run Apodex 1.0 4B SFT locally?

Yes — Apodex 1.0 4B SFT can run locally on consumer hardware. Popular tools include Ollama, LM Studio, and llama.cpp.

How fast is Apodex 1.0 4B SFT?

At BF16, Apodex 1.0 4B SFT can reach ~490 tok/s on AMD Instinct MI350X. On NVIDIA GeForce RTX 4090: ~67 tok/s. Speed depends mainly on GPU memory bandwidth. Real-world results typically within ±20%.

tok/s = (bandwidth GB/s ÷ model GB) × efficiency

Example: NVIDIA B200 → 8000 ÷ 9.8 × 0.65 = ~531 tok/s

Estimated speed at BF16 (9.8 GB)

~531 tok/s
~67 tok/s
~531 tok/s
~490 tok/s

Real-world results typically within ±20%. Speed depends on batch size, quantization kernel, and software stack.

Learn more about tok/s estimation →

What's the download size of Apodex 1.0 4B SFT?

At BF16, the download is about 9.32 GB.

Which GPUs can run Apodex 1.0 4B SFT?

40 consumer GPUs can run Apodex 1.0 4B SFT at BF16. Top options include AMD Radeon RX 6800, AMD Radeon RX 6800 XT, AMD Radeon RX 6900 XT, AMD Radeon RX 6700 XT. 26 GPUs have plenty of headroom for comfortable inference.

Which devices can run Apodex 1.0 4B SFT?

150 devices with unified memory can run Apodex 1.0 4B SFT at BF16 (9.8 GB), including AMD Ryzen AI 9 HX 370 (Strix Point) Laptop, ASUS Ascent GX10, Beelink GTR9 Pro (Ryzen AI Max+ 395, 128 GB), Framework Desktop (Ryzen AI Max+ 395, 128 GB). Apple Silicon Macs use unified memory shared between CPU and GPU, making them well-suited for local LLM inference.