Tiiks vs Componentry: Knowing the Bike vs Modelling It Behind a Paywall

Componentry is strong at prediction models: watt-loss, lifespan, race-day readiness. Tiiks is strong at the bike you can name — catalog parts, mileage reviews, and history from rides.

The race is over and the chain looks the same as it did at the start line. You know that is a lie. You felt the shift get sloppy on the last climb, and you have a number in your head that is not quite a measurement. Some apps will now hand you a watt. They will tell you what the chain is costing, when it will die, whether tomorrow is a good day to be brave on it. That can be intoxicating. It can also be a model standing between you and the part.

Riders who like models are not wrong. A drivetrain does lose efficiency as it wears. Electronic groups do have batteries. A start list does punish a bike that was optimistic last month. The question is what you want the phone to be after a normal Tuesday, when there is no start list and the chain is just a chain. If the answer is a forecast, you will shop one way. If the answer is a named part with a history and other riders’ mileage, you will shop another.

Componentry and Tiiks overlap on Strava and on the idea that components have lives. They diverge as soon as the product has to choose a center. One center is a prediction engine with a trial and then a subscription: watts, dates, readiness, batteries. The other is a bike identity with a catalog and reviews that carry mileage. You can admire both. You should not pretend they are the same screenshot with different paint, or that a readiness score is a substitute for a part you can name.

The two jobs these apps claim

Componentry is native on iOS and Android. It can take rides from Strava, Garmin, Wahoo, and Hammerhead, which is a wider ingest than a Strava-only tracker. The product story is the model: chain power-loss in watts, a personalized lifespan, replacement dates, race-day readiness, and battery state for Di2, AXS, and EPS. After a trial, you pay to keep the model. That is a coherent business if the forecast is the reason you opened the app. It is a weaker community product. There is no sense that a parts catalog and verified rider reviews are the point.

A model can be right and still leave you lonely with a decision. Watts are not a shop receipt. A replacement date is not a review from someone who ran the same cassette to a number you can read. Race-day readiness is a mood the algorithm is willing to name. If you race often, that mood has value. If you maintain a bike through a season of mixed riding, you may want the part to exist as an object, not as a curve that unlocks when the trial ends.

Knowing the bike, not modelling a future

We built Tiiks to know the bike you have. Native iOS first, Android beside it. Strava sync after the ride. Per-component mileage on the slots we track. A real parts catalog with specs. Verified reviews that include how far the reviewer had ridden. A widget on the home screen. Service versus replace, with the history still attached when the new chain goes on. Wear from rides, not from a calendar, and not from a watt we never measured.

We do not estimate chain power-loss in watts. We do not ingest Garmin, Wahoo, or Hammerhead directly. We do not score race-day readiness, and we do not make Di2 battery the hero of the home screen. Those are Componentry’s strengths. Saying we lack them is not modesty theater. It is the product boundary. We would rather name the chain and show you other riders’ miles than invent a laboratory we do not run.

A prediction model versus parts you can name

Componentry’s center of gravity is the forecast. Personalized lifespan and a replacement date are the sentences the app wants to finish for you. That can save a rider who hates deciding. It can also hide the part behind a number that feels more scientific than the input. A model is only as honest as the rides and the assumptions underneath it. If you like watching the curve, you will forgive the subscription. If you wanted to tap a chain and see the actual model from a catalog, the curve is a detour.

Tiiks names the part. You pick it from a catalog when we have it. You see specs. You read reviews that carry mileage. The wear number is the kilometers that landed on that mounted component after Strava syncs. We will tell you when it is time to service or replace. We will not dress that up as a physics paper. The bike stays inspectable. That is a different kind of confidence — closer to a workshop stand than to a dashboard that predicts your next purchase.

Direct head-unit ingest versus Strava rides

If your riding life is Garmin, Wahoo, or Hammerhead and you do not want Strava in the middle, Componentry’s ingest is a real advantage. That is not a small thing for a rider who already refused a social network, and it is not a thing we are going to claim. It is also the feature people accidentally assign to every bike app in this category after one late-night scroll. Read the store page twice. Many trackers, including us, are Strava-shaped, and the honest ones say so before the trial starts.

Tiiks listens to Strava. If the ride is there, the parts move. If the ride lives only on a head unit, we will not pretend we swallowed the file. Riders who already publish to Strava will not feel a hole. Riders who built a private Garmin world will. We are not going to paper over that with a vague “connects to your devices” line. Specific is the only honest comparison.

A trial, then a subscription for the model

Componentry lets you taste the forecast, then asks you to pay to keep it. That is a normal SaaS shape, and it fits a product whose value is the ongoing model. The paywall is not a moral failure. It is a reminder of what you are buying: continued access to predictions. Tiiks is a rider product with a catalog and a history, not a model you rent. If you resent subscriptions on principle, examine which features actually stop when you stop paying. A ledger you own and a forecast you lease are different objects even when both icons sit in a folder named Bike.

Race-day readiness versus rider reviews

Race-day readiness and electronic-group batteries are Componentry speaking to a racer’s week. Useful if you start. Decorative if you do not. Tiiks speaks to the rider who wants other humans in the loop — reviews with real mileage, a catalog you can search, a history you can hand to a mechanic without translating a readiness score. We are weaker as a prediction studio. We are stronger as a place the bike remains a bike. If your season is more start list than coffee ride, you may want their model anyway. Just do not expect it to become a community because the chain number is precise.

Who the model is for, and who the bike is for

Componentry is for the rider who wants a forecast: watts lost on a chain, a replacement date, a race-day readiness call, Di2 or AXS or EPS batteries, and head-unit ingest beyond Strava. If that sentence made your shoulders drop, you have your answer. Pay after the trial if the model earned the week. Do not stay because the screenshots looked like science, and do not stay because a number with a decimal feels more adult than a catalog name.

Tiiks is for the rider who wants to know the bike. iOS first, Android too. Strava after the ride. A catalog you can search. Reviews that include miles. A widget on the home screen. Service or replace, with the history still attached. We are enthusiasts for enthusiasts, and we will not sell you a laboratory we do not operate or a watt we did not measure. If you want the part to stay an object you can talk about with a mechanic, that is our side of the line.

Questions we get

Does Tiiks estimate chain power-loss in watts?

No. Componentry does, and that is a fair reason to open their trial if watt-loss is the sentence you came to hear. We track the kilometers on the chain after Strava rides and help you decide service versus replace. If you want a watt, you want their model. If you want to know how far this chain has gone and what other riders said at a similar distance, you want us. Those answers can coexist on a team bike. They should not be marketed as the same number with different branding.

Can I sync Garmin or Wahoo straight into Tiiks?

Not directly. Publish the ride to Strava and we will take it from there. Componentry’s Garmin, Wahoo, and Hammerhead connections are a genuine difference, not a slogan we are going to copy into this paragraph to look complete. If avoiding Strava is a hard rule in your house, we are the wrong tracker, and you should stop reading for permission. If Strava is already the library, the ingest debate is smaller than the catalog debate, and the catalog is where we spent the product.

Is Componentry more scientific than a rider app?

It is more model-shaped. Science, in the workshop sense, is still a chain tool, a mechanic, and a rider who noticed the shift. A personalized lifespan can be a helpful estimate. It is not a peer-reviewed paper, and it is not a substitute for a catalog part you can identify. We would rather be a precise bike than an imprecise laboratory. If you enjoy the laboratory, use it — and keep the bike’s identity somewhere the trial cannot evict.

If the race is over and you still want the chain to be a part you can name, not a watt you have to subscribe to after a trial, you already felt the split. Keep the model if the forecast earned another month. Keep the readiness score if you start again next weekend. Track this bike in Tiiks and let the rides you already did do the counting, so the next chain is a catalog object with a history instead of a curve behind a paywall.