From a schoolhouse evaluator: "Our training network has no internet access at all. Marketing pages say ‘offline capable’ and then the app phones home for fonts or licence checks. What does TaskFlight actually require?"
Nothing. The application is fully client-side and builds to a static export — a folder of HTML, JS and assets — that serves from any internal web server, network share behind a web front end, or approved kiosk image. This is not a degraded mode; the desktop build ships exactly this way and runs from local disk.
Specifics that usually matter to accreditors: fonts are system-stack (no font CDN), there are no analytics or telemetry endpoints, no licence-check callout, and every 3D asset is procedural geometry compiled into the bundle — there are no model files to fetch. The only external links in the product are clearly-marked navigation (this board’s GitHub links, mailto links), which simply fail closed on an enclave with no route out.
Training progress in the demonstration build is per-browser localStorage, so it never needs a server either. If you need progress to land in an LMS inside your boundary, see the SCORM/xAPI thread on this board.
This board is read-only — TaskFlight has no accounts and stores nothing on a server, so replies live on GitHub Discussions, where the conversation is public and moderated. Prefer email? Same address as always; useful questions get added to this board with identifying details removed.