Managed SFTPGateway for Cloud Storage
Give partners, vendors, and legacy applications standard SFTP, FTPS, and FTP access while files stream directly into your cloud storage. Rilavek is a cost-effective AWS Transfer Family alternative for teams that want a managed SFTP gateway, not more infrastructure.
Cloud SFTP in three steps
The sender experience stays familiar. The infrastructure behind it becomes your cloud storage.
Create a Pipe and bucket destination
Connect AWS S3 or any S3-compatible storage in the dashboard. We give you a Pipe and a managed gateway endpoint.
Issue partner-specific Sender credentials
Each vendor, app, or business unit gets isolated credentials. Revoke one party without rotating everybody else.
Files land directly in your bucket
Partners keep using SFTP, FTPS, or FTP. Rilavek streams uploads straight into your storage and can trigger webhooks immediately.
Zero Infrastructure
Forget patching OS updates or managing instances. We provide a fully managed, auto-scaling SFTP service that just works.
Identity Isolation
Stop sharing passwords. Assign unique 'Sender' identities to every partner. Revoke access instantly without rotating keys for everyone else.
Event Driven
Don't poll. React. File Pipes trigger webhooks or cloud functions as soon as an upload completes.
The "Missing Link" for SFTP to S3
Modern teams store data in S3. But the rest of the world (Banks, Healthcare, Agencies) still runs on SFTP. Setting up a Cloud SFTP Server is usually complex and expensive.
Rilavek bridges this gap. We accept the file via standard protocols and stream it directly to your private S3 buckets. Your partners get the interface they need; you get the SFTP Gateway you want.
✓ Connection Established (SFTP)
✓ Auth User: 'vendor_client'
➜ Streaming to 's3://finance-bucket/invoices/'
✓ Upload Complete (250ms)
How this compares to the usual options
Most teams either overpay for a managed gateway or underinvest in a server they have to babysit. This is the middle path.
| Capability | Rilavek | AWS Transfer Family | Self-hosted SFTP |
|---|---|---|---|
| Bring your own bucket | Yes | Yes | Yes |
| No servers to patch | Yes | Yes | No |
| Per-partner identity isolation | Yes | Yes | Depends on your setup |
| Webhook triggers on upload | Built in | Needs extra wiring | Custom work |
| Works across S3-compatible providers | Yes | AWS-centric | Possible, more ops |
| Infrastructure ownership | Managed | Managed | You own it |
What partner-facing file transfer needs in production
The gateway is only useful if onboarding, auditing, and security stay manageable as your partner count grows.
Partner-by-partner access control
Create unique Sender identities for vendors, business units, or applications. Disable one account without touching the rest.
Protocol bridge to cloud storage
Accept SFTP, FTPS, or FTP on the front door and translate it into object storage writes on the back end.
Audit-friendly transfer visibility
Track who uploaded what, when it arrived, and whether each destination completed successfully.
Upload-only gateway posture
Keep the gateway focused on ingestion instead of turning it into a broad file-serving surface area.
Event-driven downstream workflows
Trigger webhooks, cloud functions, or ETL jobs as soon as transfers complete instead of polling buckets.
Multi-cloud destination flexibility
Route into AWS S3, Backblaze B2, Cloudflare R2, MinIO, and other S3-compatible destinations without changing the sender.
Common questions
Can partners keep using their existing SFTP client?
Yes. Cyberduck, WinSCP, FileZilla, legacy ERP systems, and automated jobs keep using standard SFTP, FTPS, or FTP. The change is on the gateway side, not the sender workflow.
Is this upload-only or a full shared file server?
It is designed as an ingestion gateway first. That keeps the security model simpler and avoids turning the endpoint into a general-purpose file distribution layer.
Can I isolate vendors from each other?
Yes. Use unique Sender identities per partner or per group. That gives you cleaner audit trails and lets you revoke a single party without broad credential rotation.
What storage backends are supported?
Any S3-compatible destination works well, including AWS S3, Cloudflare R2, Backblaze B2, Wasabi, and MinIO. Exact destination configuration can vary slightly by provider.
Can this trigger downstream processing when files arrive?
Yes. Pair the gateway with webhooks to notify your API, ETL flow, or automation system as soon as the transfer completes.
Give partners SFTP access without owning the gateway.
Give partners a familiar protocol, keep the files in your own cloud storage, and let the gateway stay managed.
Free plan includes 10GB of transfer. No credit card required.