STRG Integration

FTP & SFTP to STRG Object Storage

Stream FTP, SFTP, and HTTP uploads into STRG Object Storage, with EU or US regions and no minimum retention period.

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

The file transfer bridge built for STRG

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

SFTP & FTP to STRG

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

Explore SFTP ingest

Source

Cameras, devices, partners

Protocol

SFTP · FTP · FTPS

Destination

STRG

Why Rilavek

Why Rilavek + STRG

A protocol bridge, not a storage competitor. Your STRG 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 STRG, 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. No Minimum Retention

    STRG has no minimum storage duration, so short-lived files can expire on your schedule without a retention penalty.

  4. One Upload, Several Buckets

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

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

Video archive

Keep surveillance footage in a dedicated bucket with lifecycle rules for expiry.

Short-retention workloads

Expire files on a short schedule without a minimum storage duration penalty.

EU and US backups

Choose a Frankfurt or Virginia region and stream backups straight into the bucket.

Setup

How it works

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

  1. 1

    Connect your STRG bucket

    Add a Data Store in Rilavek with your access key, secret key, bucket name, and endpoint. STRG endpoints are regional (e.g. https://s3.eu-central-1.strg.com or https://s3.us-east-1.strg.com).

    bucket

    access key

    secret key

    STRG Access Keys
  2. 2

    Create a pipe

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

    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

STRG integration questions

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

Does STRG support S3 lifecycle rules?

Yes. STRG is S3-compatible and supports lifecycle expiration and transitions on your buckets.

Does STRG have a minimum retention period?

No. STRG has no minimum storage duration, so you can expire files on a short schedule.

Which regions does STRG offer?

STRG provides EU Central (https://s3.eu-central-1.strg.com) and US East (https://s3.us-east-1.strg.com). Choose the region that matches your bucket.

Does Rilavek store files before sending them to STRG?

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

Which upload protocols can write to STRG?

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

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

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