# Another SFTP server

A very useful feature of SFTP.cloud is that it can be used as a cloud-native secure front-end to **bridge traffic to another (often on-prem) SFTP server, without opening up such SFTP server to the world**.

Easy to do with SFTP.cloud. Just deploy the Storage Connector on or near the SFTP server you want to protect, then create a VFS that points to it. The Storage Connector connects to the SFTP.cloud SaaS only outbound so you can keep all your inbound firewall ports closed and your original SFTP server safe.

Here's an example of how to configure a VFS that points to an SFTP server. Note: even though your auth data is stored encrypted in the Connector's DB, and even though all traffic between Connector and your internal SFTP server is on private LAN, using PKI auth is still the strongly recommended way.

[![image.png](https://kb.syncplify.com/uploads/images/gallery/2026-09/scaled-1680-/8b6image.png)](https://kb.syncplify.com/uploads/images/gallery/2026-09/8b6image.png)

Once you've created the VFS, simply switch to the Users page, and grant access to the newly created VFS for all the transfer users you want to be able to access it.

[![image.png](https://kb.syncplify.com/uploads/images/gallery/2026-09/scaled-1680-/4ccimage.png)](https://kb.syncplify.com/uploads/images/gallery/2026-09/4ccimage.png)

Once that's done, the users you granted access to will be able to point their browser or SFTP client to your SFTP.cloud hostname, sign in, and interact with your now-fully-protected original SFTP server:

[![image.png](https://kb.syncplify.com/uploads/images/gallery/2026-09/scaled-1680-/aKpimage.png)](https://kb.syncplify.com/uploads/images/gallery/2026-09/aKpimage.png)

\[Manual: [general information about storage back-ends](https://docs.sftp.cloud/connector/backends)\]