Trial credits, this article is retired
This article described an old per-device generation credit. It is retained as a dated correction, not as current usage guidance.
Rackd is local-first. Training data starts on the device where you log it, so a network connection is not the first dependency between you and the next set.
When you log a set, the weight, reps, RPE, and timestamp are written to the local training record first. The app can keep the session moving when the signal is poor.
Programs, workouts, history, and progression inputs follow the same local-first shape. Export and optional sync are covered in the articles below.
The local training core does not need a web account to store the record on the device. A sign-in may be needed for an optional account surface such as sync or web access, depending on the release you are using.
The selected catalog contains 15 programs, 11 progression systems, and 448 exercises.
Cloud Sync is optional and off by default. If your release exposes it, read Backup vs Sync before turning it on. Sync is a mirror between devices, not a replacement for an export you control.
If you train on one device, local-first is the whole job. If you need another device, use only the account and sync flow shown by the release you installed.
This article described an old per-device generation credit. It is retained as a dated correction, not as current usage guidance.
Backup is a file you keep. Sync is an optional mirror between devices. They solve different problems.
Rackd is local-first. If your release exposes optional sync, use the same account on each device and keep a backup as well.