Desktop + Website + Account System

Run Link Peeler like a product, not a loose collection of ports.

Link Peeler now has a clear product split: a public web surface for discovery, registration, account management, and downloads, plus a desktop client that executes the local work. Marketing pages, login, registration, and account pages all live in the same public entrypoint.

Download desktop Register now

One web service. Landing pages, auth, account pages, and relay-facing APIs share a single product entry.

Templ pages. No extra frontend deployment is required for the website surface.

Two runtime units. web handles the public product. desktop handles the local operator runtime.

Public website.

The main domain exists for real users: positioning, product explanation, download entry points, login, registration, and account management.

Desktop runtime.

The desktop client stays focused on execution: local data, embedded API, tunnel runtime, and browser automation.

Unified auth chain.

Google-only website access, desktop password setup, token refresh, quota checks, and device state all stay inside one coherent server boundary.