Rilavek

Rilavek is a managed file transfer service that sits between the way files arrive and where you actually want them to live. It accepts uploads over both legacy and modern protocols, then streams each file straight into cloud object storage without ever writing it to a local disk first. The company describes it as a universal storage bridge, and that's a fair summary. You point a sender at Rilavek, tell it which bucket to feed, and files land in your own storage without a staging server sitting in the middle. The service handles the protocol handshake, the authentication, and the streaming itself, and simply hands each file off to storage you already control.

The problem it goes after shows up constantly in real infrastructure. A partner, a camera, or an industrial device only speaks FTP or SFTP, but your storage lives in S3, Cloudflare R2, or Backblaze. The usual fix is a stack of cron scripts plus a staging box that holds files temporarily, which becomes one more thing to patch, monitor, and clean up when a disk fills or a job silently fails. Rilavek removes the staging step entirely, so files move from the sender to the bucket in a single hop. That also means there's no half-finished pile of temp files to reconcile when something goes wrong midway through a transfer.

Under the hood it works as a real-time pass-through. Uploads come in over FTP, FTPS, SFTP, HTTPS, or TUS, and the bytes get streamed in memory directly to the destination rather than parked on a server first. The company calls this a zero-knowledge, zero-disk design, meaning large transfers don't have to fill a buffer and finished files don't sit around waiting to be swept off local storage. TUS matters here because it's a resumable upload protocol, so a dropped connection on a huge file can pick up where it left off instead of starting over. Because nothing touches local disk, one incoming upload can also fan out to several destinations at once. That fan-out runs on the same stream, so a file bound for two buckets doesn't get uploaded twice from the sender's side.

On the storage side it targets S3-compatible services broadly, so AWS S3, Cloudflare R2, Backblaze B2, Wasabi, and self-hosted MinIO all work, alongside Google Cloud Storage and providers like DigitalOcean Spaces, Linode, IDrive, Oracle, and Alibaba. Consumer file services such as Drive, Dropbox, Box, and OneDrive are listed as coming soon. Events during a transfer can trigger webhooks or email notifications, and there are prebuilt connectors for Zapier and n8n, so a completed upload can kick off the rest of a workflow without writing custom glue code. That turns Rilavek into a trigger point in a pipeline rather than a dead-end drop box. Sender identities and pipes are configured once, then reused across as many uploads as you need, which keeps the setup light even for teams juggling several partners at the same time.

It's aimed at developers, ops teams, and anyone maintaining data pipelines who is tired of babysitting FTP-to-cloud plumbing. Typical jobs include standing up a managed SFTP gateway for vendor exchange, retiring a folder full of migration scripts, handling camera-to-cloud delivery from the field, or feeding legacy file drops into an AI ingestion pipeline. Multi-cloud replication and simple disaster-recovery copies fall out of the fan-out feature naturally, since the same upload can be mirrored into a second region or a second provider. Edge devices in industrial settings that can only emit files over old protocols fit the same pattern. Because the transfer never leaves memory, the same setup works whether the payload is a few kilobytes from a sensor or a multi-gigabyte video file from a location shoot.

What sets it apart is the combination of protocol breadth and the no-buffer approach. Plenty of services move files on a schedule, and plenty of gateways speak SFTP, but Rilavek's pitch is that it does the translation live, keeps nothing on disk, and points at almost any S3-compatible backend you already use. Every plan includes unlimited pipes, sender identities, and destinations, so the constraints are about how much data you move rather than how many connections or endpoints you configure. For a small team that would rather not run and secure its own SFTP server, that bundle of translation, streaming, and routing is the whole appeal.

Access is freemium. A free tier covers 10GB of monthly transfer with community support, the Starter plan runs ten dollars a month for 100GB with standard email support, and the Pro plan is thirty dollars a month for 1TB with priority email support. The tiers scale on transfer volume rather than locking features behind higher prices, which makes it easy to try a single pipe on the free plan and grow into a paid tier as a feed starts moving more data each month.