FrameLathe

Compare

Search “AI video enhancer” and you get hosted tabs — Wink and a long tail of the same idea. You upload a clip. They run a model. You download a result. They capture the generic click. They also have to see the media.

A box of tapes is a different job: hours of files, spotty uplink, retention you do not control, and a bill that scales with minutes in someone else’s GPU. FrameLathe is built for that job. Drop the folder. The GPU in the machine works overnight. Footage is not uploaded. There is no cloud processing path.

Snapshot

Cloud / online enhancers (Wink as the named example) FrameLathe
The job One clip in a browser tab Overnight folder queue
Where it runs Their servers Always this PC. No cloud GPU to burst to
You upload the file Yes. That is the product No
Box of tapes Their queue, their compression, their bill Drop the folder. Quick / Full / Best possible. Bounded by the disk, not a credit balance
Morning after Their account Approve / Flag a wipe or difference view. History keeps the recipe, not the video
What leaves the machine Their terms. Wink’s overseas terms grant a licence to store inputs/outputs and to improve their AI features Local processing. EULA §7 allowlist only. The app does not phone home to render
Packaging (18 Sep 2026) Wink Web Creative Plan: Standard 1,000 credits/month, Pro 4,000, valid 31 days. Free exports include a watermark No credits. No upload. No watermark. Price unpublished — waitlist
Best for One public clip Footage that cannot leave the room

The website assistant is not a cloud renderer. It answers from docs. Sharing the result is a comparison MP4 Review exports beside the output, not a link on someone else’s account. Joining the waitlist does not upload footage and does not create an app account. More: why local GPU beats cloud.

Sources (18 September 2026)