Getting started with FLY8HT

FLY8HT’s whole job is this: you give it a project, it works out how to run it, and it runs it on your own computer, at localhost. Here’s exactly what that looks like the first time.

1. Open the desktop app and choose a source

On the Home screen, switch between GitHub and Local. For GitHub, paste a repository URL (a branch picker appears automatically once FLY8HT recognizes it). For Local, drag a folder onto the drop zone or click “Choose folder…”. The folder stays exactly where it is; FLY8HT never copies or moves it.

2. FLY8HT analyses the project

For a GitHub repo, you’ll briefly see a real progress screen: repository found, cloning, framework detected, dependencies analysed. Nothing here is guessed silently: every step is a real signal (a config file that exists, a lockfile that’s actually committed), never an assumption.

3. Review what it found

Before anything is built, FLY8HT shows you exactly what it detected: the framework, the package manager, the literal build and start commands it’s about to run, and a compatibility verdict. If everything looks right, one click (“Build with FLY8HT”) starts a real build. If FLY8HT genuinely can’t tell how to run something (a monorepo with more than one app, or an unfamiliar setup), you’re taken to a short configuration wizard instead of a guess.

4. Watch it build, then open it

A real build runs (install, build and start) with live logs the whole way. Once it succeeds, your project is genuinely running locally, with a real, clickable URL and a Stop button right there in the header.

What FLY8HT never does

• It never uploads your code anywhere. Everything runs on your own machine.
• It never requires an account for a public repository or a local folder.
• It never silently guesses when it isn’t confident. It asks you instead.