NetworkChuck demonstrates a thin laptop playing a demanding game and running a huge AI model through a nearby WiCi One with an RTX 5090. The intriguing part is not that a 763-billion-parameter checkpoint somehow fits inside 32 GB of GPU memory. It does not. WiCi combines a GPU shared over the local network with an SSD-backed inference engine that moves selected model weights through limited memory. Those are two distinct engineering problems, and they deserve two distinct tests.
WiCi One is a nearby, networked GPU; InferSSD is the open-source engine for running certain large mixture-of-experts models from SSD. The sponsored video shows both working on an early engineering sample. It does not prove that any 32 GB GPU can hold the complete official DeepSeek model in VRAM, that every creative app works transparently, or that the advertised speed is guaranteed in your home.
Watch NetworkChuck's Demonstration
Sponsorship: WiCi sponsored the video and supplied an early engineering unit. NetworkChuck offers a $600-off sponsor link. The link and the demonstration are not an independent hardware endorsement.
Source note, 31 October 2026: The video and supplied transcript establish what NetworkChuck saw and measured. We checked specifications, prices and policies against WiCi's product page; the engine, supported platforms and benchmark method against its public repository; and the official parameter count against DeepSeek's model card. We did not receive a device, rerun a benchmark or audit the wireless protocol.
Two Problems, Two Systems
Problem one is distance. A conventional GPU sits on a fast internal bus. Sending every driver call across Wi-Fi would add a network round trip many times during a single render or inference. WiCi says its driver and protocol reduce those blocking calls through caching, deduplication and pipelining, while keeping the GPU on your local network. The laptop remains the host for the application; the box does the GPU-heavy work. WiCi also offers an SDK and a local, OpenAI-compatible API, which are different integration routes from a virtual GPU driver. These are WiCi's architecture claims, not an independent compatibility test.
Problem two is capacity. Model weights can be far larger than a single GPU's VRAM or a typical computer's RAM. WiCi's InferSSD, built on llama.cpp, stores a supported GGUF on an SSD and streams the mixture-of-experts weights needed as generation proceeds. Active pieces are cached in faster memory. It trades storage capacity for extra data movement and lower speed; an SSD does not literally acquire VRAM's bandwidth. InferSSD is public software and can be tested without buying WiCi One.
How a 763B Model Runs With 32 GB of VRAM
DeepSeek's official model card lists 763B total parameters. The tested community GGUF conversion is not that complete original checkpoint: WiCi's format notes say it is text-only and excludes the vision and multi-token-prediction components. InferSSD's README describes about 470 GiB of first-run model files, stored on disk rather than in VRAM. The 5090 edition has 32 GB of VRAM and a 4 TB NVMe SSD, according to WiCi's specifications.
The helpful mental model is a library: the SSD holds the shelves, RAM and VRAM hold a changing selection of pages, and the mixture-of-experts router determines which parts are needed next. Most of the model is not active for every token, but the full set must remain available on storage because future tokens may choose different experts. In the video, NetworkChuck explains aligned reads, batched requests, caching popular experts and placing work across CPU and GPU. WiCi's architecture document gives the implementation details. This makes the run possible; it does not make the first download, model loading or response time disappear.
What the Speed Numbers Mean
The same model name appears beside several very different numbers. Here is the distinction to keep in mind before treating any one figure as a purchase guarantee.
| Source | Reported result | How to read it |
|---|---|---|
| NetworkChuck's live demo | Around 15 tokens/s briefly, then 3-4 tokens/s on another run; about 8 tokens/s in his verdict. | A sponsored, changing live demonstration on an engineering sample. Prompt, cache state and measurement window are not held constant. |
| InferSSD repository benchmark | 7.270 decode tokens/s on a separate RTX 5090 test system. | A vendor-published 4K-prompt-tier test, measured over output tokens 129-256; excludes model loading and does not use the retail box's listed CPU/SSD configuration. |
| WiCi One product page | 20 tokens/s for DeepSeek V4.1 Flash on the 5090 edition. | A vendor product claim for a production unit over Wi-Fi 7. The page does not publish a fully matched methodology beside the 7.270 tokens/s repository run. |
The numbers are not interchangeable. The repository test used 32 GB system RAM, 32 GB VRAM and a 2 TB PCIe 5 SSD, while WiCi lists a different CPU and 4 TB SSD for the 5090 product. Its published decode rate is a late-output window, not a whole-request average or time to first token. Ask for repeatable tests with your exact model file, prompt length, cold and warm starts, concurrent users and network conditions. A faster benchmark on an optimized production unit is possible; it is not established by the public standalone result alone.
The Game, Creative Apps and Shared GPU
NetworkChuck shows Cyberpunk running on a thin laptop through the WiCi box, and he tours creative workflows including Blender and video work. At 19:41, he switches between chat and image generation: one switch drops from roughly 18 to 8.6 seconds, another from 17 to 4 seconds with WiCi's scheduler. That is a useful illustration of model parking and reuse, not a controlled multi-user throughput benchmark. WiCi says model weights can be shared while each workload keeps its own state; check isolation and capacity under your own simultaneous load.
The Figma and Lovart examples need special care. Both remain cloud applications. For this demo, their AI-generation requests were redirected to a model running locally on WiCi One; that does not make the complete application, its accounts, storage or telemetry local. Likewise, WiCi's wireless link still carries data across your network. A local inference endpoint can improve control of one data path, but privacy depends on every connected app, permission and route.
Try InferSSD Before Buying a Box
WiCi's Apache-2.0 repository currently documents Apple Silicon macOS and Linux with an NVIDIA GPU; Windows is marked in progress. It builds from source and requires platform-specific tools. Its DeepSeek example fetches about 470 GiB, so choose the SSD location before a first run. The official quick start has the current install, model-directory and serving commands. Read the installer and dependencies before executing them, and verify there is enough free storage for the model and working files.
Start by recording a normal task on a model that already fits your machine; then compare quality, time to first token, full-request time, watt-hours and total setup effort with the large GGUF. WiCi's own table shows the large DeepSeek conversion decoding at 2.550 tokens/s on an RTX 5060 Ti test rig. That proves the issue is not a strict yes/no VRAM threshold. The question is whether a large model is useful enough at the resulting speed for your work.
Before You Buy WiCi One
WiCi lists two editions as of 31 October 2026. These are vendor list prices before the advertised $600 discount, shipping and tax, not independently checked checkout totals.
| Edition | Listed hardware and price | Best reason to consider it |
|---|---|---|
| RTX 5060 Ti | 16 GB VRAM, 1 TB SSD; $2,599. | Shared local GPU for smaller models and creative work. Large-model decode may be slow; check your use case. |
| RTX 5090 | 32 GB VRAM, 4 TB SSD; $9,999. | The edition shown in the video, with room for large weight files and heavier work. Compare against a conventional workstation or cloud GPU rental. |
The current shipping policy says orders ship within eight weeks to US addresses only. You can cancel for a full refund before shipping; after shipping, WiCi says change-of-mind sales are final, with a seven-day arrival-defect process and a one-year limited warranty. That matters especially for readers outside the United States. The video shows an early unit, so confirm retail software, supported host OS and apps, router requirements, noise, power draw, sustained performance and concurrent-device behavior before committing.
Finally, “no cloud inference bill” is not “free AI.” Hardware, electricity, cooling, SSD wear and maintenance all count. WiCi itself says the box complements rather than replaces cloud AI. If you only occasionally need a frontier-size model, a metered hosted service may be cheaper and simpler; if several trusted devices need sustained local compute, the economics may change. That is the comparison worth doing.
Resources by Role
| Role | Link | What to check |
|---|---|---|
| Full demonstration | NetworkChuck's WiCi test | Sponsored, early hardware; watch the speed changes, not just the peak. |
| Hardware and protocol | WiCi One · technology | Vendor specifications, supported modes and app compatibility. |
| Open inference engine | wici-ai/inferssd · architecture | Mac/Linux prerequisites, SSD requirement and versioned instructions. |
| Model provenance | Official checkpoint · tested GGUF | Different publishers and formats; the tested conversion is text-only. |
| Evidence and purchase terms | Benchmark method · store policies | Measurement window, distinct rigs, US shipping and returns. |
Video Chapters
The wireless GPU
| Time | Topic |
|---|---|
| 00:00 | An RTX 5090 over Wi-Fi |
| 00:38 | What WiCi One contains and sponsorship |
| 02:15 | Why Wi-Fi looks too slow |
| 04:37 | The WiCi protocol |
| 05:36 | Cloud gaming origins |
The large-model problem
| Time | Topic |
|---|---|
| 06:05 | Two local AI bottlenecks |
| 07:32 | Why huge models do not fit |
| 09:57 | The 750B-parameter math |
| 11:59 | Mixture of experts explained |
| 13:50 | Four storage and caching techniques |
| 15:16 | Live DeepSeek demonstration |
Sharing, price and verdict
| Time | Topic |
|---|---|
| 17:36 | Why GPUs are difficult to share |
| 19:41 | Scheduler switching test |
| 21:06 | Price, shipping and verdict |
| 22:18 | Closing prayer |
Sources and Limits
The video and user-supplied transcript are the source for NetworkChuck's game, creative-app and model-switching demonstrations. The product page and technical overview are WiCi's own descriptions. The InferSSD repository and benchmark methodology establish what its public release and test report actually cover. DeepSeek's checkpoint and the community conversion are separate artifacts. Pricing, availability, performance and compatibility can change. We have not independently reproduced WiCi's results or inspected the retail product.