Documentation

Learn how to architect your data pipeline in minutes.

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.

Destination

Where your data ends up (S3, R2, B2).

Sync Event

Notifications via webhooks for each transfer.

Quick Start: FTP/S to S3

In this example, we will bridge a legacy FTP/S server to an S3 bucket in 4 steps.

01

Create your Destination

First, tell us where you want the data to go. Add your S3 credentials.

Destination Config
Name
My S3 Backup
Provider
AWS S3
Region
us-east-1
Access Key ID
AKIA...
Secret Access Key
••••••••••••••••
Bucket Name
my-archive-bucket
02

Create a Pipe

Create a new Pipe and enable input protocols (FTP, SFTP). We provide the high-availability endpoint.

Pipe Configuration
FTP Host
ftp.rilavek.com
Port
21
Pipe Short ID
p_x9z2a
03

Create & Assign Sender

Create an identity (e.g. 'Camera 01') and assign it to the Pipe. This generates unique credentials.

Sender Credentials
Sender Username
camera_01
Sender Password
pass
Credentials are specific to this Sender.
04

Connect the Pipe

Link them together. Any file uploaded to the FTP endpoint will immediately appear in your S3 bucket.

$ curl -T test.jpg -u "camera_01@p_x9z2a:pass" ftp://ftp.rilavek.com/
200 OK: Object created s3://my-archive-bucket/test.jpg

Ready to build your first pipe?

Go to Dashboard →