Built for inference
128 GB of unified memory holds long context and larger models. 32 GB of GDDR6 keeps the hot path on the GPU.
Our open source inference engine is used by engineers at
Local inference hardware
128 GB of unified memory holds long context and larger models. 32 GB of GDDR6 keeps the hot path on the GPU.
Engine, tuned models, and compatible APIs are installed before shipping. Plug in, pair, run.
No mandatory cloud path. Your code, prompts, and model weights stay on hardware you own.
Full specs and information




| Chassis & thermals | |
|---|---|
| Enclosure | Machined aluminium, hand-assembled in-house |
| Dimensions | 340 × 110 × 320 mm (13.4 × 4.3 × 12.6 in) |
| Volume | 11.97 L (approximately 730 in³) |
| Weight | 6 kg (13.2 lb) |
| Cooling | Air-cooled, tuned for low noise under sustained load |
| Connectivity | |
| Ports | 2× USB4, 2× USB-A, HDMI 2.1, 2× DisplayPort 2.1, 5 GbE Ethernet, plus 4 display outputs on the GPU |
| Wireless | Wi-Fi 7 and Bluetooth, built in |
| System | |
| Software | Ubuntu, engine and models pre-installed, OpenAI and Anthropic compatible API |
| Warranty | 1 year, parts and labor, 72-hour burn-in before shipping |
Dense and MoE inference
Dense
One-user DFlash2 long-prompt decode · 61.3 tok/s on R9700
DFlash2 user run · prose 38.0 · count 217.9
Source / One-user DFlash2 run
Point results · prompt lengths differ / tok/s
R9700 uses one user's long-prompt result; public workloads differ / tok/s
MoE
788 tok/s prefill · 86 tok/s decode
R9700 + Strix Halo · measured
Source / Lucebox measurement
Reported 2K point results / tok/s
Published point results / tok/s
Browser-first onboarding
Pair the nearby machine and put it on your network from the actual onboarding page.
Use the actual local dashboard to prepare the model, enable Lucebox Connect once, and open any supported app.
Visit lucebox.com/setup from a nearby laptop or Android device. There is no app or CLI to install.
The real onboarding UI sends Wi-Fi, account, and optional Tailscale settings directly to the box over encrypted Bluetooth.
The real local dashboard checks the machine, installs its qualified model profile, and starts the private API.
Enable the small Lucebox Connect launcher once, then install when needed, configure, and open any supported app from Manage.
Limited production capacity
Time remaining / --d --h --m --s
Tell us what you are building, the workloads involved, how many boxes you need, and your preferred timing.
We schedule a short call to understand the work, confirm technical fit, and discuss delivery needs.
Capacity is limited and demand is high. If we can allocate a unit, we confirm the delivery window and send a secure purchase link after the call.
Open development
What builders said after testing our inference engine.
I like your stuff so far, keep going
this guy just cracked 134 tok/s on qwen 3.5-27b dense and 73 on new qwen 3.6-27b on a single 3090. open source moves at godspeed in 2026.
Interesting run w/ Dflash from the lucebox-hub guys
speculative PREFILL?????
I have tested some LLM server software for home PCs for Linux and Windows. Fastest and best for running home is Linux running 145 t/s, Lucebox. @pupposandro @luceboxai
PFlash just killed the 4-minute blank screen problem. 128K token prefill in 25 seconds, same GPU, same model, no compromises
Consumer-grade GPUs actually have sufficient hardware potential, general-purpose frameworks just waste most of it on overhead. Lucebox releases that potential through hand-written kernels, letting even a 2020 RTX 3090 rival Apple's latest chips on efficiency.
Crazy I was litteraly wondering how can I increase my token speed 10 min ago
Crazy what @pupposandro just dropped on Qwen3.5-27B. 207 tok/s on a single 3090 with Q4_K_M and full DFlash speculative? Chinese labs + ggml hacks are just cooking on consumer hardware right now. This is the kind of local win I like to see.
RTX 3090 ready for a new life! Bringing it to @luceboxai team to make some experiments together
github.com/Luce-Org/lucebox-hub looks promising as a way to run "dense" models (eg. Qwen 27B) more efficiently. It's janky, but on my 5090 laptop it seems to be ~2x more tok/s than llama.cpp
This is very very good work BRAVO. I love it
Nearly 10x faster! After finishing Decoding, it starts cranking through Prefill. The previous DFlash was already stunning enough, and now they've added PFlash. Speculative prefill, up to 10x speedup. Go try it right now.
First time reading about speculative prefill, and it's crazy. 257s down to 24s for a 128K prompt on a single RTX 3090. Great article, definitely go ahead and give this a read.
impressive... so this is what it looks like when you focus on a set ram limit and optimizing for a single model above everything
Speculative decoding on ggml for Qwen3.5-27B Q4_K_M, with the published setup and results.
Speculative prefill cuts a 128K prompt from about 257 seconds to 24.8 seconds on the published CUDA reference run.
Only the experts used by the current tokens stay resident, so larger MoE models fit on smaller GPUs.
Runs 256K context on a 24 GB card while reducing KV VRAM from 4.6 GiB to 72 MiB through bit-exact paging to host memory.
Experiments and benchmarks
About 257 seconds down to 24.8 seconds in the published CUDA reference run, with NIAH retrieval preserved.
Read article →Up to 207 tok/s, 3.43× over autoregressive, with 128K context in the published reference configuration.
Read article →Keep only the experts used by current tokens resident. Self-tuning, one flag, and measured memory use.
Read article →Custom decode and prefill paths measured on the Ryzen AI MAX+ 395 against llama.cpp HIP.
Read article →The first MoE target for PFlash, with measured long-context prefill and decode performance.
Read article →Prebuilt, self-tuning images across supported NVIDIA GPUs and AMD Strix Halo.
Read article →Questions