Kimbia pulls your training off the wrist, lays it out like a journal you'll still read in ten years, and keeps the keys in your pocket. Your runs, your rides, your coaching - under one roof that you can take with you.
Join the waitlist →Your training is a decade-long document. It logs your injuries, your breakthroughs, the summer you peaked, the winter you didn't. But the tools that hold it were not built to give it back. Export is a hostage negotiation.
We think the data belongs to the person who earned it - in the sweat, the kilometres, the alarms before sunrise. Kimbia hosts it for you by default. When you want to host it yourself, the door stays open. You can leave with every byte.
"Every split, every beat, every plan - yours forever, portable by design."
We're starting with the sports we actually do - running and cycling - so the first release feels lived-in, not demoed. Multisport, strength, and swim will arrive when we can do them right.
Social is a separate problem from training, so we let Bluesky solve it. Your likes, reposts, replies - all in the app you're already in. Your followers came with you. No new network to convince.
A week is a unit of training. Kimbia reads that way too - one row per week, a circle for every activity, sized by volume. Tap any dot to go deep; pull back for a season. Your years live on a single page.
A north star, not a finished product yet. The first brick is your account - portable by design. The key control is a public-to-private cursor on every activity: what you show, what you keep for yourself, with start-point obfuscation for home and work.
1 Hz GPS, heart rate, power, cadence, temperature, running dynamics. No downsampling to save our servers. Raw FIT files kept alongside parsed records.
A single reference table - Marathon, Half, 10k, 5k, 3k, 1k, 100m, plus HR min / base / max - drives every session's prescribed pace. Updates never automatic, never retroactive.
Invite a coach for a window of time - they can see and edit plans during it. Revoke whenever: they keep read-only access to the data from their period, nothing more. Multiple windows supported, so the story stays coherent across seasons. Templates auto-adapt to each athlete's current metrics.
Race predictions (Riegel, VDOT, Cameron, one trained on your own data) shown side-by-side. A peak-form window that says when you're sharp. A rest signal when you're not. Nothing touches your metrics without you.
A polished share card with stats and route preview, posted to Bluesky with the title you choose. Likes, reposts, and replies stay where your people already are. Nothing forced, everything optional.
The plan says 3 × 2000m at 4:15 ± 3s. What actually happened? Kimbia lines up each prescribed segment against the matching effort and tells you, per rep, what went right - too fast, too slow, HR too high, on target. Insight, not just numbers.
Honest, controlled. RPE 3/10.
Felt good. Your rating: 4/5 · effort 7/10
Your global metrics define who you are, athletically, today. Every training prescription is derived from them - and copied into the plan at creation, so a half-marathon workout from two years ago still reflects the runner you were then.
Amber dots are snapshots frozen with each plan. Past plans keep their pace; new plans use today's. The reference travels with the session.
Race result (red) may revise the table on confirmation. Predicted times never do.
Invite a coach for a window - a season, a block, a year. They see all your data and edit plans inside that window. Invite two in parallel if you need a run coach and a strength coach.
End a window whenever you like. They keep read-only access to what happened on their watch - so last season's story stays coherent - but the next chapter is yours alone until you invite again.
Build a session once - a 6 x 1000m at threshold - and drop it onto any athlete's calendar. Paces re-derive against their current metrics.
After the session the athlete rates it - effort and how it felt, the way a watch asks. You see whether a 3/10 landed at 3/10. The feedback loop is short, legible, and stored with the workout itself.
Today: we host. Tomorrow: you can too - on your own server, with a protocol built to move. Auth is the first brick we've laid; the rest follows as the open standards mature. This is the vision, stated out loud.
One sign-up. Full history. We store your activities, back them up, let you export any time. Free during beta.
Bring your own storage, point Kimbia at it, keep every feature. The plan, not today's state - arriving as the protocol matures.
Running first. Garmin first. We'd rather nail one sport and one device than demo five. The rest follows in the honest order below.
The watch I wear, the sync I need. Full-fidelity ingestion on day one. Manual FIT upload for everyone else.
Left-page intent, right-page truth. Per-segment verdict on each interval. Notes and comments pinned to the day.
Bring every activity from the apps you are leaving. Migration is a priority, not an afterthought.
Cycling next, then swim, strength, triathlon. Bring-your-own storage when the protocol is ready.
We want this to work, so here it is plain: donations keep us running. If Kimbia makes your training better, help us grow. Coaches who take us past 5 athletes - we give you the best tool on the market, you earn money using it, you pitch in. That's the deal. No ads, no data sale, ever.
Three things. One: you can export everything, in open formats, any time. Two: nothing's sold or fed to ad networks. Three: the longer-term plan is to let you host your own copy on your own server - the vision we're walking towards, not where we're standing today.
Because a prescription reflects the athlete who received it. A 2024 plan should still read at its 2024 paces - that's what you actually ran. New plans always use today's metrics.
A public-to-private cursor on every activity: private, coach-only, followers, public. Privacy zones hide start and end points from any public view. Private by default.
Not yet. The first release is post-activity sync and analysis. Live tracking is a different product.
All of them, shown side-by-side. Riegel, VDOT, Cameron, and a model trained on your own history - plus a peak-form window and a rest signal. A predicted time never updates your metrics on its own.
No launch date yet - we're still making decisions in public and building slowly. The waitlist gets first invites and a say in what ships first.