> I run open-weight models on boxes I own — NVIDIA Spark, ASUS GX10, Grok, local agents — then write what worked. No brochure. Games included.
Local AI leads: open-weight models on hardware I actually own, plus Grok, vibe coding, and the games that come out of that stack. Marketing archives stay in the hubs — they are not the front door.
Open-weight models, local inference stacks, VRAM planning, and homelab setups for running AI on your own hardware.
Open hub From the labSmall browser games shipped from the same stack — including Moon Trail, built with a local agent.
Open hubIn-depth reviews, comparisons, and guides for the latest AI tools reshaping how we work and create.
Open hubSEO strategies, content marketing insights, and growth tactics for the AI-powered marketing landscape.
Open hubBreaking developments in AI, cloud computing, data centers, and the future of technology.
Open hubI unboxed an ASUS Ascent GX10 — NVIDIA DGX Spark in a 150mm cube — and started running local models on 128GB of unified memory. No brochure. First notes from the bench.
Read full articleI told Grok Build to recreate my link-in-bio page from live links. It published wikiwayne.grok.me. Zero monthly fee, full control — this is what 'just build it' looks like in 2026.
I run every X post through Grok's Enhance button before I hit send. It catches omitted words and missed punctuation. Here is why that tiny feature matters more than another chatbot.
Fantastic pricing is credible. Calling Grok 4.6 a solid Sonnet-class model on day one, ahead of Gemini, is not — not without real metrics. How I read launch-day AI posts.
I posted Qwen 3.8 27B three times and meant it. Why a 27B open-weight model still matters on a 128GB Spark-class box, and how I would actually load it.
Local AI, vibe coding, real hardware
Open-weight models on hardware I own. Grok and local agents when they earn it. Skeptical of the brochure.
Read Full BioHardware unboxings, local-model runs, Grok experiments, and the occasional cookie bet.
Follow @wikiwayne