Backblaze B2 Integration

FTP & SFTP to Backblaze B2

Stream FTP, FTPS, SFTP, and resumable HTTP uploads straight into Backblaze B2, with no staging server and no copy stored on our side.

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

The file transfer bridge built for Backblaze B2

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

SFTP & FTP to Backblaze B2

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

Explore SFTP ingest

Source

Cameras, devices, partners

Protocol

SFTP · FTP · FTPS

Destination

Backblaze B2

Why Rilavek

Why Rilavek + Backblaze B2

A protocol bridge, not a storage competitor. Your Backblaze B2 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 Backblaze B2, 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. Archival-Grade Object Storage

    B2 is built for durable, write-heavy archives and supports native lifecycle rules that hide and then delete objects on a schedule.

  4. One Upload, Several Buckets

    Send the same file to Backblaze B2 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 Backblaze B2 workloads

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

Continuous backup and archival

Land nightly database dumps and file-system snapshots in B2 without building a local staging server.

Surveillance retention

Stream camera footage straight into B2 and let B2 lifecycle rules hide and delete old clips automatically.

Media libraries

Keep large photo and video libraries in durable object storage with S3-compatible tooling.

Setup

How it works

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

  1. 1

    Connect your Backblaze B2 bucket

    Add a Data Store in Rilavek with your access key, secret key, bucket name, and endpoint. Found on your Buckets page under Bucket Details in the Backblaze B2 console (e.g. https://s3.us-west-004.backblazeb2.com).

    bucket

    access key

    secret key

    Backblaze Keys
  2. 2

    Create a pipe

    Choose Backblaze B2 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 Backblaze B2.

    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

Backblaze B2 integration questions

Protocol, credential, and setup answers for sending files into Backblaze B2.

Is Backblaze B2 suitable for continuous uploads?

Yes. B2 handles write-heavy, read-light workloads and exposes S3-compatible APIs, so continuous feeds and lifecycle rules work without a staging server.

Which B2 credentials should I create?

Create an Application Key scoped to the target bucket with Read and Write access. Avoid the master application key so a single pipe cannot touch every bucket.

How do I set retention on B2?

Use B2's own lifecycle rules, not the S3 lifecycle API. In the Backblaze console open the bucket's Lifecycle Settings (or run b2 update-bucket with --lifecycleRules) and set how many days after upload a file is hidden plus how many days after hiding it is deleted — for example hide after 30 days and delete 30 days later. Hiding alone leaves the file billable, so the delete step is what frees storage.

Does Rilavek store files before sending them to Backblaze B2?

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

Which upload protocols can write to Backblaze B2?

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

Yes. A pipe can have Backblaze B2 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 Backblaze B2?

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