ABOUT PITWALL
A focused training sidecar for individual athletes.
Why Pitwall puts athlete-owned plans beside completed training and focuses on the next useful decision instead of another social feed.
Current statusPitwall is operated by De Bonte Koning B.V. in the Netherlands and is running a controlled production closed beta. Invitations are reviewed manually, public registration remains closed, and an open beta follows only after validation.
The problem Pitwall is built around
Athletes can collect detailed training data and still struggle to answer a simple question: is the work they completed moving the plan in the intended direction? Existing tools can be data-rich, socially noisy, or closely tied to one provider.
Pitwall narrows the job. It connects an athlete-approved target to completed work, explains meaningful differences, and prepares the next useful decision without replacing the athlete's watch or provider account.
Athlete control is part of the product
A target is not a command and a suggestion is not a decision. Pitwall is designed so the athlete can inspect proposed changes, correct activity matches, and explicitly approve a workout before it is published to a provider.
- No silent autonomous plan rewriting in V1.
- No social feed, likes, kudos, or leaderboards.
- No claim that one metric can replace athlete context.
Garmin-first, provider-neutral
The first pilot athletes use Garmin, so Garmin Activity and Training API access is the first external request. The internal product model uses provider-neutral goals, plans, sessions, and activities so another connection can be added later without redefining the product.
The closed-beta application and public pages are live for controlled validation. Planning, activity capture, matching, route playback, progress and PR review, Body Check, Buddy, and account controls are working. A temporary Garmin connector is active for approved athletes while official approval and open-beta operations remain pending.
TRAIN. PLAN. PERFORM.