Reference
Licensing & Updates
Understand one-time Desktop licenses, seats, activations, online and offline validation, device transfers, recovery, and update eligibility.
License model
Ghostable Desktop is paid software sold with a one-time license. The license does not expire for application versions covered by the purchase, and it includes one year of eligible Desktop updates from the purchase date.
Buying a Desktop license is separate from repository permissions. A licensed person still needs a Ghostable device identity and grants for each encrypted project environment.
Plans and limits
-
Personal — $49 - 1 seat and up to 2 active device activations.
-
Team 5 — $249 - Up to 5 seats and 5 active device activations.
-
Team 10 — $499 - Up to 10 seats and 10 active device activations.
-
Business - Contact Ghostable for larger or custom licensing needs.
These are the current one-time plans documented by the application. The license purchase page is authoritative for current pricing and terms at checkout.
Activate a device
- Open Application Settings → License.
- Paste the entire license key and choose Activate.
- Desktop registers a fingerprint for this installation and stores a protected activation token locally.
- Confirm that the panel reports the expected plan, seat allowance, activations, updates-through date, and offline-until date.
A successful activation enables project windows. The launcher, license form, and Info page remain accessible when no license is active.
Enter the purchase key in Application Settings to activate this Desktop installation.
Seats and activations
A seat represents licensed usage under the plan. An activation is a registered Desktop installation or device. Personal includes two activations for one seat so the licensed person can use more than one machine; team limits scale with the selected plan.
Activations do not replace project access grants. Releasing a Desktop activation does not revoke that machine's repository identity, and revoking a project device does not automatically free a paid Desktop activation.
Offline use
After online activation, Desktop caches a signed entitlement for offline use and attempts validation periodically. The default entitlement window is seven days and the client normally attempts validation every six hours; the Offline until value shown in License settings is authoritative for the entitlement actually issued.
If the cache reaches its valid-until time without a successful validation, project access is blocked until Desktop can validate again. This does not mean the perpetual product license expired; it means the local cached proof is no longer current.
Release or recover a license
Choose Release Device before selling, wiping, or retiring a machine. The release contacts the licensing service, removes this activation, and clears the local activation token.
If the old machine is unavailable or the key is lost, open Manage licenses and request a signed recovery link for the purchase email. Team owners who claimed a license can manage it through their account.
Contact support when an activation cannot be released and automated recovery does not restore access. Never send project secrets or automation tokens with a license request.
Updates and renewal
Check for Updates compares the installed Desktop version with the current release and asks the license service whether that version is covered. If the license's updates-through date covers the release, Desktop can offer the update.
After the included update year, the installed covered version remains licensed. A newer release may report renewal required. Renewing update eligibility extends access to newer versions; it is not a subscription required to keep using the already-covered version.
License data and privacy
Activation and validation send the license key or protected activation token, application version, and device fingerprint needed to enforce the plan. Update checks send version and entitlement context. These requests are separate from Ghostable project operations and do not include environment names, keys, values, repository contents, or .ghostable/ state.
On macOS, the activation token is stored in Keychain under Ghostable's Desktop service. Other supported platforms use Electron-protected local storage when available. See Privacy for the service policy.