SFTP / FTPS SERVER IN. GCS OUT. NO SCRIPTS.
A hosted SFTP server that delivers uploads into Google Cloud Storage
DocEvent hosts an SFTP, SCP and FTPS server: senders upload to it with their own login and every completed upload is delivered into your Google Cloud Storage bucket. Hosted SFTP-to-GCS ingestion with a service-account key on the bucket side, retries and a full audit trail.
From
SFTP / FTPS Server
To
GCS
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Filespull
Servers & protocols
SFTP / FTPS Serverhosted · you push
FTP Pull
SFTP Pull
HTTP Upload
Email
Apps & trading partners
SharePointpull
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
Cloud storage
Amazon S3s3-compatible
GCSpush
Azure Blobpush
Servers & protocols
FTP / FTPS
SFTP
Webhook
Email
Apps & trading partners
SharePoint
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.
How SFTP / FTPS Server to GCS routing works
Source
SFTP / FTPS Server
DocEvent hosts an SFTP, SCP and FTPS server for you. Customers, partners and your own systems upload to it with their own login, and every completed upload enters the channel.
DocEvent Channel
routes · retries · logs
Destination
Google Cloud Storage
Files are delivered into your Google Cloud Storage bucket.
1
File arrives via SFTP / FTPS Server
A hosted upload server, not a poll of yours: SFTP and SCP on port 22, explicit (AUTH TLS, port 21) and implicit (port 990) FTPS - cleartext FTP is refused. Usernames, passwords and SSH keys are managed in the console, with a per-service IP firewall and a browser uploader for people without a client. The login is upload-only: a file leaves the server the moment its upload completes, so nothing sits on it and there is nothing to poll.
2
Channel routes it
DocEvent's channel server matches the incoming file to your configured route, queues it for delivery, and ensures no file is ever lost — even during downstream outages.
3
Delivered to GCS
Delivery into a Google Cloud Storage bucket, authenticated with a service-account key. Configurable folder (prefix) inside the bucket, and a built-in connection test that verifies the bucket, credentials and permissions before the first file flows. No Pub/Sub, no Storage Transfer Service, no scripts - each routed file is simply written into your bucket.
Common use cases
Real workflows that teams automate with a SFTP / FTPS Server → GCS channel.
- Receive partner deliveries over SFTP into a GCS bucket with no server to run
- Feed BigQuery or Dataflow pipelines from systems that only speak SFTP or FTPS
- Replace a self-managed SFTP VM in front of Google Cloud Storage
- Per-sender logins, an IP firewall and a full audit trail
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the SFTP / FTPS Server or GCS side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
SFTP / FTPS Server
A hosted upload server, not a poll of yours: SFTP and SCP on port 22, explicit (AUTH TLS, port 21) and implicit (port 990) FTPS - cleartext FTP is refused. Usernames, passwords and SSH keys are managed in the console, with a per-service IP firewall and a browser uploader for people without a client. The login is upload-only: a file leaves the server the moment its upload completes, so nothing sits on it and there is nothing to poll.
DocEvent hosts an SFTP, SCP and FTPS server for you. Customers, partners and your own systems upload to it with their own login, and every completed upload enters the channel.Destination:
Google Cloud Storage
Delivery into a Google Cloud Storage bucket, authenticated with a service-account key. Configurable folder (prefix) inside the bucket, and a built-in connection test that verifies the bucket, credentials and permissions before the first file flows. No Pub/Sub, no Storage Transfer Service, no scripts - each routed file is simply written into your bucket.
Files are delivered into your Google Cloud Storage bucket.Automatic retries with exponential back-off
Full end-to-end audit log for every file
Zero-code setup via the DocEvent UI
Reliable delivery even during downstream outages
Related channel integrations
Other destinations from SFTP / FTPS Server
- SFTP / FTPS Server → Amazon S3
- SFTP / FTPS Server → Azure Blob
- SFTP / FTPS Server → FTP
- SFTP / FTPS Server → SFTP
- SFTP / FTPS Server → HTTP Webhook
- SFTP / FTPS Server → SES Email
- SFTP / FTPS Server → AS2
- SFTP / FTPS Server → SharePoint
- SFTP / FTPS Server → Filerouter (on-premise)
- SFTP / FTPS Server → DocEvent Agent (on-prem)