A while back I was frustrated when wanting to buy a keyboard that there were no triangle-shaped keyboards or circle-shaped keyboards. This lack of peculiar keyboard shapes gave me the idea to make a keyboard that could be reconfigurable into any shape my heart desired. I’m still working on the firmware and making more keys but I wanted to share my progress so far. Heres the source if anyone’s interested in how I made it: https://github.com/notaroomba/keybytes
darksim905 · 2026-10-26 06:37:55 UTC
Just a small suggestion but... maybe re-record your demo without giant floodlights on your desk? :(
stavros · 2026-10-26 08:05:02 UTC
What's wrong with the lights? I like a well-lit video.
luplex · 2026-10-26 09:01:00 UTC
it completely clips when viewing on firefox (I use Zen btw). Like half the pixels are pure white. Looks fine on chromium.
frangonf · 2026-10-26 09:03:32 UTC
Not the case in my Zen (macos) looks fine.
jdiff · 2026-10-26 10:40:15 UTC
Firefox on my machines looks fine.
goodmythical · 2026-10-26 14:44:30 UTC
Looks fine on mine as well.
darksim905 · 2026-10-27 05:22:34 UTC
reading these comments are so interesting to me. I would've thought a video is a video, but I guess maybe there's some codec settings behind the scenes? On Firefox, I get the washout. On Brave/Chrome, it looks normal.
pjc50 · 2026-10-26 10:49:20 UTC
I think that might be a FF problem.
If anything it needs more light to force the camera to turn down the exposure because the LEDs on the keys are bright. Almost all indoor home videos, youtube or zoom, could be improved by more light.
reading these comments are so interesting to me. I would've thought a video is a video, but I guess maybe there's some codec settings behind the scenes? On Firefox, I get the washout. On Brave/Chrome, it looks normal.
sleepybrett · 2026-10-26 09:43:38 UTC
at the cost of what per key? Congrats your removed all the efficiency from the system.
pjc50 · 2026-10-26 09:58:30 UTC
People are willing to spend quite a lot on regular old mechanical keyboards.
But yes, just eyeballing that it's going to be hard to get it below $5/key and probably more like $10 for the first run.
pipe01 · 2026-10-26 11:19:54 UTC
The key's circuit by itself is probably a few tens of cents, I can't imagine the rest of it being that expensive
For reference, my heuristic for circuit price estimation is
- passives and little SMT things are free
- anything electromechanical ~$1: switches, connectors, in this case the pogo pins
- fancy connectors up to $10 (ZIF sockets, RAM sockets, etc)
- normal ICs $1
- BGA or fancier ICs: check digikey or guess $10-$100
- board area is "free" for small boards (up to hand-sized)
podocarp · 2026-10-26 12:46:15 UTC
Is that for a certain order size? Because a lot of the cost can come simply from retooling or swapping components. Like if you have 100 x1 smt components vs 1x 100 smt components it's a huge different if you get what I mean. Also anything through hole I basically just give up getting assembled as a hobbyist.
sleepybrett · 2026-10-26 20:33:43 UTC
you know what a spool of wire, a reel of diodes, a peice of plasticcard and a hobby knife (for a switch plate, assuming you don't have access to a 3d printer or laser cutter), and a rp2040 costs? Because that's all you need (aside switches) to build any size/geometry of keyboard you want.
These per switch pcbs are conceptually cool but just kinda stupid, there are tons of people selling these single switch pcbs without the magnets/pogopins out there.. people try them out and then decide that they are pointless.
wongarsu · 2026-10-26 16:08:43 UTC
Pogo pins are expensive. Somewhere around $0.15-$1 per pin. This design has four pairs of two pins. So just the connectors are over a dollar per key, possibly multiple dollars
pipe01 · 2026-10-26 18:41:27 UTC
That's fair, I didn't take that into account. I wonder if some alternative design that doesn't use them is possible
addaon · 2026-10-27 02:35:10 UTC
Inductive coupling could work for both power and data, but probably not at high enough power levels to have LEDs per key if you want to go through 10+ keys in a row...
sleepybrett · 2026-10-26 18:20:13 UTC
Oh i've spent a lot prototyping keyboards, the pcb quite often one of the cheapest bit (if you even bother with one).
broken-kebab · 2026-10-26 11:14:38 UTC
But looking at demo, I see it can only be rectangular anyway?
digikata · 2026-10-26 11:28:47 UTC
It's a reasonable demo, I could envision variable length wire/flex ribbon spacing segments for different arrangements. Also would be fun for custom buttons for custom panels - big red buttons, buttons w/ guards, etc.
nine_k · 2026-10-26 14:08:56 UTC
It should be relatively easy to add slightly angled connectors. It should be also not hard to make the key PCBs non-square.
jacquesm · 2026-10-26 13:25:29 UTC
How about using a capacitive sheet under the keys, a software x/y map -> keystrokes and a simple passive blob under the keys? That might end up cheaper than this. Nice work though, at least you got the itch scratched :)
NotARoomba · 2026-10-26 15:36:26 UTC
Ohh this does sound like a good idea. w tinker around with it and see but then I would also have to carry around a capacitive sheet thats the size of whatever keyboard I want. Thank you!
schiffern · 2026-10-26 17:08:07 UTC
I know, carry around a keyboard-sized keyboard? How preposterous. :)
Everyone knows keyboards are carried in a hefty sack, like an old baron with their gold coins...
jacquesm · 2026-10-26 17:22:43 UTC
You're welcome, if you make it work let me know please it sounds like a very interesting thing you are doing.
NotARoomba · 2026-10-27 16:05:58 UTC
Of course! I’ll probably make another hacker news post about it lol
conorbergin · 2026-10-26 17:37:51 UTC
Someone sent me a link to your project because I had done something similar earlier this year, I left a github issue with the links, if I had seen this I would’ve commented like a normal person.
My motivations were very similar to yours, I wanted to do some tests with ergonomic keyboards and not have to solder or get custom pcbs made, I opted for small cables between the modules so they could flex, but I had a lot of trouble with the connectors.
NotARoomba · 2026-10-26 22:12:40 UTC
Woahh this seems cool, I did think of using cables but I didn't want to deal with the hassle of them adding space between the keys. Also the cpbergin link in the github issue doesn't work. Also, "I think the concept has legs", what do you mean by this?
conorbergin · 2026-10-27 00:51:58 UTC
Hmm, somethings wrong with my hosting, https://cpbergin.com/dyson2026 should work. It’s just the same video as in the submission.
I mean I think the idea is worth pursuing, this could lead to a useful product. I’d be interested in trying different connection strategies, my cables were way too fiddly and unreliable, and your solution, while very neat, only allows grid layouts. Maybe there’s something else?
sleepybrett · 2026-10-26 20:29:31 UTC
here is the thing though. I can buy a 10$ board like a arduino pro micro or a rpi 2040. Cut out or 3d print a switch plate for whatever switch i want to use and then handwire the matrix, flash qmk/zmk on the board and I have a keyboard for FAR less than 6$ a key. Wiring that matrix is not rocket science, he'll it's barely harder than your typical baking recipie.
trollbridge · 2026-10-26 03:44:15 UTC
I’ve wondered when someone would do this (which gets rid of the annoyances of scanning).
The real breakthrough would be reprogrammable key legends in something like e-ink.
kaipereira · 2026-10-26 03:46:06 UTC
This is awesome!
How does the rigidity of the keyboard hold up with many keys and what's the cost of the materials at higher order quantity?
NotARoomba · 2026-10-26 05:08:56 UTC
Thank you!!
It’s really rigid with 2 keys so far but I have yet to test with longer configurations. At a higher order quantity, each key comes out to be around 6 USD but I’m trying to minimize that as much as possible with future revisons!
fitsumbelay · 2026-10-26 03:56:16 UTC
this is extremely cool. would love to see full board
jasonjmcghee · 2026-10-26 04:01:23 UTC
This is very cool.
It needs spacers / extensions so it can be laid out as desired.
aghuang · 2026-10-26 04:07:57 UTC
Very cool, would really like one
pparanoidd · 2026-10-26 04:24:47 UTC
Now give them all wheels so they can rearrange themselves on my desk
thenthenthen · 2026-10-26 06:58:33 UTC
Was looking in the comments for this^
bitwize · 2026-10-26 08:44:45 UTC
Hook the whole mess into Claude, so that it can punish you for attempting to write the code yourself!
IllIIlIlIlIIIIl · 2026-10-26 04:27:26 UTC
This is a really neat idea for a macro keyboard. If it supported staggered rows and row heights, not to mention structural rigidity it would be good for everyday use too.
NotARoomba · 2026-10-26 05:10:08 UTC
Thank you! I am currently thinking about adding those in the next revision and it would definitely make it more practical.
eviks · 2026-10-26 04:32:17 UTC
Is there a mouse module? Can you connect in a "staggered" manner rather than in a linear grid?
NotARoomba · 2026-10-26 05:11:36 UTC
There isn’t a mouse module yet, but I am going to make more modules that include screens, finger print sensors, and I’ll add in a mouse one too :D. Currently there isn’t support for a staggered manner but I am going to work on it for the next revision.
SV_BubbleTime · 2026-10-26 04:37:02 UTC
I looked over the PCB and schematic and it looks well polished. Not a first draft obviously.
I sort of don’t get the 4x I2C busses. I’m probably missing something obvious but it isn’t immediately apparent how the units all have addressing worked out.
NotARoomba · 2026-10-26 05:26:16 UTC
Thank you!
The 4x I2C busses were mainly there to reduce parasitic capacitance and also allows me to know where each key is physically relative to each other in software. I’m still working on the firmware for it, but currently the plan is for each of the keys to remember its “parent”, the neighbor that is closest to the main board, and forward events repeatedly to the main board.
SV_BubbleTime · 2026-10-26 13:49:11 UTC
So every I2C command is a relay hop? The 10th key in a chain has all the latency of the 9 before it who got the message and relayed it on? Separately what happens when the key is connected on all four of its sides? Does it receive four messages and need to send out four? Or is there some discovery of best path to master? I assume the master polls out “hey have you been pressed” to everyone?
Off the top of my head, I think I would have considered a masterless node system like CAN here, there everyone would just post their press status on change and on cyclic… because if you have to relay I2C messages even at 400kbps, that seems like a latency build up at n keys down the line.
But, I haven’t really thought about it at all. I’ve only used I2C like twice ever!
kvakvs · 2026-10-26 04:56:00 UTC
Sometimes my keyboards get dropped and lose a keycap or two, but never anything serious. If this is dropped on the floor, my trusty keyboard will turn into a bag of puzzle bits, right in the middle of heated gameplay or a meeting...
NotARoomba · 2026-10-26 05:07:40 UTC
The magnets are strong enough that most of it should survive lol. I will be doing drop tests to test that theory out soon
tensegrist · 2026-10-26 08:43:52 UTC
perhaps you could add optional magnetic rails for extra support
or even 3d-printed "grids" of arbitrary shapes, with magnets embedded at the junctions, to interface with the keys' magnets while being separate from them
Woahh this would be cool to tinker around with. I’d also want to take into consideration reducing the ammount of parts you have to assemble for a funcioning keyboard but this definitely would help with the structural support.
Agentlien · 2026-10-26 05:36:28 UTC
I like the idea but I could only find an image of two keys. It would be great to see a demo of a full layout. With only two keys it's a very early POC and hardly a keyboard.
Does communication work well and feel snappy with a full set of keys? How is the structural integrity of a full one? Can it be easily moved around? That type of questions could easily make this unusable at scale.
NotARoomba · 2026-10-26 05:46:05 UTC
I am waiting on some key switches to make more keys (5 in total), but for now I just wanted to show the progress on the mechanical/electrical side. I don’t have enough PCBs for a full set of keys yet, but when the key switches arrive and I assemble the 3 other boards I’ll let you know how it goes :D
Agentlien · 2026-10-26 06:50:37 UTC
Looking forward to seeing it!
What's the production cost of this per key?
NotARoomba · 2026-10-26 15:37:01 UTC
Currently production cost is around 8-10 USD but I’m trying to bring that down!
mentalgear · 2026-10-26 08:18:09 UTC
> Can it be easily moved around?
I would assume you could have a custom support the keys rest on, that itself is split eg in the middle, so you can easily split the whole keyboard and have it stored in a compact way (trading length for depth).
tgv · 2026-10-26 16:09:11 UTC
Normal keyboards have staggered rows. This design doesn't seem to permit that.
My impression was I2C is quite prone to interference too?
NotARoomba · 2026-10-26 16:01:58 UTC
Each key bit-bangs I2C on all four sides which removes this limit so it can technically be infinite!
M95D · 2026-10-26 07:39:36 UTC
Non-viable product. I would NOT buy this.
- How much does it cost? Sell price, not BoM price. I expect something like $10'000 for a full 104-key layout.
- How heavy would it be?
- Can you lift a 104-key layout from the table without it breaking in 2 (or more) pieces? Can you even lift or move a 40% layout with one hand?
- How do you arrange it in a non-ortholinear layout? If you can't, then anyone can just buy an ordinary ortholinear for $100 and switch layouts in software.
- How does the spacebar key look like? Enter key? Shift? I can't type if those big keys aren't big.
- How do you make spaces between key groups?
- There are a lot of pogo pin connections. It's statistically impossible for all of them to work. Is there any redundancy for those connections? Alternate signal paths with automatic rerouting? Any debugging tools/indicators to find where the bad connections are?
- If you have a MCU in every key, and at that price, I would expect them to have a mini-display in the keycap plus lots of other fancy features.
- How about automatic function assignment for each key based on it's location? Can it do that? If not, then any drop on the floor becomes a half-hour puzzle-solving problem.
tourmalinetaco · 2026-10-26 08:04:33 UTC
These are great points, however, who said anything about buying a 100% keyboard in this style, or buying anything at all? I didn’t see a sales page, so it’s likely not intended as an off-the-shelf product.
sleepybrett · 2026-10-26 09:46:49 UTC
sure but even as a diy project it's hilariously stupid.
Jasp3r · 2026-10-26 09:58:48 UTC
What do you mean? He tested the structural rigidity on 2 keys already and it worked fine
pjc50 · 2026-10-26 10:08:03 UTC
DIY is the right place for eccentric projects.
tourmalinetaco · 2026-10-26 19:31:45 UTC
The only hilariously stupid thing is your lack of understanding. Even if this isn’t overly practical, I’m sure they learned a lot that will be applicable to further projects, and the few people this is practical for benefit. OP shared a cool thing they did. You don’t have to like the thing they did. You, however, don’t have a leg to stand on if you cannot articulate constructive criticism and just call it “stupid”.
sleepybrett · 2026-10-26 20:37:54 UTC
I've built a dozen plus keyboards in various configurations. I don't lack understanding, i have better understanding that you do apparently. I can build any keyboard i want with switches, a bag of diodes, a spool of wire and just about any commodity dev board like a rp2040 that qmk/zmk can support, add a 3d printer or a friend with a 3d printer it's a viable keyboard. Hell not even a 3d printer, i've seen guys who've built switch plates and cases with a dremel or basic woodworking tools.
M95D · 2026-10-27 07:40:57 UTC
I'm the one with the criticism. You should argue with me, not those who agree with my criticism.
This project is so bad, anyone with basic physics and electronics understanding can tell it's bad. Unlike @sleepybrett I never even built a keyboard in my life and yet can I still find numerous problems with that keyboard. And I didn't even get to the MCU firmware part. I can only imagine how bad that is.
If this project was done only to learn, then why is it here? People don't usually brag about what they learn. (Look ma! I put 3 lego bricks together.) I mean, it's perfectly OK to build projects to learn, make mistakes and learn from those too - I wish I had time to do that myself - but showing it on HN as if it's some viable product? Don't do that.
Why are you defending it? Just because it looks "cool"?
tourmalinetaco · 2026-10-27 09:23:25 UTC
It’s here because OP wanted to show it (likely because they thought their project was “cool” plus wanted feedback). It was then positively voted on by the community. Like it or not, this website is a community-driven aggregator, not a curated commercial showcase. Over the course of a day I easily ignore 90% of the articles here, and consider most of them some form of “stupid” or “bad”. Unlike real life, ignoring the things you dislike here really lets them go away.
Let me remind you that you literally opened up with various constructive criticisms, providing value to OP and to others reading. That alone made the OP’s post worth it. Nobody made any claims that it was a product btw, you made that assumption yourself. OP could have—and should have—explained what they were aiming for here, but “Show HN” is literally for things people make, just because some people use it as free advertising doesn’t mean hacking away at personal projects is wrong, in fact it’s the opposite.
As for why I’m defending it? Because I want to, it’s that simple. I don’t need a complex explanation to defend it or myself, particularly when I made my thoughts clear earlier. What about you? Why do you feel the need to shield sleepybrett from criticism while he’s posturing over making a simple keyboard? Why do you feel the need to tear this project down over aspects you haven’t even looked at?
ehnto · 2026-10-26 08:14:18 UTC
I think not-a-keyboard is probably the better use case. A modular plug and play, configurable keypad would be pretty useful for sim enthusiasts or various workstation uses. You could solve the "picking up" problem by putting the modules on a baseplate.
sleepybrett · 2026-10-26 09:45:49 UTC
designing a custom pcb for your own 'weird keyboard layout' and getting them manufactured short run would probably be cheaper and work better.
M95D · 2026-10-26 11:59:19 UTC
Not even good for gaming because of the unreliable connections between modules.
Karliss · 2026-10-26 12:03:42 UTC
The MCU in each module is probably one of the cheapest parts in that build $0.2-0.25 a piece. It's the mechanical parts which are expensive. The switches+keycaps which you need anyway depending on how nice you want them to be can cost $0.4-1.5 per key. The most expensive part is probably the pogo pins $0.5/per pair x 8 = $4 and magents.
9dev · 2026-10-26 07:56:28 UTC
I'd suggest also adding blank modules without a switch on them for empty space on the keyboard (for example around arrow keys), that would still provide the interconnect to adjacent keys. Cool project.
NotARoomba · 2026-10-26 15:41:31 UTC
Ohh this would be cool, thank you for the idea!
stavros · 2026-10-26 08:07:05 UTC
This is cool, but wouldn't it cost more than $2k for a 104-key keyboard? I can't imagine these PCBs having a final price of less than $20 each.
NotARoomba · 2026-10-26 15:43:03 UTC
Around 800 currently but I’m trying to bring that cost down.
O_H_E · 2026-10-26 08:14:48 UTC
I'm not sure if I have a use case for this but on the technical aspects this is so cool. Those magnetic snaps made me grin!
vim-guru · 2026-10-26 08:19:06 UTC
I like the idea, but ergonomic keyboards are usually not perfectly columnar.
childintime · 2026-10-26 08:32:44 UTC
Gotcha! Just in time before he scales things up to consider the impact of not having column comms.
mft_ · 2026-10-26 10:43:26 UTC
Very good point. I wonder whether the communication would work with rows of connected keys, only joined to other rows at one end? You could then just create simple connection blocks for different row offsets.
rebooot · 2026-10-26 08:32:13 UTC
good idea!
the other day was doing a roundup on keyboards to see whats new and got a striking realization, how nobody has ever slapped a nvme slot into on the back/core part of the enclosure to use as external drive since lot of us comute everyday with extra peripherals
pjc50 · 2026-10-26 10:07:02 UTC
NVME might not be the right idea as it's on the wrong end of a USB connection, but you could easily put a USB3-C socket in there.
Comments
If anything it needs more light to force the camera to turn down the exposure because the LEDs on the keys are bright. Almost all indoor home videos, youtube or zoom, could be improved by more light.
But yes, just eyeballing that it's going to be hard to get it below $5/key and probably more like $10 for the first run.
For reference, my heuristic for circuit price estimation is
These per switch pcbs are conceptually cool but just kinda stupid, there are tons of people selling these single switch pcbs without the magnets/pogopins out there.. people try them out and then decide that they are pointless.
Everyone knows keyboards are carried in a hefty sack, like an old baron with their gold coins...
https://www.jamesdysonaward.org/en-US/2026/project/input-nod...
My motivations were very similar to yours, I wanted to do some tests with ergonomic keyboards and not have to solder or get custom pcbs made, I opted for small cables between the modules so they could flex, but I had a lot of trouble with the connectors.
I mean I think the idea is worth pursuing, this could lead to a useful product. I’d be interested in trying different connection strategies, my cables were way too fiddly and unreliable, and your solution, while very neat, only allows grid layouts. Maybe there’s something else?
The real breakthrough would be reprogrammable key legends in something like e-ink.
How does the rigidity of the keyboard hold up with many keys and what's the cost of the materials at higher order quantity?
It’s really rigid with 2 keys so far but I have yet to test with longer configurations. At a higher order quantity, each key comes out to be around 6 USD but I’m trying to minimize that as much as possible with future revisons!
It needs spacers / extensions so it can be laid out as desired.
I sort of don’t get the 4x I2C busses. I’m probably missing something obvious but it isn’t immediately apparent how the units all have addressing worked out.
The 4x I2C busses were mainly there to reduce parasitic capacitance and also allows me to know where each key is physically relative to each other in software. I’m still working on the firmware for it, but currently the plan is for each of the keys to remember its “parent”, the neighbor that is closest to the main board, and forward events repeatedly to the main board.
Off the top of my head, I think I would have considered a masterless node system like CAN here, there everyone would just post their press status on change and on cyclic… because if you have to relay I2C messages even at 400kbps, that seems like a latency build up at n keys down the line.
But, I haven’t really thought about it at all. I’ve only used I2C like twice ever!
or even 3d-printed "grids" of arbitrary shapes, with magnets embedded at the junctions, to interface with the keys' magnets while being separate from them
Does communication work well and feel snappy with a full set of keys? How is the structural integrity of a full one? Can it be easily moved around? That type of questions could easily make this unusable at scale.
What's the production cost of this per key?
I would assume you could have a custom support the keys rest on, that itself is split eg in the middle, so you can easily split the whole keyboard and have it stored in a compact way (trading length for depth).
The keys are attached to a board so it can be in any orientation
Maybe using CAN is better.
>https://www.nxp.com/products/LPC11C00
- How much does it cost? Sell price, not BoM price. I expect something like $10'000 for a full 104-key layout.
- How heavy would it be?
- Can you lift a 104-key layout from the table without it breaking in 2 (or more) pieces? Can you even lift or move a 40% layout with one hand?
- How do you arrange it in a non-ortholinear layout? If you can't, then anyone can just buy an ordinary ortholinear for $100 and switch layouts in software.
- How does the spacebar key look like? Enter key? Shift? I can't type if those big keys aren't big.
- How do you make spaces between key groups?
- There are a lot of pogo pin connections. It's statistically impossible for all of them to work. Is there any redundancy for those connections? Alternate signal paths with automatic rerouting? Any debugging tools/indicators to find where the bad connections are?
- If you have a MCU in every key, and at that price, I would expect them to have a mini-display in the keycap plus lots of other fancy features.
- How about automatic function assignment for each key based on it's location? Can it do that? If not, then any drop on the floor becomes a half-hour puzzle-solving problem.
This project is so bad, anyone with basic physics and electronics understanding can tell it's bad. Unlike @sleepybrett I never even built a keyboard in my life and yet can I still find numerous problems with that keyboard. And I didn't even get to the MCU firmware part. I can only imagine how bad that is.
If this project was done only to learn, then why is it here? People don't usually brag about what they learn. (Look ma! I put 3 lego bricks together.) I mean, it's perfectly OK to build projects to learn, make mistakes and learn from those too - I wish I had time to do that myself - but showing it on HN as if it's some viable product? Don't do that.
Why are you defending it? Just because it looks "cool"?
Let me remind you that you literally opened up with various constructive criticisms, providing value to OP and to others reading. That alone made the OP’s post worth it. Nobody made any claims that it was a product btw, you made that assumption yourself. OP could have—and should have—explained what they were aiming for here, but “Show HN” is literally for things people make, just because some people use it as free advertising doesn’t mean hacking away at personal projects is wrong, in fact it’s the opposite.
As for why I’m defending it? Because I want to, it’s that simple. I don’t need a complex explanation to defend it or myself, particularly when I made my thoughts clear earlier. What about you? Why do you feel the need to shield sleepybrett from criticism while he’s posturing over making a simple keyboard? Why do you feel the need to tear this project down over aspects you haven’t even looked at?