Tiiks vs BikeRevive: Rider Judgment vs a Black-Box Algorithm

BikeRevive estimates wear from Strava metrics you cannot see inside the formula. Tiiks shows the kilometers and lets you decide service or replace.

A wet descent with a lot of shifting feels harder on a chain than a dry flat in one gear. That instinct is real. Turning the instinct into a number you cannot inspect is a different move. You either trust the number because the marketing sounds like research, or you ignore it the first time it disagrees with a chain gauge.

BikeRevive, at bikerevive.app, is built on that second move. It pulls wear from Strava ride metrics: distance, power, cadence, weather, speed, elevation, shifting. You set a maintenance level — rarely, monthly, or after dirty rides — and an algorithm that they describe as research plus manufacturer guidelines plus your ride data decides how tired the parts are. iOS is live. Android is a beta you request through a contact form. There is no parts catalog and no rider community. You cannot see the formula.

Tiiks also starts from Strava. We stop at the part of Strava you can defend: distance on the bike, applied to the parts that were mounted. We do not run a watt model, a weather model, or a shifting model. We show the kilometers, the catalog identity, the reviews with real mileage, the widget, and a service-versus-replace call you make. Judgment stays with you. The box stays open. A wet month is something you already know you had. You do not need a hidden coefficient to decide to look at the chain early. You need the kilometers to be on that chain when you look.

What BikeRevive claims to compute

BikeRevive's pitch is automatic wear that is smarter than odometer math. Distance is only one input. Power and cadence change how hard the drivetrain worked. Weather stands in for grit and wet. Speed and elevation change the story of the ride. Shifting stands in for how much the chain moved across the cassette. On paper, that is a richer picture than kilometers alone. In the hand, it is a richer picture you cannot audit. Every extra input is another place the score can move without you seeing why.

The rider-facing control is coarse: how often you maintain — rarely, monthly, after dirty rides. The rest is the model. They say it comes from research, manufacturer guidelines, and the ride data itself. That may be carefully built. You still cannot open it. There is no catalog to name the chain, and no community of riders comparing notes at a real mileage. iOS you can download. Android you can ask for. The product is the score the formula emits, not a record you can audit.

Mileage you can inspect

Tiiks is native on iOS and Android today, not Android-later-if-you-email-us. Strava syncs automatically. Each component gets the distance from rides it was mounted for. That number is boring and checkable. You can hold it next to a chain gauge, a pad measurement, or a shop receipt. We do not multiply it by weather or by watts, because we did not ship those models and we will not invent them in a blog post.

What we add instead is context you can read. A real parts catalog names the component. Verified rider reviews carry real kilometers on that component, which is a human model: people who rode this part this far. The widget puts the bike on the home screen. Service versus replace keeps a dirty-ride clean from looking like a new chain. The full history stays when the part comes off. You are looking at a record, not a verdict. A verdict is done when the score updates. A record is done when you decide, with the number still sitting there.

A formula you cannot see vs kilometers you can

A black box can be right and still be a bad tool. If BikeRevive tells you the chain is at 80 percent and the gauge says 0.5 percent, you have no lever except the coarse maintenance level. You cannot see whether weather dominated, whether a power spike counted twice, or whether shifting on a compact road bike is weighted like a 1x gravel bike. Trust becomes faith.

Kilometers you can see are slower to impress and faster to argue with. If Tiiks says 3,200 km and you installed the chain at a known date, you can reconcile the number. If you disagree, you service or replace based on a measurement, and the history still shows the distance. We would rather be the odometer you correct than the algorithm you cannot interrogate. That is a product choice, not a lack of research.

Power, weather, and shifting vs distance you already trust

Power, cadence, weather, speed, elevation, and shifting are real stresses. They are also incomplete, noisy, and easy to overweight. Not every ride has power. Weather on a file is not the grit in your chain. Shifting metrics depend on the head unit and the groupset. Building a wear model on that stack is ambitious. It is also how you end up explaining to a rider why a dry recovery spin aged a cassette.

Distance is the metric riders already trust, because it is the metric they already recorded. Tiiks uses that, per component, and then lets you apply judgment: you were in wet grit for a month, so you inspect early; you waxed after every dirty ride, so you stretch a bit. The maintenance level in BikeRevive is trying to encode that judgment inside the box. We leave it outside, where you can change your mind without wondering what the model just did.

No catalog vs real parts and rider reviews

An algorithm that does not know which chain you installed is generalizing across every 12-speed in the drawer. Manufacturer guidelines differ by model. Rider reviews differ by use. BikeRevive has neither a catalog nor a community, so the formula is the only identity the part gets. Tiiks starts from the model on the bike and from riders who put real mileage on that model. That is slower than a score. It is also evidence you can read. A guideline that was written for a different chain in a different year is not a substitute for 'this exact model, this many kilometers, these riders.'

iOS now, Android later vs native on both

iOS live and Android beta via a contact form is a shipping sequence, not a platform story. If you are on an iPhone, BikeRevive is in the store. If you are on Android, you are asking to be included. Tiiks ships native iOS and Android as the product, not as a waitlist. A wear record that cannot follow a household with two operating systems is a record that will get screenshotted into a chat and then lost. Screenshots are not a history. They are how a beta becomes a rumor.

Who wants an algorithm, who wants a record

Pick BikeRevive if you want Strava to feed a wear score, you like the idea that power, weather, and shifting should matter, and you are willing to treat the formula as a given. You will set rarely, monthly, or after dirty rides and live with the output. You are on iOS, or you are willing to request the Android beta. You do not need a catalog or a community. The verdict is the product.

Pick Tiiks if you want the box open. Automatic Strava distance on named parts, a catalog, reviews with real kilometers, a widget, service versus replace, a full history, native iOS and Android. You will bring the judgment — wet month, wax habit, chain gauge — and we will bring the mileage you can check. You do not want a watt model we did not build. You want a record you can defend at the workstand.

Questions we get

Can you see BikeRevive's wear formula?

No. You set a maintenance level and the app consumes Strava metrics — distance, power, cadence, weather, speed, elevation, shifting — behind a model they describe as research plus manufacturer guidelines plus ride data. The formula itself is not something you can inspect, which is the whole comparison. If you need to see the math, this is not the app that shows it.

Does Tiiks use power, weather, or cadence?

No. We do not run a watt model, a weather model, or a cadence model. Tiiks applies Strava distance to the parts that were mounted and leaves the rest of the story to you and to a measurement. That is narrower than BikeRevive on purpose. It is also why the number on the widget is a number you can reconcile.

Is BikeRevive on Android?

iOS is live. Android is a beta you request through a contact form. That is their current path, not a store listing you can tap tonight. Tiiks is native on both platforms as the shipping product. If Android is a requirement in the household, a waitlist is not a wear record.

If you wanted a black-box score from a rich Strava file, BikeRevive is already that experiment. If you wanted kilometers you can see, on real parts, with a history you can open on either phone, that is the record we keep. Track the bike in Tiiks and keep the judgment where you can still change it.