Filebase Integration

FTP & SFTP to Filebase

Send FTP, SFTP, and HTTP uploads into Filebase's decentralized storage, keeping the same buckets and keys you already use.

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

The file transfer bridge built for Filebase

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

SFTP & FTP to Filebase

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

Explore SFTP ingest

Source

Cameras, devices, partners

Protocol

SFTP · FTP · FTPS

Destination

Filebase

Why Rilavek

Why Rilavek + Filebase

A protocol bridge, not a storage competitor. Your Filebase 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 Filebase, 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. Decentralized Storage Behind S3

    Filebase exposes a standard S3 API backed by decentralized networks such as IPFS, Sia, and Storj, so existing upload flows keep working.

  4. One Upload, Several Buckets

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

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

Content-addressed media

Pin media to decentralized storage while keeping a familiar bucket and key layout.

Web3 and dapp assets

Let apps and partners upload assets over SFTP without integrating a new SDK.

Offsite backup copies

Use Filebase as an independent second copy for critical files.

Setup

How it works

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

  1. 1

    Connect your Filebase bucket

    Add a Data Store in Rilavek with your access key, secret key, bucket name, and endpoint.

    bucket

    access key

    secret key

    Filebase Keys
  2. 2

    Create a pipe

    Choose Filebase 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 Filebase.

    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

Filebase integration questions

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

What is Filebase backed by?

Filebase provides an S3-compatible API over decentralized storage networks including IPFS, Sia, and Storj. Your applications use normal S3 credentials and buckets.

Does Filebase work with standard S3 tools?

Yes. Filebase exposes an S3-compatible API, so existing S3 SDKs and tools work with your decentralized buckets.

How does Filebase organize objects?

Filebase uses standard buckets and object keys over an S3-compatible API, so uploaded files keep the same paths and structure you configure in Rilavek.

Does Rilavek store files before sending them to Filebase?

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

Which upload protocols can write to Filebase?

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

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

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