Free, Pro and the seven-day trial

Understand which capabilities are included, what the shared trial covers and how device activation differs from connection authentication.

Check the current comparison

Open License in the app, or view the edition comparison on the website. The app shows the current license state and the feature table. The table in your installed version is the best reference when a later release changes limits.

Free includes core SSH connection management, local/remote TCP and Unix-socket forwarding, SOCKS connections within Free limits, Console/SFTP, app master-password/Touch ID unlocking, and local backup capabilities.

Free limits in 2.0.14 include 10 connection profiles, 3 host presets, 3 distinct group tags, and 2 active connections of each forwarding/SOCKS type. Imported local SSH aliases are subject to their displayed limit. Records from older versions remain available even above newer limits; this is not permission to start unlimited concurrent connections.

Shared trial features

The seven-day trial is shared across trial features, not seven fresh days for each feature. Pro features include automation, connection-completion actions, QR sharing/restoration, WebDAV backup, app OTP setup, sequential jump hosts, experimental transparent proxying, supported proxy-browser launch, UDP over SSH, multi-session acceleration and local/remote multi-port forwarding.

When the trial ends without Pro, these features become unavailable. SOCKS multi-session selection returns to the Free single-session policy, and UDP over SSH is unavailable. An ordinary TCP SOCKS profile is distinct from those optional enhancements.

Activate a personal license

Follow the purchase/activation instructions linked from the app. Use the current Mac's authorization request code when requesting a license. Paste the issued license into the app's activation workflow and confirm that License reports an active Pro license.

An authorization request code is not an SSH password or the license itself. Avoid publishing request codes, issued licenses or purchase references in public issues.

Bulk licenses

Bulk purchases use order-specific deployment links and their own seat allocation. A purchase-email approval code and user-email verification protect issuance. One bulk seat corresponds to one Mac authorization request code; it is not the personal-purchase request-code allowance.

An activated bulk license is labeled accordingly. Its deactivation flow distinguishes temporarily deactivating from changing the Mac. Temporary deactivation does not free a seat for another machine. A confirmed device-change workflow verifies the required email code, invalidates the old server-side request code and returns the seat; the app generates a fresh local request code for future activation.

Do not use personal deactivation instructions to infer bulk seat behavior. Read the app's confirmation before continuing, and retain the purchasing administrator's deployment instructions.

What this guide does not test

The comparison and active-license state were inspected. This guide does not execute a purchase, revoke a real license or promise license portability beyond the current purchase and license terms. Contact support for a licensing problem rather than changing SSH settings to address it.