How to Create a Sender Identity
A Sender represents who or what uploads files. Instead of hardcoding fragile cloud storage API keys into client devices or remote servers, Rilavek uses lightweight Sender credentials that speak standard protocols like SFTP, FTP, and HTTP.
Welcome to Rilavek
Manage your data pipelines and cloud storage destinations with ease.
Step 1: Assign a Distinct Identifier
Navigate to Senders in your Rilavek dashboard and select New Sender. Give the identity a recognizable name based on its role in your workflow:
Marcus_Lead, Sarah_Uploads
Great for collaborative teams where operators or content creators need to attribute incoming files to specific contributors.
IoT_Gateway_01, OfficeScanner_A
Helpful for edge gateways, network scanners, branch appliances, or onsite hardware streaming data independently.
ETL_Worker_01, NightlyBackup
Useful for automated scripts, cron jobs, application pipelines, or batch processing workers.
Step 2: Generate & Save Client Password
Rilavek automatically creates a cryptographically strong password for each Sender. Copy this password and store it securely or paste it directly into your client settings.
Sender passwords authenticate only with Rilavek ingestion endpoints. They have zero direct access to your cloud provider console or master bucket keys, maintaining strict isolation even if a remote device or client credential is compromised.
Step 3: How to Format Your Username
When connecting via FTP or SFTP, your username tells Rilavek who is sending the file and which Pipe should receive it. Just join your Sender name and Pipe ID with an @ symbol:
Step 4: Smart Folder Isolation
When you turn on Isolate Files to Sender Subfolder, Rilavek automatically prefixes incoming file paths with the Sender name. An incoming file called report_2026.pdf sent by BranchOffice01 will land at:
This keeps multi-client ingestion completely organized without requiring uploaders to manage folder structures on the sending side.
Guide 03: Create a Pipe
Enable ingress protocols (FTP, SFTP, HTTP), authorize senders, and configure delivery routing.