RustFS Integration

FTP & SFTP to Self-Hosted RustFS

Point FTP, SFTP, and HTTP uploads at Rilavek, and files land on your own RustFS server for private, on-premises storage under your control.

  • Instant access
  • No migration required
  • No infrastructure to run
FTPSFTPHTTPSFTPSFTPFTPSFTPHTTPSFTPSFTP
CCTV
Camera
Browser
Server
Scripts
RustFS logo
RustFS
Rilavek LogoRilavek
Diagram showing FTP, FTPS, SFTP, and HTTPS uploads flowing through Rilavek into RustFS.
Capabilities

The file transfer bridge built for RustFS

Rilavek sits between your senders and RustFS, adding the protocols and access patterns your bucket does not expose on its own.

SFTP & FTP to RustFS

Connect legacy hardware, partner systems, and internal tools to RustFS without changing firmware or running a gateway server.

Explore SFTP ingest

Source

Cameras, devices, partners

Protocol

SFTP · FTP · FTPS

Destination

RustFS

Why Rilavek

Why Rilavek + RustFS

A protocol bridge, not a storage competitor. Your RustFS bucket stays the system of record.

  1. Files Go Straight to Your Bucket

    Nothing is staged or stored on our side. Uploads stream from the sender into RustFS, and retries are held in memory rather than on disk.

  2. Every Protocol, One Bucket

    Enable FTP, explicit FTPS, SFTP on port 2222, and resumable Tus uploads over HTTPS on the same pipe, with no gateway to operate.

  3. Your Hardware, Your Control

    RustFS runs on your own NAS or server, keeping data inside your network and under your operational control.

  4. One Upload, Several Buckets

    Send the same file to RustFS and any secondary stores in a single request. For each secondary, choose whether a failure should fail the whole upload or let it continue.

Scenarios

Common RustFS workloads

The same pipe handles device ingest, application uploads, and archival feeds without a separate gateway per use case.

On-premises archive

Keep files inside your own network while still accepting FTP and SFTP uploads.

Private camera storage

Send camera footage to a RustFS bucket on hardware you control.

Homelab and SMB drops

Give partners a public SFTP endpoint without exposing your internal file server.

Setup

How it works

From bucket to first file in three steps. No servers, agents, or local staging disk.

  1. 1

    Connect your RustFS bucket

    Add a Data Store in Rilavek with your access key, secret key, bucket name, and endpoint. Publicly accessible URL of your RustFS server with valid SSL/TLS (e.g. https://s3.yourdomain.com:9000).

    bucket

    access key

    secret key

    RustFS Token Guide
  2. 2

    Create a pipe

    Choose RustFS as the primary Data Store, then enable FTP, FTPS, SFTP, or resumable HTTP uploads for that pipe.

    ftp

    ftps

    sftp

    tus

    Pipe setup guide
  3. 3

    Point your senders at Rilavek

    Use ftp.rilavek.com for FTP/FTPS or the SFTP host and port 2222 from your pipe settings. Every file streams straight into RustFS.

    ftp: ftp.rilavek.com

    sftp: sftp.rilavek.com:2222

    FTP sender docs
Security

Secure by design

File transfer is the part of the stack you should not have to rebuild to trust.

Read the setup and security docs
Transport

Encrypted protocols

FTPS uses explicit TLS, SFTP uses SSH, and HTTP uploads use HTTPS. Plain FTP is available for legacy devices only.

Storage

No temporary storage layer

Files stream through memory only. Rilavek never writes uploads to disk, even during retries.

Access

Scoped credentials

Connect each destination with a bucket-scoped key or app password instead of an account-wide master key.

FAQ

RustFS integration questions

Protocol, credential, and setup answers for sending files into RustFS.

Can I point Rilavek at my own S3 server?

Yes. Any S3-compatible server reachable over HTTPS works, including RustFS, MinIO, and NAS gateways on Synology or TrueNAS. Use path-style addressing and a valid TLS certificate.

How should I expose RustFS to Rilavek?

Publish RustFS behind a public HTTPS URL with a valid certificate, for example https://s3.yourdomain.com:9000, and confirm path-style addressing is enabled.

Does RustFS support lifecycle retention?

That depends on your server configuration. Many S3-compatible servers support bucket lifecycle expiration; where they do not, schedule retention with an external job.

Does Rilavek store files before sending them to RustFS?

No. Rilavek streams each upload directly from the sender to your RustFS bucket. Transient retries use in-memory buffering only, so files are never written to Rilavek disks.

Which upload protocols can write to RustFS?

FTP, explicit FTPS, SFTP on port 2222, and resumable HTTP uploads over the Tus protocol. Protocols are enabled and disabled individually per pipe.

Can one upload go to RustFS and another destination at the same time?

Yes. A pipe can have RustFS as its primary Data Store plus one or more secondary stores. Replication happens inline as the file streams. For each secondary, you configure whether a transient error should fail the whole upload or be ignored so the transfer continues.

Do I need to change my application or device?

Only the destination host. Point FTP/FTPS at ftp.rilavek.com or SFTP at the host and port shown in your pipe settings, and keep using your existing client or firmware.

How do I test the integration before rolling it out?

Connect the bucket, create a pipe, and send a test file from your existing client. The dashboard shows delivery status and the resulting object key, so you can confirm the path before pointing production senders at Rilavek.

Is data encrypted in transit?

FTPS uses explicit TLS, SFTP uses SSH, and HTTP uploads use HTTPS. Plain FTP is available for legacy hardware that cannot negotiate encryption, but it should be limited to trusted networks.

Ready to send files to RustFS?

Set up your first pipe in under 2 minutes. No servers, no agents, no staging disk.