FTP & SFTP to Tigris Data
Deliver uploads from edge devices, cameras, and applications into Tigris's globally distributed object storage.
- Instant access
- No migration required
- No infrastructure to run
The file transfer bridge built for Tigris Data
Rilavek sits between your senders and Tigris Data, adding the protocols and access patterns your bucket does not expose on its own.
SFTP & FTP to Tigris Data
Connect legacy hardware, partner systems, and internal tools to Tigris Data without changing firmware or running a gateway server.
Explore SFTP ingestSource
Cameras, devices, partners
Protocol
SFTP · FTP · FTPS
Destination
Tigris Data
Resumable uploads to Tigris Data
Accept large files from browsers, APIs, and server-side clients over the Tus protocol, with pause and resume built in.
Explore resumable uploadsSource
Browsers, APIs, servers
Protocol
HTTP (Tus) over HTTPS
Destination
Tigris Data
Partner drop folders in Tigris Data
Issue scoped SFTP or FTPS credentials so vendors and customers can deliver files into a bucket you control.
Explore partner exchangeSource
Vendors, customers
Protocol
SFTP · FTPS
Destination
Tigris Data
Replication beyond Tigris Data
Replicate each upload to Tigris Data and a secondary store in the same request, without a second upload or copy job.
Explore replicationSource
Any sender
Protocol
Inline fan-out
Destination
Tigris Data
Why Rilavek + Tigris Data
A protocol bridge, not a storage competitor. Your Tigris Data bucket stays the system of record.
Files Go Straight to Your Bucket
Nothing is staged or stored on our side. Uploads stream from the sender into Tigris Data, and retries are held in memory rather than on disk.
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.
Global Distribution, Low Write Latency
Tigris distributes objects across regions and exposes a single global endpoint, so edge senders get low-latency writes without choosing a region.
One Upload, Several Buckets
Send the same file to Tigris Data and any secondary stores in a single request. For each secondary, choose whether a failure should fail the whole upload or let it continue.
Common Tigris Data workloads
The same pipe handles device ingest, application uploads, and archival feeds without a separate gateway per use case.
Globally distributed apps
Accept uploads from users in multiple regions and serve them from the same global bucket.
Edge and camera ingest
Send field device footage to a globally distributed bucket with low write latency.
Media delivery
Store and retrieve media through a globally distributed bucket.
How it works
From bucket to first file in three steps. No servers, agents, or local staging disk.
- 1
Connect your Tigris Data bucket
Add a Data Store in Rilavek with your access key, secret key, bucket name, and endpoint. Global endpoint: https://t3.storage.dev (or https://fly.storage.tigris.dev for Fly.io). Region is 'auto'.
Tigris Access Keysbucket
access key
secret key
- 2
Create a pipe
Choose Tigris Data as the primary Data Store, then enable FTP, FTPS, SFTP, or resumable HTTP uploads for that pipe.
Pipe setup guideftp
ftps
sftp
tus
- 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 Tigris Data.
FTP sender docsftp: ftp.rilavek.com
sftp: sftp.rilavek.com:2222
Secure by design
File transfer is the part of the stack you should not have to rebuild to trust.
- 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.
Tigris Data integration questions
Protocol, credential, and setup answers for sending files into Tigris Data.
How does Tigris handle global access?
Tigris uses a globally distributed architecture behind a single endpoint, so uploads and reads are routed automatically without region selection.
How do I configure Tigris in Rilavek?
Create a bucket in the Tigris Console, generate an access key, use https://t3.storage.dev as the endpoint, and set region to auto.
Does Tigris require a region?
No. Use https://t3.storage.dev as the endpoint and set region to auto; Tigris handles placement.
Does Rilavek store files before sending them to Tigris Data?
No. Rilavek streams each upload directly from the sender to your Tigris Data bucket. Transient retries use in-memory buffering only, so files are never written to Rilavek disks.
Which upload protocols can write to Tigris Data?
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 Tigris Data and another destination at the same time?
Yes. A pipe can have Tigris Data 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.
Other storage integrations
The same protocol bridge works with every supported object store.

Cloudflare R2
Object storage built for read-heavy workloads

Backblaze B2
Durable object storage for write-heavy archives

Wasabi Hot Cloud
Hot cloud storage for active data

IDrive e2
Object storage with regional endpoints

DigitalOcean Spaces
Object storage with a built-in CDN

AWS S3
Enterprise S3 with Glacier archiving

Filebase
Decentralized object storage behind a standard S3 API

Scaleway
EU-hosted object storage for data residency
Ready to send files to Tigris Data?
Set up your first pipe in under 2 minutes. No servers, no agents, no staging disk.