Why Compute supports SFTP—not FTPS

FTPS vs. SFTP at a glance

Same key, same port – Your SSH key doubles for file transfers; no extra credentials.
No additional firewall rules – Everything slips through port 22, even behind strict networks.
End‑to‑end encryption – Data and commands are encrypted by default.

**Good to know: **FTPS requires opening a range of data ports, which conflicts with Compute’s default security posture.

Spin up a quick web server on port 8888 inside your instance:

python3 -m http.server 8888 --bind 0.0.0.0

Then open your instance URL:

https://<instance-id>-8888.tenants.hivecompute.ai

Old FTPS command	SFTP replacement
`curl --ftp-ssl -T file.zip ftp://user@host/`	`sftp user@host:~/upload <<< $'put file.zip'`
`lftp -u user,pass ftps://host`	`sftp user@host` then `put/get`

For automated workflows, tools like rsync or scp provide shell‑friendly, encrypted transfers.

Still unsure? Drop into Discord or open the chat widget—our team’s happy to help you switch over.

⌘I