Managed SFTP · FTPS · HTTPS

We move your files.
We never store them.

Not by policy. By architecture.

Enterprise file transfer for storage you control. Your storage credentials stay on your Storage Connector. Every transfer leaves evidence you can verify yourself.

14 days. No credit card. No feature locks.

  • 0 Customer files stored
    on our platform
    No staging disks. No swap.
  • 0 Storage credentials
    held by us
    Your Connector holds them.
  • 2 Independently signed
    audit trails
    Verify with open-source tools.
  • PQC Hybrid post-quantum
    protection
    mTLS on internal connections.
Building file transfer software since 2014 SFTP · FTPS · FTPES · HTTPS, the protocols your partners already use mTLS between every component, with no plaintext hop anywhere Post-quantum cipher suites on every protocol Zero customer files on SFTP.cloud infrastructure

01The problem

Managed file transfer keeps ending up in the news. There is a structural reason.

A conventional file transfer platform has a specific shape:

  • 01

    It sits on the public internet, because your partners have to reach it.

  • 02

    It holds the credentials to your storage, because that is how it fetches your files.

  • 03

    It keeps your files on its own disks, while they are in flight, or for good.

That shape puts some of your organization's most sensitive data in one internet-facing system, right next to the same data from hundreds of other companies.

  • 4+mass breaches in five years
  • 4different vendors
  • 1playbook, run by the same attackers each time

One flaw in one product becomes a breach at every company running it. Including yours.

So we built a different shape.

02How it works

Your storage stays yours. We handle everything in front of it.

See the full architecture →
The architectureStep 1 of 4
SFTP · FTPS · HTTPS OUTBOUND · MUTUALLY AUTHENTICATED Your files are never stored in SFTP.cloud Partners and staff the client they already use SFTP.cloud terminates the protocol · authenticates the user enforces your rules Storage Connector you install it · you hold its keys Your storage S3 · Azure · GCS · MinIO

03Guarantees

Three things we cannot do, even if we wanted to.

  • 01Files

    We cannot read your files.

    They are never written to our storage: not at rest on our disks, not cached, not buffered to a temporary volume under load. They pass between your Connector and your user, and then they are gone.

  • 02Credentials

    We cannot reach your storage.

    We hold no access key, OAuth token, service principal or assumed role. The Connector authenticates to your storage from inside your network, with credentials that never leave it. There is nothing on our side to steal.

  • 03Audit trail

    We cannot rewrite your record.

    Every session writes two audit trails: one on our infrastructure, one on your Connector, signed with a key we never hold. We cannot edit yours, and you cannot edit ours. If they ever disagree, you can prove it without us.

Every system can be attacked. The better question is what an attacker could take from you. With SFTP.cloud: neither your files nor the keys to them.

04Capability

And it does the actual job.

Architecture is why you would trust it. This is why you would use it.

  • Familiar protocols your partners already have.

    SFTP, FTPS, FTPES, and a browser-based HTTPS client for the people on your side who will not install anything.

  • The storage you already own.

    Amazon S3 and S3-compatible, Azure Blob, Google Cloud Storage, MinIO, upstream SFTP servers, and on-premises file storage. Connect several at once.

  • Users, groups, and access rules.

    Provision transfer accounts, scope them to paths, and manage all of it from a web console or the API.

  • A signed audit trail on both sides.

    One on our infrastructure, one on yours, each signed with a key the other party never holds.

  • Encryption ready for what is coming.

    Post-quantum cipher suites across SFTP, FTPS and HTTPS, and mutual TLS between every internal component.

  • Isolation when you need it.

    A dedicated environment adds your own connection allow lists, short usernames without a site suffix, and other service-level settings you control.

05The product

One place to run it. One more way in for your users.

The console

You can see everything, the moment it happens.

Every session, transfer and rejection, in real time and in one place. See which of your users is connected right now and follow any of your files from arrival to event handlers, without digging through log files.

SFTP.cloud storage connector dashboard showing live sessions and transfers
SFTP.cloud WebClient in the browser, sharing a file

HTTPS access

The same storage, through the browser.

Not all of your users have an SFTP client. The WebClient gives them the same virtual file systems, permissions and audit trail over HTTPS, and server-side transfers finish even if they close the browser.

06Pricing

Two plans. Both published. Priced per account, not per gigabyte.

You pay for accounts. Not for storage, since we store nothing, and not for transfer or bandwidth. Your renewal invoice holds no surprises.

Shared

from

$2,400/ year

or $240 a month

Every feature, on a shared environment.

Dedicated

from

$8,400/ year

or $840 a month

Your own isolated environment, allow lists and short usernames.

Verify it yourself, on your own storage.

Fourteen days on a shared environment with your own storage connected. No credit card, and nothing to cancel if it is not for you.

Still in diligence? Read the security architecture or talk to an engineer. We don't outsource, we answer personally.