SFTP to GCS
Put SFTP in front of Google Cloud Storage
Google Cloud Storage speaks its own API, not SFTP. Firepipe bridges the two. Connect a GCS bucket you already own, create separate logins for people and systems, and let them use ordinary SFTP clients while GCS remains your storage layer.
Your GCS bucket · ordinary SFTP clients · managed gateway
The short version
Firepipe presents an SFTP endpoint backed by your Google Cloud Storage bucket. It handles SFTP authentication and file operations, then streams file contents to or from GCS. There is no second storage system to keep in sync, and Firepipe keeps no lasting copy of file contents.
How it works
Authorize one bucket, create logins, then point SFTP clients at Firepipe.
Connect your GCS bucket
Provide a scoped service-account key limited to the bucket. Firepipe stores the key encrypted using an AES-256-GCM envelope under a KMS-managed key, decryptable only by the gateway. You can revoke the credential in Google Cloud.
Create separate logins
Use passwords or SSH public keys. Each credential can be jailed to a path prefix so the account cannot list or read outside its assigned area.
Let clients transfer over SFTP
Standard SFTP clients connect to Firepipe. Their uploads, downloads, listings, and deletes are translated to operations against your GCS bucket.
Why use Firepipe with GCS
GCS stays the backend
Keep file contents in the Google Cloud project you already operate. Firepipe adds the SFTP interface, and removing the scoped service-account credential removes its bucket access.
Users and transfers are attributable
Issue one credential per person or system and set a path prefix for each. Audit logs record the user, operation, path, byte count, source IP, timestamp, and status, and can be exported as CSV.
Simple transfer metering
Firepipe charges for metered transfer without adding its own per-operation or per-listing fees. Google Cloud bills the storage and cloud usage in your project separately.
Simple, metered pricing
Metered transfer. No per-operation or per-listing fees from Firepipe.
Early-access pricing, these starting tiers may change. Your own cloud usage is billed by your provider, directly to you.
Frequently asked questions
What does "SFTP to GCS" mean?
Google Cloud Storage does not expose an SFTP server. Firepipe provides that SFTP endpoint and translates SFTP file operations into GCS operations, so existing SFTP clients can work with your bucket.
Can I use my existing Google Cloud Storage bucket?
Yes. The bucket remains in your Google Cloud project. Firepipe does not require you to move those files into Firepipe-managed storage.
Does Firepipe support SSH keys and per-user access?
Yes. Give each person or system a password or SSH-key credential and jail it to a path prefix. Revoking that credential also ends any live session.
How does Firepipe access my GCS bucket?
You provide a scoped service-account key limited to the bucket. Firepipe stores it encrypted using an AES-256-GCM envelope under a KMS-managed key, decryptable only by the gateway, and you can revoke it from Google Cloud.
What does it cost?
The free tier includes 5 GB of transfer per month and 5 users. Paid plans start at $19/mo and meter transfer, with no Firepipe per-operation or per-listing fees. Google Cloud bills your own storage and egress separately. Firepipe pricing is early-access and may change.
Add SFTP to Google Cloud Storage
Connect a GCS bucket, define user access, and give SFTP clients the Firepipe hostname.
Start free