SFTP.cloud vs SFTP To Go
Both run SFTP for you. Only one leaves your files with you.
Both give your partners SFTP, FTPS and a web portal without a server for you to run. The difference is where the files end up. SFTP To Go keeps them in storage it runs and controls, so its security becomes your security, and your plan caps how much you can keep. SFTP.cloud stores nothing: every file streams straight into storage you already own and protect, with no cap.
SFTP To Go details checked against its public website and documentation on 15 October 2026.
Who holds your files
SFTP To Go, in its storage on AWS. Your own S3 bucket only on Enterprise, in beta
You do. We never store them
How much you can keep
100 GiB on Launch. Sustained overage means an upgrade
As much as your storage holds
Audit log retention
14 days on Launch, 30 on Scale
A year by default, on your Connector
01Files and credentials
Where your files live, and who can reach them.
“Storage included” sounds like more. What it means is that a vendor keeps a copy of every file your partners send, decides how much you may keep, and issues the keys your applications use to reach it. The large file-transfer breaches of recent years all took files that were sitting on the transfer platform.
SFTP To Go
Your files, on its storage.
Every file your partners send is stored by SFTP To Go on Amazon Web Services, encrypted at rest with AES-256 on the server side. Protecting it is up to SFTP To Go.
- Storage is capped by plan: 100 GiB on Launch, 500 GiB on Scale, with monthly bandwidth capped at 200 GiB and 500 GiB
- Limits are soft, but sustained overage leads to an upgrade
- Keeping files in your own S3 bucket requires Enterprise, and the feature is in beta
- Your applications reach the files with an IAM access key and secret that SFTP To Go issues
SFTP.cloud
Your storage. Nothing else.
Files stream through a Storage Connector you run next to your storage. They are never written to a disk we own.
- We hold no access key, secret key, OAuth refresh token or service principal, and you never grant us a cross-account role
- Your Connector authenticates to your storage with credentials you created and stored where you chose. Rotate them without telling us
- The Connector only dials out, so there is no inbound rule to your network
- Optional encryption at rest with a key that lives on your Connector and is never sent to us
At Amazon S3 list price, 100 GiB of storage costs about $2.50 a month. What “included” really adds is someone else holding your files.
02Encryption in transit
Traffic captured today stays unreadable tomorrow.
An attacker can record encrypted transfers now and keep them until a quantum computer can break classical key exchange. Post-quantum key exchange closes that window for files that must stay confidential for years.
| Connection | SFTP.cloud key exchange |
|---|---|
| SFTP | Hybrid post-quantum mlkem768x25519-sha256 |
| FTPS and FTPES | Post-quantum cipher suites |
| HTTPS web client | Post-quantum cipher suites |
SFTP To Go states that its connections use SSH and TLS 1.2 or later. Its public documentation does not list the key exchange algorithms it negotiates.
Mutual TLS
Every component proves who it is, on every connection.
Encrypting the connection from your partner is only the outside layer. Inside SFTP.cloud, the Head, the control plane and your Connector authenticate each other with certificates and refuse any peer that can't. No component is trusted because of where it sits on a network.
- 01A foothold is not a way in.
An attacker who reaches the network between our components still can't pose as one of them without its certificate.
- 02No plaintext hop anywhere.
Every link between components is encrypted, not only the connection at the edge.
- 03Your Connector answers only to us.
It accepts instructions only from a control plane that proves its identity, so a forged server can't direct it at your storage.
Standard protocols, standard clients. Your partners connect with the software they already use. Nothing proprietary, nothing to install.
03Audit trail
A record you can check without taking our word for it.
Both products keep an audit trail. The difference is how long it lasts, who holds it, and whether you can prove it is intact without relying on that party.
SFTP To Go
Kept for 14 or 30 days.
SFTP To Go keeps audit data for a retention period set by your plan.
- Launch: 14 days of audit log retention
- Scale: 30 days
- Enterprise: a custom period
SFTP.cloud
Two signed records, held by two parties.
Your Connector and our Head each keep their own record of every session, on machines owned by different parties. Neither side can quietly bring the other's record into line with its own.
- Your Connector records every file operation, allowed and denied, signed with a key that never leaves it
- Every line is chained to the one before it, so a changed, removed or reordered line breaks the chain
- Every five minutes a signed commitment leaves the machine and is countersigned on arrival. From then on, not even the machine's owner can rewrite that period undetected
- Download the evidence file and check it with logverify, an open-source verifier that needs nothing from us
A compliance review often asks about last year. Two signed records let you answer it yourself.
04Shield
Attackers are turned away before the handshake.
Shield watches every source address for failed sign-ins and remembers how each one behaved. A fast brute-force attempt is caught quickly, and so is a botnet that spreads its guesses thin so that no single address stands out.
Once an address is banned, its connections are refused at TCP accept, before any SSH or TLS key exchange begins. Turning away an attack costs almost nothing, so your legitimate users keep signing in while it is underway.
Shield is deterministic, so false positives are rare, and it is on for every SFTP.cloud endpoint from the first day.
A real attack
6 September 2026, less than two hours after SFTP.cloud opened for early access.
05Side by side
Plans, storage and protocols, line by line.
Checked on 15 October 2026
| SFTP To Go | SFTP.cloud | |
|---|---|---|
| Plans and price | ||
| Entry plan | Launch: $150 a month, or $1,800 a year | Shared: $240 a month, or $2,400 a year |
| Next plan | Scale: $325 a month, or $3,900 a year | Dedicated: $840 a month, or $8,400 a year, on your own VM |
| Accounts on the entry plan | 20 credentials | 15 transfer accounts and 3 Storage Connectors |
| Storage and transfer limits | Launch: 100 GiB storage, 200 GiB monthly bandwidth. Scale: 500 GiB of each. Sustained overage leads to an upgrade | None. Files go to your storage, which you size and pay for directly. No per-gigabyte or transfer charge from us |
| Free trial | 7 days | 14 days, no credit card |
| Storage | ||
| Who holds your files | SFTP To Go, in its storage on AWS | You. Never written to a disk we own |
| Your own cloud storage | Amazon S3 only, on Enterprise, in beta | Amazon S3, Azure Blob, Google Cloud Storage and S3-compatible stores, on every plan |
| Encryption at rest | AES-256, server side | Optional, with a key that lives on your Connector and is never sent to us |
| Audit trail | ||
| Who holds the record | SFTP To Go | Two signed records: one on your Connector, one on our Head |
| Retention | 14 days on Launch, 30 days on Scale, custom on Enterprise | A year by default on your Connector, configurable. Signed commitments kept at least 400 days, and you keep your own copy |
| Protocols | ||
| Protocols | SFTP, FTPS, Amazon S3 API and an HTTPS web portal | SFTP, FTPS, FTPES and an HTTPS web client |
| Post-quantum key exchange | Not stated in its public documentation | SFTP, FTPS, FTPES and HTTPS |
SFTP To Go information comes from the SFTP To Go website and public documentation as of the date above and may have changed since. Prices exclude taxes. SFTP To Go is a trademark of its owner. SFTP.cloud is not affiliated with or endorsed by SFTP To Go.
06Choosing
When SFTP To Go is the better fit.
The two products overlap, but they are not built for the same buyer. In these cases, SFTP To Go is the more direct choice.
- 01
You have no storage and don’t want any.
SFTP.cloud needs a bucket or file share of yours to write to. If you have none, and you are comfortable with a vendor holding your files, SFTP To Go is one less thing to set up.
- 02
You want S3 API access to the same files.
SFTP To Go lets your applications reach the files your partners upload through the Amazon S3 API, alongside SFTP and FTPS.
- 03
Your volume fits a small plan.
Launch is $1,800 a year for 20 credentials and 100 GiB of storage, below SFTP.cloud Shared at $2,400 a year. If your partners send a few files a month and none of them are sensitive, the lower price may decide it.
If your files must stay in storage you control, and no one else may hold the keys to it, that is what SFTP.cloud is built for.
07FAQ
SFTP.cloud and SFTP To Go, common questions.
Is SFTP.cloud an alternative to SFTP To Go?
For SFTP, FTPS and web access, yes. The difference is who holds your files: SFTP To Go keeps them in its own storage, capped by plan, while SFTP.cloud streams every file into storage you already own and never keeps a copy.
SFTP To Go includes storage. Isn’t that more for the money?
The included storage is 100 GiB on Launch, which costs about $2.50 a month on Amazon S3 at list price. What it adds is a vendor holding every file your partners send, a cap on how much you can keep, and a second place to secure and audit. With SFTP.cloud, files land directly in storage you already pay for and protect.
Can SFTP To Go use my own storage?
Bring Your Own Bucket, which lets SFTP To Go endpoints reach data in your own Amazon S3 bucket, is listed as a beta feature of the Enterprise plan. On Launch and Scale, files are stored in SFTP To Go managed storage.
Does SFTP.cloud store my files or my storage credentials?
No. Files stream through the Storage Connector you run next to your storage and are never written to a disk we own. The Connector authenticates to your storage with credentials that never leave it.
How long is the audit log kept?
SFTP To Go lists 14 days of audit log retention on Launch, 30 days on Scale and a custom period on Enterprise. SFTP.cloud keeps a signed record on your Connector for a year by default, configurable, and you keep your own copy.
How can I prove the SFTP.cloud audit trail was not altered?
Your Connector and our Head each keep a signed record of every session, and signed commitments are countersigned when they leave the machine. Download the evidence file and check it with logverify, an open-source verifier that needs nothing from us.
How do the prices compare?
SFTP To Go Launch is listed at $150 a month or $1,800 a year, with 20 credentials, 100 GiB of storage and 200 GiB of monthly bandwidth. SFTP.cloud Shared is $240 a month or $2,400 a year for 15 transfer accounts and 3 Storage Connectors, with no per-gigabyte or transfer charge. Your storage provider bills your storage as usual.
Will my partners need new software?
No. SFTP.cloud uses standard SFTP, FTPS and FTPES, so your partners connect with the clients they already use, or with the browser-based web client.
Keep your files. Keep your keys.
Connect your own storage, invite a partner and send your first file. Fourteen days, no credit card, and nothing to cancel if it is not for you.
Want the details first? Read about security or how it works.