There is a moment in every build where you already know what you want. You can see the finished setup sitting on the bench. What you don’t have is the list. Which plate, which insert, which rail, and which of them actually fit together instead of just looking like they should. So you open a catalog and start translating: the thing in your head into a stack of individual parts, hoping you got the compatibility math right before the box shows up.
That translation is a tax. You pay it every time a store hands you a wall of parts and leaves the system-thinking to you.
The new FORG3D site is built to stop charging it.
A catalog sells parts. A system builds with you.
A catalog is optimized for browsing. Rows of products, a filter sidebar, a search bar, everything flattened to the same level so you can scan it fast. That works when you want one thing. It falls apart the moment you want a setup, because a setup is not a list of parts. It is a set of relationships. The plate matters in relation to the grid. The insert matters in relation to the Systainer. The rail matters in relation to what it carries.
Name the parts and you have a shopping list. Name the relationships and you have a system. The old site was good at the first. The rebuild is organized around the second.
Built for ___, not sorted by SKU
Open the new site and the first thing that orients you is not just a product grid. It is intent. The System lays out how the families relate to each other. Built For names what each part of the system was engineered around: Built for Systainer, Built for the DIYer, Built for the maker.
That framing is deliberate, and it runs all the way down. FORG3D does not build a system for you to adapt to. We build a system that adapts to your tools, your shop, your jobsite, your workflow. The site finally reads the way the products were designed. The navigation is just being honest about what was always true.
The families, and the seams between them
The point of a system is that the pieces know about each other. If SYS-GRP is control and SYS-SRF is the stage, the value is not in any single family. It is in the seams where they meet.
A concrete one: the SYS-SRF Extrusion Kit runs anodized rails down its side, and SYS-GRP workholding hangs off those rails. The surface stops being a top and starts behaving like a platform, because a neighboring family was built to attach to it. Storage works the same way. SYS-FIT racks and mounts the Systainer stack, SYS-ORG bins fill it, and SYS-GRD drawer grids organize what the bins hold. None of those are impressive alone. Together they are the difference between owning parts and owning a workflow.
The new site shows those seams. On a product page you will see what a part pairs with, not as an upsell strip, but as the actual set of things engineered to work alongside it. The site surfaces the relationship because the relationship is the product.
Why the site is shaped this way
Every layout choice traces back to removing that translation tax.
The System section exists so you can see the families as a whole before you drill into one. Built For exists so you can enter through your work, the trade or tool or ecosystem you already live in, instead of through a SKU you have to reverse-engineer. The pairs-with and compatibility detail on each product page exists so the fit is stated up front, not discovered after the second order. The site is not decorated with these sections. It is built out of them.
What this actually means
Honest limit, stated plainly: the site maps the system. It does not decide your build for you. It will not pretend there is one correct answer to a bench, because there is not. And when we say these families work together, we are not claiming every product clicks into every other product. Some pairings are structural. Some are just neighbors in the same workflow. The site shows you which is which, instead of implying everything is universal.
That distinction is the whole difference between a real system and a marketing claim. We would rather show you the actual edges than sell you a promise that quietly has exceptions.
Where to start
Start where your dominant work lives. If most of your day is workholding, begin there and let the surface and the storage follow. If it is the Systainer stack, begin with fit and organization and let workholding attach later. The system is designed to compound, so you do not have to buy it in order. You buy it in the order that matches your work.
The site now does the part you used to do in your head. It holds the relationships so you can think about the build instead of the parts list.
That is the system learning to explain itself. The next step is the system learning you: your bench, your kit, the piece that completes it. That is what your account is being built to do, and it is where we are headed next.
Your Workflow. Without Limits.
FAQ
What is the "system" behind FORG3D products?
FORG3D products are organized into families (workholding, work surfaces, Systainer fit and racking, organizer bins, drawer grids, rail slides, and more) that are engineered to work together. The system is the set of relationships between those families, not any single product.
What does "Built for ___" mean?
It is how FORG3D names what a part of the system was engineered around: Built for Systainer, Built for the DIYer, Built for the maker. It resolves, on your account, to Built for you. "Built for Systainer" covers both Tanos and Festool, which are the same underlying ecosystem.
Do all FORG3D products work with each other?
No, and the site is deliberate about that. Some pairings are structural connections; others are simply products used in the same workflow. Each product page states what it actually pairs with rather than implying universal compatibility.
Where should I start if I am new to the system?
Start where your dominant work lives. Pick the family that matches most of your day and expand from there. The system is designed to compound in any order, so there is no required starting point beyond your own work.