Syncplify R2FS! · an add-on to Syncplify Server!
Your storage never faces the internet.
R2FS! lets Syncplify Server! in your DMZ use storage inside your network or your cloud, without opening a single inbound port. Your storage connects out to Server!, never the other way around, so nothing on the internet can reach it.
R2FS! works with every Server! edition. Runs on Windows and Linux.
Your SFTP server belongs in the DMZ. Your files don't.
A file server that faces the internet should sit in a DMZ. But the files it receives belong on internal storage, and that leaves most teams with two bad options.
✕Option 1
Keep the files in the DMZ
The most exposed part of your network ends up holding your most sensitive data.
✕Option 2
Open a port from the DMZ to your storage
Now a compromised DMZ host has a path into your internal network, and you'll be justifying that firewall exception to every internal and external auditor, year after year.
✓The R2FS! way
With R2FS!
Your storage stays inside, and the DMZ never gets a way in. R2FS! runs next to your storage and connects out to Server!, so the firewall between them stays closed.
Close every inbound port.
- Install R2FS! inside your networkNext to the storage you want to use: a file server, a NAS, a network share, distributed storage such as DFS, or cloud storage: Amazon S3, Azure Blob Storage or Google Cloud Storage.
- R2FS! connects out to Server!Only outbound traffic, authenticated in both directions with mutual TLS (or a pre-shared key). The DMZ never connects inward. Once the connection is up, files travel both ways inside it, so uploads and downloads work as usual.
- Your users see a normal folderOn Server!, the internal storage appears as a virtual folder. Users connect over SFTP, FTPS or HTTPS as always and never know the files live elsewhere.
Files stream straight through Server! to your storage. They are never stored or cached in the DMZ, not even temporarily. And nothing changes for your users or your trading partners.
Built for the security review.
No inbound ports
Not one. R2FS! opens the connection from inside, so your firewall rules toward internal storage stay exactly as strict as they are today.
Nothing to steal in the DMZ
Files stream straight through Server! to your storage and are never stored or cached in the DMZ, not even temporarily. Break into the DMZ host, and there are no files to take.
Mutual authentication
R2FS! and Server! verify each other with mutual TLS, using X.509 certificates tied to an identity, or a pre-shared key. An impostor on either side gets nowhere.
Scales and stays up
Connect one R2FS! node to every Server! node in your cluster, add R2FS! nodes for redundancy, and put distributed storage behind them. If a node fails, transfers keep going.
One server or a whole cluster. One storage or many.
The same building blocks fit very different networks. These are the five setups we see most.
One server, one storage
The simplest start: Server! in the DMZ, R2FS! next to your file server, one outbound connection between them.
A high availability cluster
A load balancer spreads partners across several Server! nodes. One R2FS! node connects out to each of them, so every node sees the same files.
Redundant R2FS! nodes
Two or more R2FS! nodes in front of distributed storage, such as DFS. If an R2FS! node or a storage node fails, transfers keep going.
Many storages, one network
A single R2FS! node can expose as many storage locations as you need, with no limit, each as its own virtual folder on Server!. Mix disks, shares and cloud storage as your teams need.
Your cloud, zero inbound rules
Run R2FS! on a cloud instance, such as AWS EC2, next to Amazon S3. Its security group needs zero inbound rules, because R2FS! only connects out to Server!. The same works with Azure Blob Storage and Google Cloud Storage.
Planning something bigger? Our engineers design and deploy it with you. Professional Services →
Your scripts, on the storage side.
R2FS! runs the same SyncJS scripts as Server!, right next to your storage, behind your firewall. 16 events let you scan, move, rename or encrypt files where they land, without ever exposing them. If you already script Server!, there's nothing new to learn.
No time to write them? We'll write them for youR2FS! completes Server!.
R2FS! is an add-on to Syncplify Server! and needs it to run. Server! faces the internet; R2FS! keeps the storage inside.
Explore Server! → AFT!Automate transfers to and from your partners, scripted in the same SyncJS.
Meet AFT! → Professional ServicesWe design your DMZ layout, deploy Server! and R2FS!, and write the scripts you need.
Talk to our engineers →Your ticket is handled by the people who wrote the code.
Every ticket is answered by a Syncplify engineer who knows R2FS! down to the source code. We have never outsourced support, and we never will. Prefer a human from the start? Skip the optional AI assistant and go straight to an engineer.
About maintenance and support →Questions we hear often
Does R2FS! work without Server!?
No. R2FS! is an add-on to Syncplify Server! and needs a licensed Server! to run.
Which Server! editions support R2FS!?
All of them: Basic, Professional and Ultimate. Through R2FS!, even Server! Basic can use Amazon S3, Azure Blob Storage and Google Cloud Storage, which otherwise need Professional.
Do I need to open any inbound ports?
No. R2FS! only makes outbound connections to Server!. Nothing in your DMZ or on the internet ever connects to your storage, and in the cloud, the instance running R2FS! needs zero inbound rules.
Which storage can R2FS! use?
Local disks, network shares, distributed storage such as DFS, and cloud storage: Amazon S3, Azure Blob Storage and Google Cloud Storage.
Where does R2FS! run?
On Windows or Linux, next to your storage: on your own servers, or on a cloud instance such as AWS EC2.
Can I run more than one R2FS! node?
Yes, and each R2FS! node can connect to every Server! node in a high availability cluster. Several R2FS! nodes in front of distributed storage (such as DFS) keep files reachable even if a node fails.
How is R2FS! licensed?
Per R2FS! node, as a perpetual license.
Can R2FS! run scripts?
Yes, the same SyncJS scripts as Server!, triggered by 16 events, on the storage side of your firewall.
See R2FS! in your own network.
R2FS! has its own free 15-day trial, on the same Download page as Server!. Install both and see your storage stay inside, with every feature and no credit card.