What is Rilavek?
Rilavek is a managed, pass-through data pipeline that bridges inbound transfer protocols (SFTP, FTP/FTPS, and HTTP) directly into your S3-compatible cloud storage.
Protocol Agnostic
Connect surveillance cameras, legacy appliances, enterprise partners, or web applications without building custom ingest servers.
Zero-Disk Pass-Through
Files stream straight through memory to your destination buckets. Data is never cached on our disks, which keeps transfers secure and private.
Multi-Cloud Fan-out
Replicate incoming transfers across AWS S3, Cloudflare R2, Backblaze B2, or MinIO concurrently from a single client upload.
The Mental Model
Rilavek treats data transfer as a stream, not a storage problem. Our architecture is based on five primitives:
Source
The ingress protocol (FTP, SFTP, HTTP).
Sender
Who is sending the data (identity & credentials).
Pipe
The logic layer. Handles routing and fan-out.
Data Store
Where your data ends up (S3, R2, B2).
Alerts
Webhooks for transfers and email alerts for pipeline silence.
How the 5 Primitives Connect
Data flows directly from authorized senders through the routing pipe into destination storage buckets, with webhooks and silence alerts keeping you updated.
Delivery Guarantees & Fan-out
A single upload can stream to multiple cloud data stores at the exact same time, delivering your files in parallel without storing anything on disk.
Simultaneous Multi-Store Streaming
Rilavek delivers your files to multiple storage providers simultaneously. You can send data to AWS S3, Cloudflare R2, and Wasabi all at once from a single upload, without waiting for slow batch syncs or keeping copies on local disks.
Primary Delivery Guarantee
Your Primary Data Store acts as the essential destination. If it rejects the file, the entire upload stops immediately so your client can retry. For secondary mirrors, choose Tolerant Mode to ignore mirror glitches or Strict Mode to require every destination to succeed.
File Transfer Lifecycle
Every file moving through a pipe is tracked with a real-time status across each configured destination:
| Status | Description |
|---|---|
| Processing | The upload has started. Data streams through Rilavek memory directly to your configured storage destinations with zero local disk buffering. |
| Success | The upload stream finished cleanly. Both the primary data store and all required secondary destinations confirmed and committed the file. Optional secondary destinations that fail do not block this success state. |
| Failed | The transfer could not finish. This triggers if the primary storage hits authentication issues, connection timeouts, or write errors, or if a secondary destination marked with strict delivery fails. |
| Cancelled | The client disconnected or aborted mid-stream, or an abandoned transfer timed out and was cleaned up by the background sweeper (which also aborts any dangling multipart uploads on your storage provider). |
Pipeline Health & Inactivity Monitoring
Most data pipelines fail in silence. An offline IP camera or a stalled backup script rarely throws a visible error. They simply stop transmitting.
Configurable Silence Detection
When enabled on a pipe, Rilavek continuously tracks your stream heartbeat. If a pipeline with baseline transfer history receives zero files past its silence threshold (configurable from 1 to 7 days, defaulting to 1 day / 24 hours), an automated alert drops straight into your email inbox with direct diagnostic links.
Smart Deduplication & Auto-Reset
Nobody wants inbox spam during prolonged maintenance. Once an alert fires, subsequent reminders stay muted while the outage persists. As soon as your device reconnects and pushes a new file, the monitor re-arms itself automatically.
Guide 01: Connect Data Store
Link AWS S3, Cloudflare R2, Wasabi, or Backblaze B2 buckets with zero public credentials exposed.