How it started

The story behind HexaNect.

It started because I needed a shoe rack.

01 · The need

It started with a shoe rack.

I was actually trying to avoid another project. Normally, if I need something, I'll just build it. But it was summer, the garage was hot and already full of half-finished projects, and I really didn't need to start another one.

So I bought a shoe rack instead.

It sucked.

Naturally, that somehow turned into a whole new project. I designed a much better one in Fusion 360, but while thinking about actually building it I started playing with another idea: simple straight-cut boards connected with 3D-printed parts.

I liked the look of it, I liked mixing materials and techniques, and I really liked the LEGO-like assembly idea. Print the connectors, make a few simple cuts, then put it together piece by piece. Easy to build, fun to assemble, and accessible without complicated joinery.

Original traditional shoe cabinet designed in Fusion 360
02 · Parametric connectors

From one connector to a system.

The first connector was modeled in Fusion 360. Once it worked, I started experimenting with OpenSCAD because I didn't want to manually model every possible connector one by one.

That is where the parametric side really clicked for me. Change the board thickness, angle, connector length or fit, and the geometry changes with it. Suddenly one connector experiment could become a whole system.

First HexaNect connector modeled in Fusion 360
Early OpenSCAD connector experiments
03 · Structure testing

One hexagon became a lot more.

I kept testing how the cells could connect, how boards could share joints, and how far the same basic rules could go. Pretty quickly it stopped being about one shoe rack and started becoming a modular building system.

Early single-cell structure test in Fusion 360
Large honeycomb structure test in Fusion 360
04 · The interface

The interface changed everything.

I started building a simple visual interface because I wanted an easier way to design the structures without constantly jumping between models, dimensions and connector files.

I thought it would just be a basic helper for my own project. But once I could actually build furniture visually, see the boards, change dimensions and have the system figure out the connectors, it was way better than I expected. That was when it stopped feeling like a one-off experiment and started feeling like a real tool.

Early Honeycomb Builder visual interface
05 · The real build

From a personal project to a website.

Then I actually built it. I printed the parts, cut the boards and put the shoe rack together. It was much stronger and more rigid than I expected, and it was genuinely fun to assemble and play with different configurations.

The whole process just made sense. Design it, print the connectors, make simple cuts, and put it together.

At that point I had already put so much work into making the system useful for myself that I thought it could be useful to other people too. So I kept going and turned it into a website.

Since then I have been adding and refining things constantly. Build packages, BOMs, measurements, Scene view, sharing, Community Designs and more. The Scene view helps make the real size of a design easier to imagine. Community Designs lets people share ideas, remix them and hopefully build things I never would have thought of.

First finished HexaNect shoe rack after assembly
Why the name?

Why “HexaNect”?

Naming it took longer than it should have. HexaLink, HexaJoin, HexaNex... most of the obvious ones were already taken.

I liked HexaNex because nexus means a connection, link, or point where things come together. Then I found out nex in Latin can also refer to a violent death. Not exactly the association I wanted for furniture.

HexaNect was the closest available thing that still fit. Hexa for the geometry, and Nect inspired by nectere, to bind, join or connect. It stuck.

Still building it

It started because I needed a shoe rack.

HexaNect is still evolving. I'm adding or refining something almost every day, and there is plenty more I want to do. Now I want to see what other people build with it.