Connect Legacy FTP HardwareDirectly to S3 Data Lakes
IoT devices, IP cameras, PLCs, and legacy manufacturing systems only speak FTP. Rilavek acts as a virtual FTP server that routes every upload directly into modern cloud storage — without touching the hardware.
Migrate legacy hardware to the cloud in three steps
Point the Hardware at Rilavek
Change the FTP host in your device's network settings to ftp.rilavek.com. The device thinks it's talking to a local FTP server.
Configure Your Destination
In the Rilavek dashboard, connect your S3 bucket, GCS, Azure Blob, or Snowflake. Use Smart Paths to organize files by device, date, or location.
Stream Without Code
Every file the device uploads is routed in real time to your cloud storage. No middleware, no local disk writes, no custom scripts to maintain.
Migrate at your own pace
"Big Bang" migrations are risky. Swapping out firmware or replacing hardware fleet-wide to support modern APIs can take months or years. Meanwhile, the data from those devices still needs to go somewhere useful.
Use Rilavek as a Legacy FTP Bridge. Your existing devices keep uploading exactly as they do today. On the Rilavek side, that data lands in your S3 Data Lake, ready for analytics pipelines, AI models, or downstream ETL — with zero changes to the hardware.
The Big Bang Migration Trap
Replacing 200 factory PLCs to update their network configuration is a multi-month project with real production risk. Rilavek acts as an abstraction layer — the devices never need to change. You cut over the cloud side when you are ready, at your own pace.
Sender Groups for Fleet Management
Onboarding 100 cameras or PLCs individually is painful. Sender Groups let you create a shared credential profile and assign it to an entire device fleet at once. Add or remove devices from the group without touching each device's config.
Your device thinks it's saving to a local FTP server. We route it instantly to S3 or any cloud storage.
Route industrial sensor data directly to Snowflake or Databricks via S3 — no glue code.
Stop writing and maintaining Python sync scripts. The routing logic lives in the Pipe config.
Files land in your cloud destination the moment the device finishes uploading. No batch windows.
Built for the industrial and IoT use case
These are the requirements that come up when managing large fleets of legacy devices.
FTP, FTPS & SFTP
Every major transmission protocol is supported. Works with whatever firmware your device ships with.
Real-time Streaming
No local buffer. Files are streamed as they arrive directly into your cloud storage with zero on-disk intermediate writes.
Fleet-scale Sender Groups
Manage hundreds of devices under one credential profile. Onboard entire manufacturing lines in minutes.
Smart Path Formatting
Auto-organize files into /year/month/day/device-id/ folder structures without coding. Configure once in the Pipe.
Per-Device Identity
Each device gets a unique Sender credential. Compromise or decommission one device without affecting the rest of the fleet.
Any S3-Compatible Destination
AWS S3, GCS, Azure Blob, Snowflake, Databricks. Route industrial data to wherever your analytics stack expects it.
Common questions
Do I need to update my device firmware?
No. If your device supports FTP, FTPS, or SFTP, you only change the host and credentials in the network settings. Rilavek handles the rest on the cloud side.
Can this work behind a NAT or corporate firewall?
Yes. Rilavek supports FTP passive mode, which is the standard configuration for devices behind firewalls and NAT. SFTP and FTPS also work without special firewall rules.
How do I manage 200 PLCs without configuring each one individually?
Use Sender Groups. Create a group with a shared credential profile and assign all 200 devices to it. Each device uses the same login but is tracked individually in the audit log via its filename patterns.
Can files be automatically organized by date or device ID?
Yes. Smart Paths let you template the destination folder structure using variables like {year}, {month}, {sender}, or {filename}. Configure once in the Pipe — no code required.
What cloud destinations are supported?
Any S3-compatible storage provider: AWS S3, Google Cloud Storage, Azure Blob, Cloudflare R2, Backblaze B2, Wasabi, MinIO, and more. You can also fan-out to multiple destinations simultaneously.
Bridge your legacy hardware to the cloud today.
No firmware changes. No migration risk. Point your device at Rilavek and your data lands in S3 within minutes.
Free plan includes 10GB of transfer. No credit card required.