S3-Compatible Destinations

Storage Integrations

Point FTP, FTPS, SFTP, or resumable HTTP uploads at Rilavek, and we securely deliver every file to the object storage you already run.

  • Instant access
  • No migration required
  • No infrastructure to run
Sources
Storage
FTPSFTPHTTPSFTPSFTPFTPSFTPHTTPSFTPSFTP
CCTV
Camera
Browser
Server
Scripts
AWS S3
Cloudflare R2
Backblaze B2
Wasabi
DigitalOcean Spaces
Webhook
Email
Rilavek LogoRilavek
Event Notifications & Integrations
Diagram showing CCTV, camera, browser, server, and script uploads flowing through Rilavek into AWS S3, Cloudflare R2, Backblaze B2, Wasabi, and DigitalOcean Spaces, with webhook and email event notifications.
Setup

How it works

Connect a bucket, create a pipe, and keep your existing senders. No servers, agents, or local staging disk.

  1. 1

    Connect your bucket

    Add a Data Store with your S3-compatible endpoint, region, bucket name, and scoped access keys.

    endpoint

    bucket

    access key

    Data store guide
  2. 2

    Create a pipe

    Choose the bucket as the primary destination, then enable FTP, FTPS, SFTP, or resumable HTTP uploads.

    ftp

    ftps

    sftp

    tus

    Pipe setup guide
  3. 3

    Point your senders at Rilavek

    Use the host shown in your pipe settings. Your existing client or device firmware stays the same.

    ftp.rilavek.com

    sftp.rilavek.com:2222

    Sender docs
FAQ

Integration questions

Protocol, credential, and setup answers for connecting your storage.

Which storage providers can I connect?

Any S3-compatible endpoint works. Destinations with their own dedicated setup guide include Cloudflare R2, Backblaze B2, AWS S3, Wasabi Hot Cloud, IDrive e2, DigitalOcean Spaces, Filebase, Scaleway, STRG, Hetzner Object Storage, Oracle Cloud, Tigris, and self-hosted RustFS. Anything else that exposes an S3-compatible API connects through the generic S3 option.

Do I need to change my application or device?

Only the destination host. Point FTP/FTPS at ftp.rilavek.com or SFTP at sftp.rilavek.com on port 2222, and keep using your existing client or device firmware.

Does Rilavek store my files?

No. Files stream directly from the sender to your bucket. Rilavek never writes uploads to disk, and retries use in-memory buffering only.

Can I send the same file to more than one provider?

Yes. A pipe can have a primary Data Store plus secondary stores. For each secondary, you configure whether a failure should fail the whole upload or continue silently.

Which protocols can write to my bucket?

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

What if my provider is not listed?

Enter your endpoint, region, and credentials yourself — in the dashboard this is the "Other S3 Compatible" data store. If the provider exposes an S3-compatible API, it works as a destination. The S3 data store guide in the docs walks through the setup.

Ready to connect your storage?

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