Activation

Activation binds your license to the current machine. After activation, ATAS will launch normally whenever the Bridge service is running.

Flow

1. Desktop reads its machine fingerprint (SHA-256(CPU|MAC|...)).
2. Desktop calls POST /api/v1/auth/login with email + password + fingerprint.
3. Backend issues an HS256 JWT scoped to the machine.
4. Desktop caches the JWT locally for 72 hours (offline grace period).
5. On every atas-bridge.exe start, the JWT is verified against GET /api/v1/license.

Offline behavior

• The first 72 hours after activation are fully offline. ATAS runs.
• After 72 hours the desktop pings GET /api/v1/license on next launch. If reachable, the local cache is renewed. If not, ATAS still runs (the grace window extends to 168 hours).
• Beyond 168 hours offline, ATAS stops launching. The Bridge service exits with a notification pointing to the docs.

What to do if the activation email does not arrive

• Check your spam folder.
• The license is also retrievable at any time via GET /api/v1/auth/login once you have your password.
• For support, contact [email protected] with the payment receipt.