When the Components You Need Don’t Exist, Build Them
The story behind Zero Components and how an internal Mosaic R&D project became something much bigger.
There’s a point in designing a bike when the parts that already exist begin to dictate what the bike can become. For Mosaic, that point kept coming up. As our bikes evolved, we wanted more tire clearance, cleaner integration, different geometry, and components designed specifically around how we wanted the complete bike to ride. But again and again, the available component options established the boundaries of what we could build.
Eventually, it became pretty clear that if the components we needed didn’t exist, we’d build them ourselves.
That thinking ultimately led to Zero Components, a new line of purpose-built components designed around the performance, fit, and integration requirements of modern bikes. It begins with a family of carbon forks for road, all-road, gravel, and 32-inch gravel bikes. But the story really started several years earlier.
Zero Ops to Zero Components
In 2025, Mosaic publicly introduced Zero Ops, an R&D program that gave our designers and fabricators a place to experiment outside the constraints of our existing production bikes. The idea was to explore what was possible when we could rethink not only the frame, but the manufacturing techniques, components, and integration surrounding it.
The first result was the RT-Zero, an advanced titanium road platform incorporating Mosaic-designed elements including one-piece CNC-machined titanium dropouts and a carbon seatmast and topper. The program later expanded with the AR-Zero, bringing the same approach to an all-road platform.
But Zero Ops was never really about creating a particular bike. It was about giving ourselves room to ask different questions.
What could we build if we weren’t limited by existing production methods? What could we improve if we designed more of the bike as a complete system? And what happens when the component we need isn’t available? That last question became increasingly important.
The Fork We Couldn’t Buy
As we began developing the latest generation of Mosaic gravel bikes, riders were asking for bigger tires and integrated front ends. We wanted those things too. The problem was that the forks available to us dictated what was – and wasn’t – possible.
Instead of designing the bike around those limitations, we flipped the process around, and we developed the fork around the bike. The first major example arrived with the GT i55, where creating our own fork allowed us to build around the geometry, integration, and tire clearance we wanted rather than adapting the frame to an existing fork.
Then came an even bigger challenge with 32-inch wheels. Making a 32-inch gravel bike that actually handled like a performance bike required much more than simply making everything bigger. Axle-to-crown height, fork offset, tire clearance, and toe overlap all became critical pieces of the geometry puzzle.
Again, an off-the-shelf fork wasn’t going to get us there. So we built one.
By that point, we realized we weren’t solving a problem for one particular bike anymore. We were developing a new way of approaching bike design.
Designing the Bike as a System
Handmade frame builders have traditionally relied heavily on what the component industry makes available. Fork dimensions, headset standards, brake routing, axle configurations, and other component standards establish boundaries around what a frame builder can realistically create.
Zero Components gives us another way to move those boundaries. Instead of choosing a fork after the major geometry decisions have already been made, we can develop the frame and fork together.
Fork offset can be selected around the handling characteristics we’re trying to achieve. Axle-to-crown dimensions can become part of the fit and geometry conversation. Tire clearance can be based on the tires riders actually want to use rather than the space an existing fork happens to provide.
It sounds like a subtle distinction, but it changes the design process. We aren’t designing a frame and then finding components that work with it. We’re thinking about the bike as a complete system and designing the pieces around the intended ride experience.
From One Fork to a Complete Family
What started with individual engineering solutions has now grown into the first Zero Components product family. The initial lineup covers Mosaic’s complete drop-bar range, with different fork configurations and offsets developed specifically for road, all-road, gravel, and 32-inch gravel applications.
The family includes:
R35Road Disc Fork: 43mm and 50mm offset options
AR40 All-Road Disc Fork: 47mm and 51mm offset options
G55 Gravel Disc Fork: 55mm offset, purpose-built for modern high-clearance gravel platforms such as the GT i55
G32 32-Inch Gravel Disc Fork: 60mm offset and 110x15mm axle standard, designed specifically around 32-inch gravel wheels
Each exists for a reason. Rather than asking one fork to work across a wide range of bikes, the goal is to give designers the right geometry and configuration for each application.
Bigger Than Mosaic
We also realized along the way that these problems aren’t unique to us. Small OE manufacturers and frame builders across the industry work within many of the same constraints. And the component dimensions or configurations that make sense for a small builder aren’t always priorities for the industry’s largest manufacturers.
That’s why Zero Components isn’t being created exclusively for Mosaic. Following its launch at the MADE Bicycle Show, Zero Components forks will also become available to other frame builders and bicycle manufacturers with compatible designs.
What began as an internal engineering solution is becoming a standalone component business with the potential to give independent builders another set of tools for creating the bikes they want to build. And while Zero Components begins with forks, the name intentionally leaves room for what comes next.
Zero Components Starts Here
Zero Components is about more than adding another logo to a fork. It’s the continuation of the thinking that started with Zero Ops about building the bike we want to build, solving the problems standing in the way, and not letting the components that already exist define what’s possible.


















































































