Weekly volume
Recent distance, as it actually happened.
Asking a runner to estimate their weekly mileage produces a rounded, optimistic number. Your activity history does not round. Connect Strava read-only and let the plan start from what you actually did.

Read-only
Peakora cannot touch your Strava
Real history
A baseline you did not have to guess
Planned vs done
Every session, side by side
History as context
Recent volume, longest runs, typical easy pace, and cross-training make a far better starting point than a dropdown and a hopeful estimate.
Recent distance, as it actually happened.
Where your endurance genuinely sits today.
Frequency, pace, and the mix of what you do.
The next block gets built around the outcome you pick.
Connect, build, compare
Peakora reads relevant activities. It does not post, edit, or delete anything in your Strava account.
Authorize read-only activity access.
Recent training becomes plan context.
Progressive weeks for your goal.
Completed activities line up against scheduled sessions.
After each run
The useful question is whether the run you finished did the job the plan needed it to do.
Compare planned distance against what you actually covered.
Read pace and effort in the context of the intended workout.
Rides and swims count toward the load you are carrying.
Spot the sessions that were missed or quietly cut short.
Look at the week as a whole before changing anything.
Connected training
If your history lives in Strava, connecting it is the fastest route to an informed plan. Apple Health and Health Connect on Android work too, and you can start from manual inputs if you would rather connect nothing at all. Oura is coming.
Available · read-only
Available · HealthKit
Available · Android
Coming soon
Strava-connected training in depth
Peakora requests activity read access and nothing more. It cannot post an activity, rename one, change your privacy settings, or delete anything. You can revoke access from Strava or from Peakora settings at any point, and your Strava data is unaffected either way.
Self-reported weekly mileage tends to be rounded up and remembered generously. Your history is not sentimental about it. Recent weekly distance, longest run, how often you actually got out, and the pace you genuinely hold on easy days are all already recorded — and they make a much more honest starting point than any dropdown.
That gap is where the coaching lives. Matching finished activities against scheduled workouts surfaces the pattern no single activity view will show you: long runs that keep coming up short, easy days drifting faster, the one quality session that quietly never happens.
If you cycle to work or swim twice a week, judging recovery from running alone understates what your body is handling. Supported rides and swims contribute to the workload picture while keeping their sport-specific detail, so a heavy non-running week is visible instead of invisible.
Frequently asked questions
Yes. Recent Strava history becomes the baseline context for a plan built around your chosen goal and schedule.
No. The connection is read-only, so Peakora cannot post, edit, or delete anything in your Strava account.
Activity timing and workout details are compared against scheduled sessions, so completed training can be reviewed against what it was meant to be.
Supported rides and swims contribute to recent workload while keeping their sport-specific context intact.
No. Apple Health through HealthKit and Health Connect on Android both work, and you can start from manual baseline inputs instead.
History into next steps
Connect Strava securely and build a plan with your real training in view.
Start free