How a $26 keyboard chip became a million-dollar dorm-room business

4 min read 1 source clear_take
├── "Niche hardware for existing enthusiast communities is a viable solo path to $1M"
│  ├── Nick Winans (nick.winans.io) → read

Winans argues that you don't need to invent demand or build a platform to clear seven figures — you need to identify a constraint in a community that already has purchasing intent and remove it. His nice!nano didn't disrupt an industry; it served a few hundred thousand mechanical keyboard enthusiasts who were already buying split keyboard PCBs and wanted wireless.

│  └── @mattrighetti (Hacker News, 263 pts) → view

By submitting and amplifying this retrospective to HN's front page (263 points), the submitter signals that the dorm-room-to-$1M-via-niche-hardware narrative resonates as a credible, repeatable template for developers rather than a one-off fluke.

├── "Pin-compatible drop-in replacements beat ground-up redesigns"
│  └── Nick Winans (nick.winans.io) → read

Winans's core technical decision was to preserve the exact Pro Micro pinout and physical dimensions while swapping in the nRF52840. This let every existing Corne, Lily58, Kyria, and Sofle PCB 'upgrade' to wireless by socketing in a new daughterboard — no PCB redesign, no community fragmentation, instant compatibility with the entire installed base.

├── "Democratized contract manufacturing is the structural enabler"
│  └── top10.dev Editorial (top10.dev) → read below

The editorial argues the real story is structural: JLCPCB/PCBWay assembly at small SMD volumes, combined with open-source firmware ecosystems like ZMK targeting the nRF52 family, have collapsed the barrier to shipping niche hardware. Any developer can now do what Winans did because the supply chain and software stack are commodity inputs.

└── "Complementary open-source software is what unlocks new hardware"
  └── Nick Winans (nick.winans.io) → read

Winans credits ZMK Firmware — the Zephyr-based wireless keyboard firmware explicitly targeting nRF52 — as the software story the legacy Pro Micro fundamentally couldn't match. The hardware alone wouldn't have sold; it needed a parallel open-source firmware project to give buyers a path from solder to working wireless keyboard.

What happened

Nick Winans, then an undergraduate, designed the nice!nano in his dorm room: a small nRF52840-based controller board that ships at around $26-30 and slots directly into the Pro Micro footprint used by virtually every DIY split mechanical keyboard on the market. In his retrospective post, Winans walks through the path from a single-PCB experiment to a product that has, by his own accounting, cleared seven figures in lifetime revenue through nicekeyboards.com.

The technical brief was small but ruthless. The dominant microcontroller in the custom keyboard scene — the ATmega32U4 Pro Micro — is USB-only, ten years old, and lacks the radio you need for a wireless split. Winans's bet: keep the exact pinout and physical dimensions of the Pro Micro, swap the silicon for Nordic's nRF52840 (BLE 5.0, ARM Cortex-M4, plenty of flash), and let the existing universe of split keyboard PCBs — Corne, Lily58, Kyria, Sofle, dozens more — "upgrade" by socketing in a new daughterboard. No PCB redesign required by the buyer.

The product didn't need to invent demand; it needed to remove one constraint from an enthusiast community that already had purchasing intent. Pair that with ZMK Firmware, the open-source, Zephyr-based wireless keyboard firmware that emerged around the same time and explicitly targeted the nRF52 family, and the nice!nano had a software story the legacy Pro Micro fundamentally couldn't match.

Why it matters

The interesting part of this story isn't the revenue number — it's the shape of the opportunity. Winans didn't build a platform, didn't raise capital, didn't disrupt an industry. He built a $30 piece of hardware for a niche of maybe a few hundred thousand people worldwide, and that was enough.

Three structural forces made this possible, and all three are still available to any developer reading this. First, contract manufacturing has been democratized: JLCPCB and PCBWay will assemble a small SMD board in single-digit-unit quantities for under a hundred dollars, and the same pipeline scales to thousands of units without renegotiation. The capital wall that used to gate hardware startups — tooling, MOQs, supplier relationships — has been flattened into a web form.

Second, open firmware is doing the heavy lifting. ZMK is BSD-licensed, community-maintained, and supports the nice!nano as a first-class target. Winans didn't write a driver stack, a HID implementation, a BLE pairing flow, or an OTA updater. He shipped a board, and an entire firmware ecosystem — built by other people for their own reasons — made it useful out of the box. Compare this to the Arduino-era model where the hardware vendor was on the hook for the entire software experience.

Third, the keyboard community markets itself. r/ErgoMechKeyboards, the geekhack forums, the keyeb Discord, the YouTube build-log ecosystem — none of this needed paid acquisition. A new board that solves a known pain point gets reviewed, integrated into build guides, and recommended in five-figure-view videos within weeks of launch. The nice!nano became the default wireless option not because of marketing spend but because nothing else fit the slot.

There's a sharper lesson here than "hardware is back." The winning move was footprint compatibility with an entrenched standard, not feature differentiation. If Winans had designed a better-but-incompatible board, he'd have been asking every PCB designer in the community to redo their layout. Instead, he asked them to do nothing, and let the network effect of an existing footprint do the distribution work for him. This is the hardware equivalent of shipping a drop-in replacement for a popular npm package — you inherit the install base.

What this means for your stack

If you're a developer who has ever flirted with hardware, the nice!nano is a useful proof point against the usual objections. You don't need a fab. You don't need a hardware team. You don't need to raise. You need a niche where (a) an open firmware or driver ecosystem already exists, (b) there's a dominant form factor or interface you can hug, and (c) the community has a forum or subreddit dense enough to provide both feedback and distribution.

For practitioners specifically considering a side project: the analog isn't "build the next Raspberry Pi." It's "find a $20-50 component in an enthusiast workflow that has one obvious limitation — wireless, power, size, sensor accuracy — and ship the version without that limitation, with the same pinout." Look at the 3D printing, retro-computing, amateur radio, e-bike, modular synth, and home automation communities — every one of them has a dominant board with a known constraint and a forum full of people complaining about it.

The budget math is tractable. A prototype run of 5-10 boards from JLCPCB with assembly is typically $80-200. A first production batch of 100 units lands around $1,500-3,000 depending on BOM. If you can sell at $25-30 with a 50% margin, you're break-even on the first batch and self-funded from there. The nice!nano took years to compound to seven figures; the runway to your first thousand dollars is measured in weeks.

Looking ahead

The nice!nano story will get cited as a one-off, but it shouldn't be. Nordic's nRF54 series is shipping, ESP32-C6 just brought Wi-Fi 6 and Thread to a $2 chip, RP2350 added a second core and security features — every one of these is a candidate for a drop-in upgrade board in some community that's still running 2015-era silicon. The opportunity isn't gone; the formula is now visible. Pick the niche, hug the footprint, let open firmware carry the software, and let the community do the marketing. A dorm room is optional.

Hacker News 511 pts 80 comments

I made a million dollar product from my dorm room (2025)

→ read on Hacker News
k_plankenhorn · Hacker News

The part that resonates with me most is the timing and luck acknowledgement. I built a solo Saas product over the past few months using Calude Code as my development partner. Total cost $600. Launching in 3 days. The tools available now means the barrier to building something has basically collapsed

Aurornis · Hacker News

This is a really cool story. If the author is reading: It would be interesting to read about your experiences with marketing and building support for your products. I know you said a lot of it was luck and timing, but it would be helpful to get your thoughts on which moves you made that best took ad

latentframe · Hacker News

What to notice is that this wasn't really a startup idea at first but it was someone noticing that commercial wireless keyboards had solved a problem that the DIY ecosystem had not; a number of successful products seem to be from bringing an existing capability into a community that need it.

Galanwe · Hacker News

I switched to ZMK circa 2024, and never looked back at QMK. I am the proud owner of a Corne wireless from typeractive, and it's such a beautiful product. The nice!nano are also a welcome addition.There is a growing community of enthusiasts starting to sell ZMK powered boards from traditionally

c7b · Hacker News

I admit, I barely understand what the product does, much less how there's 50k people wanting this. This is a component you can use if you're building a DIY keyboard and want to make it wireless? Seems profoundly niche to me. Am I missing something?Anyway, congrats on finding and reaching y

// share this

// get daily digest

Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.