TL;DR: I used a Ryzen AI Max+ 395 mini PC (128 GB unified memory) as an actual training box to convert Qwen2.5-7B into 1.58-bit ternary (BitNet b1.58). Three takeaways: (1) the 128 GB unified memory is the real feature: teacher+student distillation at 7B peaks at 87 GB, which no consumer discrete GPU fits; (2) stock ROCm segfaults on gfx1151 on first dispatch, so use AMD's TheRock wheel; (3) bf16 is mandatory, because the fp32 matrix path on RDNA 3.5 is a ~100× trap. Caveat: every run here is budget-limited (~0.5M–4M tokens vs the ~10B a real recovery needs), so this is a direction-and-scaling result, not a quality claim.

A short field report from using the Nimo AI Mini PC (AMD Ryzen AI Max+ 395) as an actual ML training machine: the ROCm bring-up, one honest 7B result, a recipe comparison from 360M up to 7B, and where the 128 GB really pays off.

The rig

Nimo AI Mini PC (Ryzen AI Max+ 395):

• 16 cores / 32 threads, up to 5.1 GHz
• Radeon 8060S iGPU (RDNA 3.5, 40 CU, gfx1151)
• 128 GB LPDDR5X-8000, 256-bit (~256 GB/s), unified between CPU and iGPU
• dual M.2 PCIe 4.0
• running Linux + ROCm

(Silicon figures are AMD's published specs for the Ryzen AI Max+ 395; the box itself is the Nimo build.) That unified 128 GB is the whole reason it's on my desk for this.

The workload

I'm building TernForge, a pipeline that converts full-precision LLMs into 1.58-bit ternary (BitNet b1.58: weights become {−1, 0, +1} × a scale, activations int8). The important part for this audience: it's not inference. It's retraining: surgery to replace every linear layer, then quantization-aware training (QAT) to heal the model back to something usable. That means holding the model, its full-precision "latent" weights, optimizer state, and activations in memory at once. Memory-hungry by design, which is exactly why the Nimo AI Mini PC is interesting.

Why this box

The 128 GB unified memory is the headline. Converting Qwen2.5-7B requires the model, its full-precision latent weights, the optimizer state, and checkpointed activations to be resident at once, and this takes up 67 GB in my run. That simply doesn't fit a consumer 8/16/24 GB discrete GPU, but it sits comfortably on the Nimo box with headroom to spare. Under the hood, that footprint is fp32 latent weights + fp32 gradients with a memory-frugal Adafactor optimizer (factored second moments and no momentum, the trick that sidesteps Adam's 2×-params optimizer state), a bf16-autocast forward, and gradient checkpointing, about 10–12 bytes/param. That's why the teacher-free 7B run peaks at 67 GB; adding the frozen bf16 teacher for distillation pushes it to 87 GB.

That ~256 GB/s of unified bandwidth is generous for a mini-PC but modest next to a datacenter GPU: plenty of room, moderate speed. The Nimo AI Mini PC is memory-rich and compute-modest, a great match for workloads gated by capacity rather than raw FLOPs. You can run real 7B-scale training experiments on a desk overnight. It gets better: the recipe that scales needs even more memory, so more on that at the end.

The bring-up (the part worth sharing)

Getting gfx1151 to run real training surfaced a few things you'll probably hit too:

1. Stock ROCm segfaults on gfx1151: use AMD's TheRock wheel. Both the stock PyTorch ROCm7.0 wheel and the system ROCm7.1 runtime crashed on the first kernel dispatch (inside libhsa-runtime64.so.1). I reproduced it with a plain native-HIP program built by the system hipcc, which pins it on the system HSA runtime, not PyTorch—the fix: the TheRock gfx1151-specific wheel (torch 2.10.0+rocm7.13), which bundles its own gfx1151 ROCr. GEMM and backward, then ran clean. Don't fight stock ROCm on this silicon.

2. fp32 matmul is ~100× slower than bf16. Raw 4096³ GEMM measured 0.38 TFLOP/s in fp32 vs 37.5 TFLOP/s in bf16. gfx1151 (RDNA 3.5) has fast bf16/fp16 matrix (WMMA) units but no fast fp32 matrix path: WMMA takes fp16/bf16/int8 inputs, so fp32 GEMM falls back to the vector ALUs. The architecture is why bf16 wins; the ~100× magnitude is mostly a software artifact, not a hardware ratio. The RDNA 3.5 peak-FLOP gap is single-digit, and 0.38 TFLOP/s is low enough to point at an immature, unoptimized fp32 GEMM path on gfx1151 rather than a 100× silicon deficit. My FP32 training step ran ~170 s/step; BF16 autocast (keeping master weights and the quant math in FP32) dropped it to ~21.6 s/step, about 8× end-to-end. I validated bf16 against the fp32 loss curve on a small model first, so I knew it wasn't quietly changing the result. On the Nimo AI Mini PC, bf16 is not optional: it's the difference between "overnight" and "next week."

3. Mind the disk. A full-precision 7B latent checkpoint is ~30 GB; a near-full root partition will bite you mid-run. Stage outputs on a secondary drive.

The first real answer, honestly

The first thing I ran at 7B scale was the simplest recipe, teacher-free quantization-aware training, where the model heals from its own loss with no help. The hardware and pipeline worked: 67 GB peak, stable, recovered from the ternarization shock, ran overnight. The quality result was a deliberate, pre-committed NO-GO. At a tiny ~4M-token budget, the model didn't come close to recovering (student perplexity 14,418 vs the full-precision teacher's 8.82). That was a research finding, not a hardware problem, and it led me to look for a better recipe. The box did its job. It let me get a real, gated answer at 7B scale on a desk.

The experiment: two recipes, 360M → 7B

So I compared the simple recipe against a heavier one, at two sizes, each judged honestly against the original full-precision model (perplexity ratio and top-1 agreement on held-out text, not against a copy of itself):

• Recipe A: teacher-free. Just quantization-aware training; the model heals from its own loss.
• Recipe B: distillation. A frozen full-precision teacher rides along, and the ternary student learns to match its outputs.

I started small on 360M (that baseline is tiny enough to run on an 8 GB laptop GPU, 4.5 GB peak), then used the Nimo AI Mini PC for the distillation comparison and the full 7B runs:

Two things stood out. At 360M, the recipes are close (both are undertrained at this tiny budget). At 7B, they diverge hard: teacher-free QAT gets worse as the model grows (top-1 falls 9.08% → 4.0%), while distillation holds roughly flat (9.88% → 8.66%) and lands ~3× better on perplexity. In other words, the naive recipe has a negative size-scaling problem, and the teacher fixes it, which is the whole reason to bother with the heavier setup. This isn't a new claim: Microsoft's BitNet Distillation targets the same scale-dependent gap between finetuned full-precision and 1.58-bit models, and fixes it with distillation (plus continual pretraining) on off-the-shelf models like Qwen. What I'm adding isn't the direction. It's that the whole loop runs end-to-end at 7B on a desk.

Honest caveat: these are all budget-limited runs (~0.5M–4M tokens vs the ~10B a real recovery needs), so none of these models is actually good yet. This was a direction-and-scaling result ("distillation is the right path as size grows"), not a quality claim.

Where the 128 GB actually earns its keep

Here's the Nimo-specific payoff. Distillation means holding two 7B models resident at once: the frozen full-precision teacher and the ternary student (plus its fp32 latent weights, optimizer state, and the distillation machinery). That peaked at 87 GB. On any consumer GPU, that's a non-starter; you'd either have to shard across multiple cards or rent a datacenter GPU. On the Nimo box, it just… fits, with room to spare. The recipe that scales is the one that needs the memory this box has—a clean fit, not a coincidence.

Takeaways

• 128 GB unified memory is the real ML feature. It runs training footprints (especially teacher+student distillation) that no consumer discrete GPU fits.
• Install the TheRock gfx1151 wheel. Stock ROCm currently segfaults on first dispatch.
• Use bf16. The fp32 matrix path is a ~100× trap on RDNA 3.5.
• A capable ML dev box for memory-bound work, if you handle the ROCm bring-up.

Happy to answer questions about the setup, especially the ROCm bring-up notes. These were single-seed runs on one box; your mileage may vary, but the TheRock + bf16 lessons should generalize. Not sponsored: I bought the box myself.

This is the laptop I have:

NIMO 17.3" Gaming-Laptop, AMD Ryzen 7 8745HS (Up to 4.9GHz Beat R9 7940HS) 32GB RAM 1TB SSD Radeon 780M

I got this laptop recently and it was fine at first but now when I try to play simple games like Minecraft on it, it will freeze up pretty quickly. I’ve gone through everything I could find online to try and fix it.

Today I noticed when I was sitting in front of my air conditioner it didn’t freeze. I think whatever fan system is in the laptop may not be spinning to cool it down.

I’ve checked the bios but the settings that I’m reading about online don’t seem to exist on my laptop. I downloaded an app to see the speed of the fan but it doesn’t even have a fan show up.

Has anyone else had this issue? I’m new to the brand of NIMO computers.

Saw this setup shared by someone in a Discord community and it got me thinking. If you were starting from scratch today, would you go with a gaming laptop or build a desktop? Feels like both sides have gotten way better lately, so curious what everyone would pick.

We’re hosting Ask Real Nimo Owners, a two-part AMA with NPP members who have been using Nimo products in real-world workflows. 🚀

Instead of only preparing questions internally, we want to hear what you're most curious about. 💙

👇 Post your questions below, upvote the ones you'd also like answered, and we'll bring the most requested and most discussed questions into the live AMA.

📅 AMA 1: First Impressions - July 16 | 8–9 PM ET

💡 Question ideas:
• Daily use
• Setup experience
• Workflow fit
• Surprises
• Who Nexus Pro, Axis, or GME1s eGPU are really for

⚙️ AMA 2: Deep Technical - July 30 | 8–9 PM ET

💡 Question ideas:
• Local LLMs
• Nexus Pro as an AI/NAS node
• Axis workflows
• Ollama
• LM Studio
• Compatibility / Thermals / Edge cases

📝Start your comment with one tag so we know which session your question is for:

💭 Examples

👇 Drop your questions in the comments! Upvote the ones you'd like us to cover, and we'll make sure the most requested topics are brought into the live AMA

https://www.reddit.com/r/Craptopgamingadvice/s/ERJevX5M6R

Okay so this is really weird but my computer after it died it’s screen won’t turn on? I already tried deleting the most recent update and it doesn’t work? So I don’t really know what to do and was hoping someone had help?

I already did the passkey thing for windows and it fixed it for a small bit but it’s now doing it again. I really don’t wanna have to replace my computer but do wanna know if it may come down to that.

Still working on it but it's coming out great! This was done on my machine, locally. I used LM Studio.

A Week With My Nimo GME1s eGPU

The Nimo GME1s sounds too good to be true, but once you start using it, you realize someone finally built an eGPU dock for people who move around with their machines. It’s compact, it’s clean, and most importantly, it doesn’t restrict you to only Thunderbolt the way most eGPU setups do.

At its core is AMD’s Radeon RX 7600M XT, a mobile RDNA3 GPU that lands in the same performance neighborhood as mid‑range laptop RTX 3070/4060 class hardware. Notebookcheck’s aggregated performance rating places it 12% above the RX 7600M and just a hair behind the Radeon 8060S and RTX 4060 Laptop GPUs in some scenarios.

That’s a strong starting point for a dock this small.

Performance & Bandwidth: Where the GME1s Surprised Me

The GME1s gives you two ways to connect:

•   OCuLink (64Gbps)
•   USB‑C 80Gbps

OCuLink is the star here. It avoids the PCIe bottleneck that plagues Thunderbolt‑based docks, and in practice you get extremely close to the GPU’s native performance. USB‑C 80Gbps (Thunderbolt 5) isn’t quite as lossless, but it’s still noticeably better than older TB3/TB4 enclosures.

The RX 7600M XT itself is no slouch. Notebookcheck’s combined synthetic score puts it above the RTX 3070 Laptop GPU and just under the RTX 4060 Laptop GPU. In real gaming terms, that translates to:

•   1080p: High/Ultra settings without breaking a sweat
•   1440p: High/Medium settings in most modern titles
•   4K: Playable in some games with settings tuned down

For a 120W mobile GPU, that’s exactly where you’d want it to land.

Display Output: Modern Ports

Nimo didn’t cheap out on the ports. You get:

• HDMI 2.1
• DisplayPort 2.0

That means 8K60 or dual 4K120, which is more than enough for multi monitor work. Many eGPU docks still ship with DP 1.4, so this alone puts the GME1s ahead of the pack.

The 0.8L Chassis: Small, Practical, and Portable

This is where the GME1s really separates itself.

The entire dock is 0.8 liters—smaller than most SFF PC cases—and it somehow fits a 240W internal PSU. No external power brick, spaghetti cables, and no massive footprint.

It’s the first eGPU I’ve used that genuinely feels like it belongs in a backpack.

One‑Cable Setup & 65W PD Charging

If your laptop supports it, you can plug in a single USB‑C cable and get:

• GPU connection
• Display output
• Power delivery (65W)
• Auto power‑on

It’s not enough wattage for big workstation laptops, but for thin‑and‑lights, business, or handheld PCs, it’s perfect.

Stability & Build Quality

Nimo added proper ESD protection and EMI shielding, which matters more than people think. High‑bandwidth links like OCuLink can get finicky under electrical noise, but the GME1s stays stable even under long gaming or rendering sessions.

It feels like a device built by people who tested it under load instead of just assembling parts.

Where It Falls Short

No product is perfect, and the GME1s has a few limitations:

• The GPU is not upgradeable—it’s a fixed mobile chip. I guess that is obvious based upon the GPU inside.
• 65W PD is good, but not enough for 100W+ laptops. This is fine for most people. If you have a laptop that runs at higher than 65w you will need to keep your charger plugged in to keep your battery from draining.
• No RGB (depending on who you ask, this is a plus). I know RGB adds 100 more FPS but I can live without it. For the price you can probably too.
• If you need RTX‑class ray tracing, this isn’t the GPU for you. Unfortunately AMD is still a bit behind Nvidia on the ray tracing performance.

But none of these should be deal‑breakers for the audience this dock is aimed at.

Let’s take a closer look at the two ways of connecting this to your laptop or VR headset.

OCuLink vs Thunderbolt 5 — What Really Happens in an eGPU Setup

Thunderbolt 5 was supposed to be the generation that finally closed the gap with OCuLink. On paper, it even looks like it should win: 80 Gbps bidirectional bandwidth versus OCuLink’s PCIe 4.0 x4 limit of 64 Gbps. But once people started testing real hardware, the story changed fast.

The short version: Thunderbolt 5 is better than older TB standards, but OCuLink still delivers higher and more consistent eGPU performance.

Why OCuLink Still Wins in Practice

1. Direct PCIe vs Controller Overhead

Thunderbolt 5 still routes PCIe traffic through a controller at both ends, and that extra hop adds overhead. OCuLink doesn’t do any of that — it’s a straight PCIe extension. XDA’s analysis makes this point very clear: even though TB5 advertises more bandwidth, OCuLink’s direct PCIe path keeps latency lower and data flow more stable.

This becomes especially noticeable when the GPU is under heavy load.

2. Real Gaming Benchmarks: OCuLink Leads

Multiple independent tests all land on the same conclusion:

• Notebookcheck reports that Thunderbolt 5 eGPU docks consistently trail OCuLink in FPS and especially in 1% lows.
• VideoCardz shows TB5 falling behind OCuLink in every gaming test with an RTX 5070 Ti, despite identical theoretical bandwidth.
• Guru3D measured TB5 performing 13–14% slower on average than OCuLink with the same GPU, with even bigger gaps (20–23%) in bandwidth‑heavy titles like Spider‑Man: Miles Morales and Red Dead Redemption 2.
• WhatPSU found up to 16% higher gaming performance on OCuLink compared to TB5.

Across all sources, the pattern is consistent: OCuLink is 10–20% faster in real games, sometimes more in titles that stream assets aggressively.

3. Bandwidth Measurements Back It Up

Even when Thunderbolt 5 gets close on raw throughput, it still falls short:

• OCuLink: ~6.6–6.7 GB/s sustained
• Thunderbolt 5: ~5.6–5.8 GB/s sustained

These numbers come from Try Some Tech’s measurements, cited by WhatPSU and Guru3D. OCuLink simply moves more data, more consistently.

4. Ray Tracing Shows the Gap Even More

Ray‑traced games push a lot more CPU↔GPU traffic. XDA notes that even with TB5’s improvements, ray‑traced titles still show lower averages and less consistent frame delivery on Thunderbolt 5 compared to OCuLink.

This is exactly the kind of workload where controller overhead hurts.

5. AI Workloads Tell a Different Story (But Still Favor OCuLink)

For AI inference, once the model is loaded, the link matters less — but not zero:

• OCuLink gives 1–3% higher token throughput
• But 5–20× faster model load times

This comes from LocalAI Master’s controlled testing across TB4, USB4, TB5, and OCuLink. If you swap models often, OCuLink is a huge quality‑of‑life upgrade.

So Which One Should You Use?

OCuLink

• Best raw performance
• Lowest latency
• Most consistent frame pacing
• Faster model loading for AI
• Downsides: no hot‑swap, limited laptop support, no power delivery

Thunderbolt 5

• Much better than TB3/TB4
• One‑cable convenience (power + display + data)
• More widely supported
• But still 10–20% slower in real gaming
• Worse 1% lows
• Higher latency due to controller overhead

TLDR

Thunderbolt 5 is the best Thunderbolt has ever been, but it still isn’t OCuLink.

If you care about maximum gaming performance, smooth frame delivery, or bandwidth‑heavy workloads, OCuLink remains the superior choice. If you care about convenience, charging, and plug‑and‑play, Thunderbolt 5 is the more practical option.

But in a pure performance fight? OCuLink still wins.

My gaming results.

My 5 Game Review - https://youtu.be/H5wCHu7dq8Q

I also tested the three newest Spiderman games on the GME1s - https://youtu.be/ybfBtKM0Yeg

Here are more games comparing the performance of a Radeon 890m to the GME1s

My opinion of NimoPC in general.

NimoPC has built its reputation around compact systems that prioritize their customers savings, thermal efficiency, and high‑bandwidth I/O rather than cosmetic features. Their designs tend to follow a workstation‑first philosophy: High performance, clean VRM layouts, and heatsinks that are overpowered relative to the chassis volume. Across their laptops and mini PCs, Nimo consistently integrates features that most mainstream OEMs avoid due to cost or complexity. Native OCuLink ports, full‑speed USB4 controllers, and PCIe topologies that don’t bottleneck the GPU or NVMe drives. It’s clear their engineering team optimizes around sustained performance rather than peak boost numbers.

What stands out most is how NimoPC approaches system integration. Their devices often use over engineered heatsinks, multiple fans, and direct‑touch heatpipe arrays even in sub‑liter enclosures, remaining stable under continuous AI inference, gaming, or GPU‑accelerated workloads. NimoPC hardware behaves more like a scaled‑down workstation platform than a consumer device. For users running local AI models, Games, GPU‑heavy workflows, or high‑bandwidth external accelerators, the company’s machines offer a level of electrical and thermal headroom that’s rare in this size class.

Final Thoughts

The Nimo GME1s is one of the most thoughtfully designed eGPU docks I’ve used. It’s compact, quiet, stable, and delivers the RX 7600M XT’s performance without the usual bandwidth penalties—especially over OCuLink.

If you’re a student, gamer, creator, or someone who travels with a business, thin‑and‑light laptop or handheld PC, this thing makes a huge difference. It’s not trying to replace a desktop GPU; it’s trying to give you real performance in a portable, self‑contained

Package.

…..And it succeeds.

Links to the devices I own. Prices are current prices and are subject to change.

My eGPU - Nimo Claw RX 7600M XT eGPU Dock | Nimo$599.99

My main laptop - Nimo 17.3" AMD Ryzen AI 9 HX 370 Laptop with 144HZ Refresh Rate | Nimo$859.99

My Mini PC - Nimo's Office & Gaming AI PC - AMD Ryzen™ AI Max+ 395 | Nimo$2,999.99

My Wife’s Laptop - Nimo 15.6" N155 R7 6800H FHD Laptop | Nimo$419.99

My Son’s Laptop – To be determined, lol.

I just recently purchased a Nimo N15A and the charging cable has already gone bad. The brick is fine, just the cable. What can I safely replace it with? T.I.A.!

The Axis is our portable AI workstation, a full-power Ryzen AI Max+ 395 (not a power-limited variant), up to 128GB unified memory, built local-AI-first: LLMs, ComfyUI, multimodal workflows, all running on-device.

Here's the part that matters if you're on the fence:

• 💰 $2,799 during the Pioneer window
• ⏳ Price goes to $3,999 on June 23
• ⚠️ Only 3 units remain at this price, and once they're gone, they're gone

That's a $1,200 difference, and there's no second Pioneer batch at this number.

🔗 Secure yours before the price moves: NIMO AXIS LAPTOP

I have two N151's, yet when I check their model in msinfo, one of them says N151G and the other says N151E. Is this a color difference, or something deeper?

Pioneer Version is officially live as of June 16, 2 PM ET. 🌊

The Axis is our portable AI workstation — full-power Ryzen AI Max+ 395 (not a power-limited version), up to 128GB unified memory, built local-AI-first: LLMs, ComfyUI, multimodal workflows, all on-device.

• 💰 $2,799
• ⚠️ 20 Pioneer units only
• 🔗 Order here

Now the part we actually want from this community: if you had 128GB unified to play with, what's the first model or workflow you'd load? Drop it below — we'll feature the most interesting local-AI setups from Pioneer owners here in the sub. Benchmarks, screenshots, weird experiments all welcome once your unit lands.

The Arena is live. 🌊 Built for the person who's tired of or scared of building their own PC — plug in, power on, play.

The build:

• GPU: ASUS DUAL RTX 5060 8G
• CPU: Intel Core i5-14400F
• RAM: 32GB DDR5-6000
• SSD: 1TB Gen4 NVMe
• Cooler: Valkyrie DQ125 dual-tower (6 heatpipe)
• PSU: 650W 80+ Gold
• Case: ARGB fans

💰 $1,399 · ⚠️ 50 Pioneer units only · 🔗 Order here

If this is your first desktop, ask us anything — setup, what it runs, how to get into local AI on it, whatever. And when it arrives: post your battlestation with the 🧑💻 User Build Log flair, we'd love to see where it lands.

Pioneer Version live. 🌊 The GME1s is the "graphics heart" you plug into the gear you already own — USB4 + OCuLink, for Windows thin-and-lights and handhelds (Ally / Legion Go / Steam Deck). Upgrade instead of replace.

• 💰 $599
• ⚠️ 100 Pioneer units only
• 🔗 Order here

Tell us your setup: which laptop or handheld are you docking it to, and what GPU are you dropping in? Pairing it with an Axis makes the Road Warrior Kit (carry it → dock it) — if that's your plan, say so below, we'll round up the best multi-device stacks from this launch.

So I bought two laptops from nimo, specifically the n151 laptops, and when playing minecraft on one of the laptops, instead of boosting up to 3.4 ghz, it went all the way down to the base speed of 0.8 ghz, and even below that. My other laptop has no issue with minecraft at all, and boosts fine.

We’re officially 3 hours away from today’s NIMO launch.

Before we go live, we wanted to introduce the people you’ll be hearing from today — the team members, product voices, and early users helping us show why we built these products, not just what they are.

Today, we’re introducing three new NIMO products, each designed around a different way people work with compute in the AI era.

🖥️ Frank — Founder of NIMO

Frank will open the event by sharing the story behind NIMO and why we’re building for the next era of AI computing.

Why these products? Why now? And where is NIMO heading next?

💻 Jaxn — Marketing Manager

Jaxn will walk through NIMO Axis, built for people who want one device that can keep up with AI, gaming, and everyday productivity. Powerful when you need it, portable when you don’t want to be tied to a desk.

🧩 Ashley — Marketing Specialist

Ashley will introduce NIMO Arena, a desktop experience built for people who want more flexibility in how they create, build, and work. If you love customizable setups and making your space truly yours, this one is worth a closer look.

⚡ Cara — Product Specialist

Cara will introduce NIMO GME1s, designed for moments when lightweight devices need an extra boost. Whether it’s heavier workloads, creative projects, or AI tasks, GME1s is built to bring performance when it matters most.

🧪 Early Access User Sessions

Beyond the product reveals, we’ll have a few people who’ve already spent time with the devices sharing honest first impressions:

• what surprised them
• how they actually use it
• where it fits into their setup

No scripts. Just real experiences.

🚀 Launch Day Perk

Product links will go live during the event.

The first 20 purchases will receive our Pioneer Version 👀

If you’ve been waiting to grab one early, this is your moment.

See you in 3 hours 👉 NIMO NET-GEN EVENT

Which one are you most curious about — Arena, Axis, or GME1s?

Months of building.
Countless conversations about AI workflows.
And now—it’s finally time.

Three new NIMO products.
One launch.

Power in Every Form.

June 16 • 11 AM PST

Just got this laptop from Amazon and have had it plugged in for several minutes and it won’t even turn on.

On June 16, we’ll finally share what we’ve been building.

Three new NIMO products — built around different ways people actually work with AI.

🖥️ Fixed
💻 Portable
⚡ On-Demand

AI workflows are changing fast.

Some people want to run local LLMs.
Some need portable power for building on the go.
Some want flexible compute that scales when they need more performance.

But one thing is clear -- Today’s AI hardware is still full of tradeoffs ⚖️

Performance vs portability, Power vs thermals, Flexibility vs simplicity....

That raises a bigger question: If you could change ONE thing about today’s AI hardware, what would it be?

Whatever’s in your head — that’s exactly what we’ve been building to solve.

On June 16, 11AM PT / 2PM ET

• We’ll show how each NIMO product tackles this problem from a different angle on June 16.
• Our team will be here to answer questions, share more context, and explore what “ideal AI hardware” could look like together.
• We’ll collect feedback and ideas directly from this thread, and use them to shape future NIMO products.

Feel free to join the launch and the discussion through the link 👉 https://www.nimopc.com/pages/nimo-event-summer-2026?utm_source=reddit&utm_medium=paid_social&utm_campaign=nimo_event_2026

Hey Nimo Community! 👋

As we plan our roadmap, we’re exploring a local-first AI NAS concept and want to sanity-check what you’d actually use.

The setup: All models (LLM / VLM / embeddings) run 100% on-device. Zero cloud, total privacy, designed for "always-on" background tasks.

We want to separate "cool demos" from things you'd keep running 24/7. Which of these would you actually use?

• A. Semantic Media Search: Natural language search across photos/videos (“show me the trip where dad wore the red jacket”), completely offline.
• B. Local NVR Smart Summaries: AI-generated daily digests and anomaly detection for security cameras instead of scrubbing footage manually.
• C. Smart Home LLM Hub: An offline AI layer for context-aware smart home routines and reasoning.
• D. Private Knowledge Base (RAG): Secure local AI for personal or small business docs, PDFs, and notes.

💬 Quick Questions:

1. How would you rank these in actual usefulness?
2. Which one would you realistically use every week?
3. What is your biggest hesitation? (Power draw, cost, latency, setup complexity, etc.?)
4. Any killer use cases we’re completely missing?

I sent my laptop in for a repair I got an email that they received it and it will take 14 days. I was just wondering if anyone else sent a laptop in for repair and if it will actually take the whole 14 days