Download the Storage Connector
The Storage Connector is the only piece of SFTP.cloud you install. It runs next to your storage, inside your own network, and it is what keeps your files where they already are. It needs to be enrolled with your account in the SFTP.cloud Portal after installation.
Install it and enroll it once, it self-updates afterwards
Windows, Linux, macOS and FreeBSD builds are all below.
Download for macOS
We cannot tell from your browser which processor this Mac has, so here are both.
If you are not sure, open the Apple menu, choose About This Mac, and look at the chip.
The Storage Connector runs on a server
It needs to sit next to your storage, on a machine that stays on. There is nothing useful to install on a phone.
See all downloads so you can send the right one to yourself, or start with the installation guides.
Every build
All downloads
The installers below always install the Storage Connector’s latest version.
You only need to install it and enroll it once: the Storage Connector self-updates afterwards.
| Platform | Architecture | Installer | Size |
|---|---|---|---|
| Windows | x86-64 | sc-setup-windows-amd64.zip | 11.6 MB |
| Windows, console installer | x86-64 | sc-setup-cli-windows-amd64.zip | 7.7 MB |
| Linux | x86-64 | sc-setup-linux-amd64.tar.gz | 7.3 MB |
| Linux | ARM64 | sc-setup-linux-arm64.tar.gz | 6.7 MB |
| macOS | Apple Silicon | sc-setup-darwin-arm64.tar.gz | 6.6 MB |
| macOS | Intel | sc-setup-darwin-amd64.tar.gz | 7.1 MB |
| FreeBSD | x86-64 | sc-setup-freebsd-amd64.tar.gz | 7.2 MB |
Or run it in a container
docker pull syncplify/sc-connBuilt for linux/amd64 and linux/arm64. Works with Docker, Podman, or anything else that runs OCI images.
Give it a persistent /data volume. That is where the Connector keeps its identity, its database and your at-rest encryption keys. Without it, the container comes back as a stranger every time it restarts and has to be enrolled again. And if you are using your own encryption keys, we never have a copy of them, by design, so there is nowhere else to get them back from.
Container installation guide →Verification
Verify what you downloaded
Three layers, and you can use all of them.
The checksum
Every file above has a published SHA-256. Checking it takes about ten seconds and confirms that what reached your machine is what left ours.
Windows
certutil -hashfile sc-setup-windows-amd64.zip SHA256Linux, FreeBSD
sha256sum sc-setup-linux-amd64.tar.gzmacOS
shasum -a 256 sc-setup-darwin-arm64.tar.gzCompare the result against checksums.txt. If it does not match, do not install it, and please tell us.
The code signature, on Windows
The Windows installers are code-signed by Syncplify, Inc. Right-click the file, open Properties, and look at the Digital Signatures tab. Or from PowerShell:
Get-AuthenticodeSignature .\sc-setup-windows-amd64.exeA status of Valid and a signer of Syncplify, Inc. is what you want to see.
The installer checks itself
On every platform, the installer carries an Ed25519 signature over its own payload and verifies it before doing anything. If the contents have been altered, it refuses to run and tells you why. You do not have to remember to check this one.
Our signing key is published here, so you can check it yourself rather than trusting the installer to check itself:
Before you click
If your operating system warns you
Operating systems are cautious about software they have not seen before.
Here is what you may run into and what it means.
If your operating system
warns you
Operating systems are cautious about software they have not seen before.
Here is what you may run into and what it means.
-
Windows.
Our installers are code-signed by Syncplify, Inc. If SmartScreen still says the file is not commonly downloaded, that is a reputation signal rather than a security finding: it reflects how many people have run this exact version so far, and it settles as downloads accumulate. Check the Digital Signatures tab and the checksum, and you have better evidence than SmartScreen has.
-
macOS.
The macOS builds are not yet notarized by Apple, so Gatekeeper will tell you it cannot check the software for malicious software. Notarization is coming when SFTP.cloud moves from early access to general availability. Until then, verify the checksum above, and see the macOS installation guide for how to proceed.
-
Linux and FreeBSD.
No operating system level signature check applies. Verify the checksum, the installer will also verify itself independently.
Guides
Installing it
Installation takes a few minutes. You will need your enrolment details from the customer portal, which is where the Connector gets its identity.
Requirements
What the Connector needs
-
Outbound HTTPS to portal.sftp.cloud, and outbound port 7600 to connect to the Protocol Head. That is the whole network requirement. No inbound rule, no published endpoint, no inbound port to open.
-
A machine that stays on, close to your storage. A small virtual machine or a container is plenty.
-
Access to your storage, using credentials you create and hold. They never leave your network.
| Supported systems | |
|---|---|
| Windows | Windows 10 or later, Windows Server 2016 or later |
| Linux | Kernel 3.2 or later |
| macOS | macOS 12 Monterey or later |
| FreeBSD | FreeBSD 13 or later |
| Processors | x86-64, or ARM64 (ARMv8.0 or later) on Linux and macOS |
Or run it as a container. The image is built for linux/amd64 and linux/arm64 and runs as an unprivileged user.
New to SFTP.cloud?
Fourteen days on a shared environment, with your own storage connected. No credit card, and nothing to cancel if you decide it is not for you.
SFTP.cloud gives your partners and users managed SFTP, FTPS, FTPES and HTTPS access to storage you already own. Your files stay in your own storage, we never hold the credentials to reach them, and the Storage Connector above is the piece that makes that work.
No credit card. No feature locks.