atproto.
No need to understand all of this to use Kimbia - come back whenever you're curious. The point: you stay in control of your data, every step of the way.
Identity.
Your handle is the login. No email, no password. The same handle works across every atproto app - Bluesky today, a dozen more tomorrow. Bring one you already have, or take one we offer below.
Your hosting.
If you do not have an atproto identity yet, Kimbia hosts one for you - on what atproto calls a PDS (Personal Data Server), your personal data space. Pick the prefix that fits you.
Hosted in Germany, in Frankfurt · EU · GDPR · self-managed, no third party holds the keys.
Privacy.
A training journal is not a public timeline. Your home, your kid's school route, your rest-day HR - those never go public. Your race PR - you post it proudly. atproto records today are all-or-nothing, which does not fit.
Hence the slider, private ↔ public. By default every activity is private - you and your coach, nobody else; one tap makes it public. Until atproto standardises fine-grained visibility (permissioned data), that private is our own version: your data lives in Kimbia's database and we hold the boundaries. The moment the spec lands, we go fully in-protocol - and until then, you can export the full archive whenever you like.
Connectivity.
The ecosystem grows by the month. Share a race card to Bluesky. Join a race event from a collaborative event app. Let a coaching app read your training load. As atproto apps light up, Kimbia records flow with them - not because we build every feature, but because the protocol lets other apps read and write the same data, with your consent.