Update · BikePartPicker Updates
BikePartPicker Is Live in Beta: What You Can Do Today and What's Next
See what the BikePartPicker beta can do today, where its compatibility coverage stops, and what we plan to build next.
By BikePartPicker Editorial
Published · Updated · 3 min read

BikePartPicker is live, but it isn't finished. The beta already lets you start with a frameset, choose reviewed components, and catch supported compatibility conflicts before they become expensive mistakes.
The catalog is still growing, and some compatibility questions are not covered yet. When we do not have enough evidence, the answer stays unknown. That is better than guessing.
What You Can Do Today
Start a build and BikePartPicker will walk you through the component slots that follow from your frameset. As you add parts, the builder updates its compatibility status, estimated weight, estimated total, and build completion.
A red or green result is not enough. Each compatibility note names the parts and interface involved. Conditional results and unknowns stay visible, so you know what still needs checking.
You do not need an account. Your working draft stays on the device you are using. Once a frameset has been selected, you can publish a stable, read-only snapshot and send the link to a friend, riding group, or mechanic.
You can also browse the parts catalog without starting a build. Category and product pages show specifications, source evidence, whether compatibility has been reviewed, and current retailer information.

Which Brands Are in the Catalog?
The catalog already includes reviewed products and manufacturer documentation from these brands:
- Drivetrain and braking coverage includes Campagnolo, Shimano, SRAM, microSHIFT, KMC, Praxis Works, ROTOR, Tektro, and TRP.
- Wheels and tires include Continental, DT Swiss, ENVE, Hunt, Mavic, Panaracer, Pirelli, Schwalbe, Stan's NoTubes, Vittoria, WTB, and Zipp.
- Frames, cockpit parts, and saddles include Fizik, Ritchey, Salsa, Specialized, Surly, Vision, and WTB.
This is a launch snapshot, not a permanent boundary. The live parts catalog is the better place to check what is available now.
What Beta Means
BikePartPicker is focused on modern street and gravel builds. That includes road, all-road, commuter, fixed-gear, and single-speed projects where the catalog evidence and compatibility rules support the required interfaces.
It is not a universal bicycle database. Some brands, product families, older standards, and component relationships are still missing. Retailer prices and stock can change after their latest check. A part can also be documented well enough to appear in the catalog while one of its compatibility relationships remains unknown.
The builder is planning guidance, not an inspection or installation guarantee. Check the exact model and size against current manufacturer documentation before buying. Have a qualified mechanic review the final build, especially when a mistake could affect braking, steering, or wheel retention. The full compatibility methodology explains how we handle evidence and uncertainty.
What We Are Building Next
Our next major feature starts with a bike you already own.
We want you to be able to select the exact bike, load its original components, and replace one part at a time. BikePartPicker could then show compatible upgrades and compare cost, weight, and gearing before and after the change.
That workflow has not shipped yet. We do not have a launch date to share. To make it useful, we need exact bike variants, trustworthy stock component lists, and the same evidence standards used by the current builder.
We will keep adding reviewed manufacturers, useful product categories, retailer listings, and compatibility rules. A larger catalog only helps if it produces answers riders can understand and verify.
Help Us Improve the Beta
If a product is missing, a specification looks wrong, or a compatibility result needs another look, send us a correction. Reports enter a review queue and do not automatically change a public result.
If you are ready to try the current workflow, start with a frameset. Build something you would actually ride, then tell us where the process still gets in your way.