SFTP and FTP for Google Cloud Storage

Google Cloud has no managed SFTP service. DocEvent gives your partners an SFTP, FTPS, FTP or SCP endpoint that reads and writes directly into your own GCS bucket — without running a VM to do it.
SFTPFTPSFTPSCP
Client
Partner or app
DocEvent
Simple FTP Service
GCS
Your bucket
Files stream straight through to your own Google Cloud Storage bucket — nothing is stored on our servers.

How it works

1
Connect your GCS bucket
Create a service account with access to the bucket, download its JSON key and paste it into DocEvent. Grant it Storage Object Admin on one bucket and the endpoint can reach nothing else.
2
Create a user for each partner
Add an SFTP/FTPS/FTP user per partner or system, with a password or an SSH key and its own home directory. Lock it down with per-service IP allow and deny rules if you want it pinned to known addresses.
3
Hand over the hostname
Give them the DocEvent hostname and credentials. Files land in your bucket as they are uploaded, and every connection and transfer is recorded in the audit log.Prefer your own domain? Point a CNAME at the endpoint and partners connect to something like sftp.yourcompany.com instead.

Built for Google Cloud Storage

The gap Google leaves

There is no first-party managed SFTP on Google Cloud, so the usual answer is a Compute Engine VM running sshd that you patch, monitor and scale yourself. This replaces it with an endpoint you configure in minutes.

Service-account scoped

Access is a service-account key you control and can rotate or revoke in the Google console at any time. Scope it to a single bucket and the endpoint can never see the rest of the project.

Your bucket, your lifecycle

Object versioning, retention policies, customer-managed encryption keys and lifecycle rules into Nearline, Coldline and Archive all keep working. Files are never stored on our servers.

Common questions

You focus on integration,
we'll focus on delivery.

Get started for free