FrameLathe

Docs

The product claim is specific: processing is local. The installer is still allowed to use the network for a short list of jobs. That list is in EULA §7, not a slogan.

Desktop app

The software runs on your computer and processes your video locally. It connects to the internet only to:

  • check for and download updates
  • activate or release a licence key when you ask it to
  • download NVIDIA and PyTorch wheels for the GPU add-on pack when you request it
  • download model weights you request
  • load the public model index when you open Model Hub

Activation happens when you paste a key in Settings, not at launch and not when a job runs. What is sent is the key and a fingerprint derived at activation. It is not stored as hardware inventory. It is not sent at launch or at render. Checking for updates may ask whether that key is still offered updates; that lookup does not send the fingerprint, and it does not run if the update check is off. The app does not phone home to run.

It sends no usage analytics, no crash reports, and no information about your files to FrameLathe.

There is no cloud processing path. Joining the waitlist does not upload footage and does not create an app account.

This website

The site is separate from the renderer:

  • Waitlist email lives in Cloudflare D1 so we can send a confirm mail and one launch mail.
  • The optional docs assistant runs on Cloudflare Workers AI over published docs, not over your media.
  • If you ask to talk to a human, the Worker emails the team. It does not open a third-party helpdesk.

Details: Privacy and EULA.