PeakRunning — FAQ
Questions answered.
Excuses removed.
PeakRunning is a Runner's Operating System: training structure, dialed-in paces, daily check-ins, and a small squad that notices when you disappear. Here is how the beta, squads, adaptive training, and tracker data are intended to work.
Beta invites roll out to select training groups · One email · No credit card
Week 4 / 12
Build Volume
45
mi target
- MONRESTActive recovery–
- TUEEASYAerobic base6
- WEDSPEED8×400m @ 5k pace8
- THUEASYRecovery jog5
- FRITEMPO3×2mi @ HMP9
- SATRESTPrep for LR–
- SUNLONGTime on feet16
Beta access
Get on the list. Know what happens next.
The beta is rolling out by training group. These answers set the expectation without pretending the doors are already wide open.
What is PeakRunning?+
PeakRunning is a training, accountability, and small-group community app for serious-but-not-elite runners. It combines weekly training structure and target paces with binary daily check-ins, visible streaks, adherence stats, and invite-only squads of 5–10 runners. It is not trying to replace your watch or become another activity feed; it is the layer that turns a plan into work completed consistently.
How do I join the PeakRunning beta?+
Submit your email through the Request Beta Access form. PeakRunning is rolling out invitations to select training groups rather than opening every account at once. Joining the waitlist requests access; it does not guarantee an immediate invitation or a specific start date.
What happens after I join the waitlist?+
Your email is added to the PeakRunning waitlist. When a suitable beta opening or training-group cohort is available, PeakRunning can contact you with next steps. Waitlist members are invited before public launch and may have opportunities to influence the roadmap through real use and direct feedback.
Does joining the waitlist cost anything?+
No. Joining the waitlist only requires an email address and does not require a credit card. Any plan or payment choice will be presented clearly before a paid subscription begins.
Why is access rolling out by training group?+
The product depends on real accountability, not empty profiles. Cohort-based rollout makes it possible to form useful squads, observe whether check-ins and alerts create the right behavior, and improve the training experience before a broad launch.
Will every beta member get the same features?+
Not necessarily. PeakRunning is still in beta, so feature availability and onboarding may vary by cohort. Your invitation will state what is available to you, including the current training workflow and any supported data connection.
High-signal squads
Small enough to notice. Serious enough to act.
The squad is not an audience. It is a compact accountability system built around visible execution and useful pressure.
What is a high-signal squad?+
A high-signal squad is a private group of 5–10 runners organized around a shared goal rather than a public feed. It is small enough that absence is visible, focused enough that training updates matter, and structured enough to keep accountability from dissolving into chatter.
Why are squads limited to 5–10 runners?+
Accountability weakens when nobody can tell who is missing. A 5–10 person group is designed to stay personal: every runner can recognize the roster, see check-ins and streaks, and notice when somebody goes quiet. The goal is not maximum reach. The goal is useful pressure.
How does daily accountability work?+
Each day, runners give a simple signal: Crushed It or Skipped. That check-in feeds visible streaks, adherence percentages, a 12-week history, and the squad activity view. PeakRunning deliberately keeps the action simple so there is less room to hide behind elaborate explanations.
What happens if I stop checking in?+
A runner who has not checked in for two or more days can be flagged as a quiet member. That makes drift visible to a captain or coach early, when a direct nudge can still change the week. It is accountability, not public humiliation: the purpose is to pull runners back into the work.
Who runs a squad?+
A captain manages the roster, shared goal, weekly mileage target, and training schedule. Runners focus on the work: view the schedule, check in, track their streak and adherence, and support the rest of the squad. Coaches can oversee multiple squads through a cross-squad view where available.
Can I join with my existing running group?+
PeakRunning is designed for real training groups as well as matched beta cohorts. The captain-led model, invite codes, shared goal race, and small roster let an existing crew move its accountability into one focused system. Availability during beta depends on the cohort and invitation process.
Is ruthless accountability the same as punishment?+
No. Ruthless means the signal stays honest. A skipped session is recorded as skipped, silence is visible, and a broken streak is not disguised by likes or motivational noise. Smart training still includes rest, recovery, and changed sessions; the standard is honest execution of the plan, not running through pain.
Adaptive training
The plan bends. The standard does not.
Adaptation protects the purpose of the training block while responding to completed work, readiness, and real life.
What does adaptive training mean in PeakRunning?+
Adaptive training means the plan responds to the runner rather than remaining frozen regardless of execution and recovery. Useful adaptation can involve changing session timing, intensity, volume, target pace, or recovery based on recent efforts, completed work, and readiness. The purpose is controlled progression, not random daily changes.
What information can affect an adaptive plan?+
Relevant inputs may include recent mileage, workout completion, pace or effort, skipped sessions, goal race, training phase, and recovery feedback. Connected tracker data can reduce manual entry when supported, but the accountability system does not need a GPS file to know whether you showed up and checked in.
Does the plan change every day?+
Not simply for novelty. An adaptive plan should preserve the purpose and progression of a training block while adjusting when the evidence calls for it. One missed easy run does not require panic; repeated skipped work, accumulated fatigue, or a major schedule change may justify a more meaningful adjustment.
How are target paces set?+
Target paces should reflect the runner's current ability and the purpose of the session, then become more precise as recent effort data becomes available. Easy, tempo, interval, and race-specific work should not all be run at the same effort. Exact pace-setting and automation may vary during beta, so your invitation and in-product guidance are the authority for your cohort.
Does adaptive mean I should run through soreness or injury?+
No. PeakRunning is not medical care, and accountability is not permission to ignore pain. Training progression should be gradual and responsive to health status and exercise response. Stop or modify training when needed, and seek a qualified clinician or coach for pain, injury, illness, or a return-to-running decision.
Garmin, Strava & data
Your tracker records. PeakRunning organizes.
Connections require consent and specific permissions. The core accountability loop remains useful without a GPS file.
Do I need Garmin or Strava to use PeakRunning?+
No. PeakRunning's core accountability workflow is intentionally usable without a GPS watch or public activity feed. A watch can record the run; PeakRunning's job is to organize the work, make the daily commitment visible, and keep the squad honest.
Does PeakRunning currently sync with Garmin?+
PeakRunning does not publicly guarantee Garmin syncing for every beta cohort. Garmin supports partner integrations through its Connect Developer Program: users provide consent, sync a device to Garmin Connect, and approved applications can receive activity data. If Garmin connectivity is enabled for your cohort, PeakRunning will state the supported data and permissions during onboarding.
Does PeakRunning currently sync with Strava?+
PeakRunning does not publicly guarantee Strava syncing for every beta cohort. Strava integrations require each athlete to authorize the application through OAuth and approve specific activity permissions. If Strava connectivity is offered in your beta, you will see a clear authorization flow and can revoke access through Strava.
What data could a tracker connection provide?+
With the runner's authorization and a supported integration, activity data can include completed activity time, distance, pace, route-related details, and workout files. PeakRunning should request only the permissions and data needed for training and accountability features rather than treating a connected account as unlimited access.
Will PeakRunning post workouts back to Garmin or Strava?+
Do not assume two-way syncing. Reading completed activities and sending structured workouts are different permissions and APIs. Any feature that publishes a workout, uploads an activity, or edits third-party data will be labeled explicitly before you connect the account.
Can I disconnect Garmin or Strava later?+
A properly implemented connection is revocable. Strava allows athletes to revoke an application's access, and Garmin's program uses user consent and permissions. PeakRunning will provide clear connection status and disconnection guidance whenever an integration is available.
Does my squad see all my tracker data?+
The squad should see accountability signals needed for the group experience, not unrestricted access to every metric in a connected fitness account. Exact visibility will be explained in-product before a connection is authorized. Privacy settings and permissions remain distinct from the simple Crushed It or Skipped check-in.
Accountability & safety
Ruthless honesty. Intelligent restraint.
PeakRunning expects a truthful signal, not reckless training through pain or a substitute for qualified medical advice.
Is PeakRunning a replacement for a running coach?+
No. PeakRunning can provide training structure, shared schedules, paces, adherence visibility, and squad pressure. A qualified coach adds individualized judgment, technique feedback, race strategy, and context for injury or complex training needs. PeakRunning also supports coach-led squads rather than forcing runners to choose between software and a human coach.
Who is PeakRunning best for?+
PeakRunning is for runners past the beginner stage who know they can do more with better structure and stronger follow-through. It is especially relevant when the limiting factor is not another dashboard of data, but consistency: knowing what to do, doing it, and being accountable when you do not.
Who is PeakRunning not for?+
It is not a medical device, injury-diagnosis service, GPS replacement, or passive social feed. It is also a poor fit for runners who want completely private, consequence-free training with no group visibility. The product is built around honest check-ins and a squad that notices.
What is the shortest explanation of PeakRunning?+
The coaching app has no crew. The crew app has no coach. PeakRunning is both: an adaptive training structure plus a small squad that makes execution visible.
Research notes
Product truth first.
Tracker answers are grounded in official platform requirements. Training language is intentionally educational, not medical advice.
- PeakRunning features
Current product workflow, squads, roles, check-ins, and alerts.
- Strava API authentication
OAuth consent, scopes, tokens, and revocation.
- Garmin Connect Activity API
Partner approval, consent, sync flow, and activity data.
- Individualized endurance training study
Recovery-aware adjustment and controlled training progression.
Are you in?
Beta invitations are rolling out to select training groups. Join the waitlist to secure your spot.
- Early access before public launch
- Founding-member status
- Direct input on the roadmap
Spots strictly limited · No spam ever