FTP & SFTP to Scaleway Object Storage
Keep file ingest and storage in the EU by connecting your existing FTP, SFTP, and HTTP workflows to Scaleway Object Storage.
- Instant access
- No migration required
- No infrastructure to run
The file transfer bridge built for Scaleway
Rilavek sits between your senders and Scaleway, adding the protocols and access patterns your bucket does not expose on its own.
SFTP & FTP to Scaleway
Connect legacy hardware, partner systems, and internal tools to Scaleway without changing firmware or running a gateway server.
Explore SFTP ingestSource
Cameras, devices, partners
Protocol
SFTP · FTP · FTPS
Destination
Scaleway
Resumable uploads to Scaleway
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
Scaleway
Partner drop folders in Scaleway
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
Scaleway
Replication beyond Scaleway
Replicate each upload to Scaleway and a secondary store in the same request, without a second upload or copy job.
Explore replicationSource
Any sender
Protocol
Inline fan-out
Destination
Scaleway
Why Rilavek + Scaleway
A protocol bridge, not a storage competitor. Your Scaleway 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 Scaleway, 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 Hosting and Regional Control
Scaleway hosts object storage in Paris, Amsterdam, Warsaw, and Milan, keeping ingest and storage inside the EU.
One Upload, Several Buckets
Send the same file to Scaleway 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 Scaleway workloads
The same pipe handles device ingest, application uploads, and archival feeds without a separate gateway per use case.
EU data residency
Keep ingested files inside EU regions for data-sovereignty requirements.
Application uploads
Accept SFTP and resumable HTTP uploads from internal tools and customer apps.
Backup and archive
Send scheduled backups to a nearby EU bucket without extra gateway servers.
How it works
From bucket to first file in three steps. No servers, agents, or local staging disk.
- 1
Connect your Scaleway bucket
Add a Data Store in Rilavek with your access key, secret key, bucket name, and endpoint.
Scaleway API Keysbucket
access key
secret key
- 2
Create a pipe
Choose Scaleway 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 Scaleway.
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.
Scaleway integration questions
Protocol, credential, and setup answers for sending files into Scaleway.
Where is Scaleway Object Storage hosted?
Scaleway offers object storage regions in Paris (fr-par), Amsterdam (nl-ams), Warsaw (pl-waw), and Milan (it-mil), all within the EU.
Which region should I choose?
Pick the region closest to your senders: fr-par, nl-ams, pl-waw, or it-mil. Rilavek uses the matching regional S3 endpoint.
Does Scaleway support lifecycle rules?
Yes. Scaleway Object Storage supports S3 lifecycle rules for expiring or transitioning objects over time.
Does Rilavek store files before sending them to Scaleway?
No. Rilavek streams each upload directly from the sender to your Scaleway bucket. Transient retries use in-memory buffering only, so files are never written to Rilavek disks.
Which upload protocols can write to Scaleway?
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 Scaleway and another destination at the same time?
Yes. A pipe can have Scaleway 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

STRG
EU and US regions with no minimum retention
Ready to send files to Scaleway?
Set up your first pipe in under 2 minutes. No servers, no agents, no staging disk.