What foundry-ops connects to

foundry-ops has no accounts, analytics or telemetry of its own, and Knownframe receives nothing from it. Everything it does happens on your Proxmox host and in the container it creates. While it installs or updates Foundry, it and the community-scripts engine it builds on connect to the places below.

The installer runs as root in your host’s shell. It creates the container, and sets the container’s notes, tags and login banner to point to foundry-ops. If the host doesn’t have the Debian 13 container template yet, the engine downloads it from Proxmox’s template server.

Foundry VTT is downloaded only from the Timed URL you paste in, or the FOUNDRY_SOURCE you set, straight into the container. foundry-ops is written never to save the URL to disk or to logs: it goes to the download on its standard input, not on the command line. The zip is deleted once Foundry is unpacked. Nothing is downloaded from Foundry on your behalf otherwise.

• Debian. The container’s operating system is updated, and unzip and jq are installed, from its Debian package sources.
• Node.js. Node.js comes from NodeSource’s package repository, in the version Foundry needs.
• A connection check. Before installing, the engine checks the container can reach the internet, for example by pinging a public DNS server or connecting to deb.debian.org or github.com.

The installer, the community-scripts engine (at a pinned version) and the foundry-ops install script are fetched from GitHub each time you install or run update.

The first time a community-scripts installer runs on a host, the engine asks whether to send anonymous diagnostics about installs to the community-scripts project. If you agree, each install reports details such as the CPU, RAM and disk size, the operating system and Proxmox VE versions, the app installed, how long it took, and whether it succeeded, with the error if it failed. Your answer is saved in /usr/local/community-scripts/diagnostics on the host; set DIAGNOSTICS=no there to stop. This is the engine’s feature, not foundry-ops’s, and the data goes to community-scripts, not to Knownframe.

Once it’s running, Foundry VTT connects to whatever it needs under its own license and terms, such as checking your license key. foundry-ops doesn’t change that, apart from turning UPnP off so Foundry doesn’t open ports on your router.