Population Averages
Every platform uses generalized formulas like 220 - age to calculate your max heart rate. Your physiology isn't just "average" though.
Real-time injury alerts and training insights built with your data and sports science, not AI.
Currently supported: Garmin & Polar devices only for beta
The tools runners rely on today are built on assumptions and a lack of context, not your data.
Every platform uses generalized formulas like 220 - age to calculate your max heart rate. Your physiology isn't just "average" though.
Sickness, Injury Risk, PRs, Current Fitness, Phase of season, Max HR. These are all important things to take into context when building your training or insights. Yet, no current platform does.
Charts, graphs and numbers everywhere. Runners spend more time trying to interpret their data than actually using it.
Spikes analyzes wearable data relative to your physiological baseline and training history -- then generates runner-specific insight, not generic charts. Uses ML built on sports science.
6 hours
80
7:30 / mile
90°F
180 bpm
Comparing against your baseline...
Uses ML and Sports Science to analyze your data
Today's Effort
High
Expected
Moderate
Higher-Than-Normal Effort
This run required more physiological strain than your recent runs at similar pace. The engine detected elevated effort relative to your historical patterns.
Recovery Risk Elevated
Low sleep, high stress, heat exposure, and elevated heart rate suggest reduced readiness today.
Keep Next Session Easy
Reduce volume or intensity on your next run to avoid accumulating excess fatigue this week.
Spikes continuously monitors five proven injury precursors from your wearable data, combines them into a single risk score, and alerts you when the science says slow down.
Data we monitor
Acute:Chronic Workload Ratio
Detects dangerous spikes in training load relative to your baseline.
Heart Rate Variability Trend
Flags suppressed HRV patterns that precede overtraining injuries.
Run Efficiency Drop
Biomechanical degradation shows up in efficiency scores before pain does.
Training Monotony
Too much similarity in daily load is a known injury precursor in the research.
Zone Creep
Heart rate drifting into higher zones at the same pace signals accumulated fatigue.
Risk Score
Baseline + trend analysis
Output Alerts
Low Risk
Training load and recovery signals are balanced. You're in a healthy adaptation window.
Elevated Risk
One or more signals are trending toward a concern. Spikes recommends reducing intensity on next session.
High Risk
Multiple injury precursors are active. Spikes sends an alert and recommends a rest or easy day immediately.
A continuously updated injury risk score built from five proven precursors -- ACWR, HRV trends, run efficiency drops, training monotony, and zone creep. When the science says slow down, Spikes tells you.
A full lookback across your key health and training metrics -- HRV, activities, sleep, resting heart rate, ACWR, and more -- so you can spot trends, track recovery, and understand your body over time.
Your max HR is the foundation of every zone, grade, and alert in Spikes. We don't guess it with a formula -- we scrape your top peak HR windows, confidence-grade each one, and refine it as you run more.
Understand the relationship between your pace and heart rate over time. See how your aerobic efficiency evolves and identify when your fitness is genuinely improving -- not just when you ran faster.
Every run gets a grade based on how efficiently you performed -- not just how fast you went. Understand the quality of your effort, not just the quantity.
Your pace doesn't exist in a vacuum. Spikes accounts for temperature, humidity, altitude, elevation, and wind speed -- so a hard run in the heat gets the credit it deserves.
Weekly load calculated with context -- using graded paces instead of raw numbers. Finally, a load metric that actually means something.
Every run is automatically categorized -- easy, tempo, threshold, long run, and more -- based on your actual zones and effort, not just pace. Know what kind of run you did, not just how far.
Ask questions about your training in plain English. Claude contextualizes your data -- zones, load, grades, trends -- against what you're actually training for and gives you answers, not more charts.