Cloudflare R2 Integration

FTP & SFTP to Cloudflare R2

Give cameras, partners, and legacy apps an FTP, SFTP, or HTTP endpoint that streams straight into R2 and is ready for fast global reads.

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

The file transfer bridge built for Cloudflare R2

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

SFTP & FTP to Cloudflare R2

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

Explore SFTP ingest

Source

Cameras, devices, partners

Protocol

SFTP · FTP · FTPS

Destination

Cloudflare R2

Why Rilavek

Why Rilavek + Cloudflare R2

A protocol bridge, not a storage competitor. Your Cloudflare R2 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 Cloudflare R2, 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. Built for Read-Heavy Workloads

    R2 is designed for frequent reads, so reviewing footage or serving uploaded files back to users stays fast and simple.

  4. One Upload, Several Buckets

    Send the same file to Cloudflare R2 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 Cloudflare R2 workloads

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

CCTV and motion clips

Send camera footage to R2 over FTP, then replay or download clips from the same bucket.

Web and app uploads

Accept browser uploads through resumable Tus endpoints and serve the objects straight from R2.

Partner drop folders

Give vendors SFTP credentials that land files in an R2 bucket you control, with optional replication to a second store.

Setup

How it works

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

  1. 1

    Connect your Cloudflare R2 bucket

    Add a Data Store in Rilavek with your access key, secret key, bucket name, and endpoint. Copy your API endpoint URL from the Cloudflare R2 dashboard (https://<account_id>.r2.cloudflarestorage.com).

    bucket

    access key

    secret key

    Cloudflare Tokens
  2. 2

    Create a pipe

    Choose Cloudflare R2 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 Cloudflare R2.

    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

Cloudflare R2 integration questions

Protocol, credential, and setup answers for sending files into Cloudflare R2.

How does Cloudflare R2 handle downloads?

R2 serves objects from Cloudflare's global network, which keeps playback and downloads fast for distributed users. Rilavek writes the object; R2 handles delivery.

What endpoint and credentials do I use for R2?

Use https://<account_id>.r2.cloudflarestorage.com and an R2 API token with Object Read & Write scoped to the bucket. Rilavek sets region to auto and uses path-style addressing.

Does R2 work with standard S3 tools?

Yes. R2 exposes an S3-compatible API, so existing S3 SDKs, lifecycle rules, and tools work alongside the FTP, SFTP, and Tus endpoints Rilavek adds.

Does Rilavek store files before sending them to Cloudflare R2?

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

Which upload protocols can write to Cloudflare R2?

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 Cloudflare R2 and another destination at the same time?

Yes. A pipe can have Cloudflare R2 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 Cloudflare R2?

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