Desktop downloads

Install the local engine that peels the links.

The website handles account, billing, relay, and discovery. The desktop client performs local resolution and outbound synchronization.

Build

macOS Apple Silicon

Native build for M-series Macs.

Download

Ready to download.

Build

macOS Intel

Intel fallback build for older Macs.

Download

Ready to download.

Build

Windows

64-bit desktop build for Windows.

Download

Ready to download.

Install command deck

Pick the build, then prove the desktop is attached.

The download page should do more than expose artifacts. It should explain what the operator installs, how the account attaches, and which cloud surfaces become available after the desktop signs in.

recommended build

macOS Apple Silicon for M-series operators.

Use the native Apple Silicon build when the operator machine resolves links from an M-series Mac and needs local browser context.

install path 01 download, sign in, confirm device state.

artifact.selected -> macos_arm64

account.sign_in -> device.visible

Account ready Create or open the website account first so plan state, downloads, and desktop password setup share one identity.

identity check

Device linked After desktop sign-in, the account center should show the linked device and its cloud-side runtime state.

device check

Source selected Choose Google Sheets for visible review or platform API mode for hosted rows before recurring jobs run.

source check

Resolution tested Run a small link batch and confirm final URL, conclusion, checked time, and failure state are written back.

runtime check

Install workflow

What happens after download?

The desktop app is the local execution engine. After signing in, it can pull cloud work, resolve links, synchronize rows, and expose the operator interface for configuration.

Sign in with the same account

Use your website account email and desktop password so the device can attach to the correct membership and cloud state.

Select a data channel

Choose Google Sheets for user-owned spreadsheets or platform API for hosted row storage and external triggers.

Run or schedule resolution

Execute link checks manually or through configured schedules, then write final link conclusions back to the selected source.

Install readiness

The desktop is ready when these four checks pass.

Teams should treat installation as an operational handoff, not a file download. The ready state is account linkage, device visibility, source selection, and verified result writeback.

Identity Website account and desktop password are aligned

The same account identity controls membership, downloads, device state, API key inventory, and desktop sign-in.

Device The desktop appears in account center

Cloud-side device state proves the local runtime can participate in outbound work pickup.

Data A source channel is configured before volume

Google Sheets and platform API mode define where rows are read and where verified results return.

Runtime A small batch produces final URL evidence

Operators should see final URL, conclusion, error or skip reason, and checked time before scaling.

Download FAQ

Desktop setup questions.

Which desktop platforms are supported?

The site can expose macOS Apple Silicon, macOS Intel, Windows, and Linux artifacts when the configured release URLs are available.

Does the desktop need the web service?

Yes for account, membership, platform API, queue, and cloud state workflows. Local execution still happens inside the desktop app.

Can the download links point to external hosting?

Yes. The web runtime can link to external artifact URLs or serve files from the configured downloads directory.

Why install a desktop app at all?

Redirect resolution can depend on local browser, proxy, and device context, so a local execution engine is more reliable than a purely hosted fetcher.