FTP & SFTP to Hetzner Object Storage
Point your existing senders at Rilavek's FTP, SFTP, or HTTP endpoints, and uploads stream into Hetzner Object Storage with your data staying in EU data centers.
- Instant access
- No migration required
- No infrastructure to run
The file transfer bridge built for Hetzner Object Storage
Rilavek sits between your senders and Hetzner Object Storage, adding the protocols and access patterns your bucket does not expose on its own.
SFTP & FTP to Hetzner Object Storage
Connect legacy hardware, partner systems, and internal tools to Hetzner Object Storage without changing firmware or running a gateway server.
Explore SFTP ingestSource
Cameras, devices, partners
Protocol
SFTP · FTP · FTPS
Destination
Hetzner Object Storage
Resumable uploads to Hetzner Object Storage
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
Hetzner Object Storage
Partner drop folders in Hetzner Object Storage
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
Hetzner Object Storage
Replication beyond Hetzner Object Storage
Replicate each upload to Hetzner Object Storage and a secondary store in the same request, without a second upload or copy job.
Explore replicationSource
Any sender
Protocol
Inline fan-out
Destination
Hetzner Object Storage
Why Rilavek + Hetzner Object Storage
A protocol bridge, not a storage competitor. Your Hetzner Object Storage 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 Hetzner Object Storage, 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.
EU Data Centers, Standard S3 API
Hetzner hosts object storage in Germany and Finland with a standard S3 API and lifecycle support.
One Upload, Several Buckets
Send the same file to Hetzner Object Storage 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 Hetzner Object Storage workloads
The same pipe handles device ingest, application uploads, and archival feeds without a separate gateway per use case.
GDPR-sensitive workloads
Store files in ISO 27001-certified German and Finnish data centers.
Surveillance archive
Write continuous or motion-triggered clips into a bucket with lifecycle retention.
Backup target
Use a dedicated bucket as an offsite backup target.
How it works
From bucket to first file in three steps. No servers, agents, or local staging disk.
- 1
Connect your Hetzner Object Storage bucket
Add a Data Store in Rilavek with your access key, secret key, bucket name, and endpoint. Hetzner endpoints use your bucket's regional location (e.g. https://fsn1.your-objectstorage.com, https://nbg1.your-objectstorage.com, or https://hel1.your-objectstorage.com).
Hetzner Consolebucket
access key
secret key
- 2
Create a pipe
Choose Hetzner Object Storage 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 Hetzner Object Storage.
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.
Hetzner Object Storage integration questions
Protocol, credential, and setup answers for sending files into Hetzner Object Storage.
Which regions does Hetzner offer?
Hetzner Object Storage is available in Falkenstein (fsn1), Nuremberg (nbg1), and Helsinki (hel1). Choose the endpoint that matches your bucket.
Does Hetzner support S3 lifecycle rules?
Yes. Hetzner Object Storage supports standard S3 lifecycle expiration and cleanup policies.
How do I create Hetzner credentials?
Generate S3 credentials in the Hetzner Cloud Console under Security > S3 Credentials. Each key pair is valid for all buckets in the project.
Does Rilavek store files before sending them to Hetzner Object Storage?
No. Rilavek streams each upload directly from the sender to your Hetzner Object Storage bucket. Transient retries use in-memory buffering only, so files are never written to Rilavek disks.
Which upload protocols can write to Hetzner Object Storage?
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 Hetzner Object Storage and another destination at the same time?
Yes. A pipe can have Hetzner Object Storage 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 Hetzner Object Storage?
Set up your first pipe in under 2 minutes. No servers, no agents, no staging disk.