SFTP / FTPS SERVER IN. FILEROUTER (ON-PREMISE) OUT. NO SCRIPTS.
A hosted SFTP server that delivers uploads into a folder on your own server
DocEvent hosts an SFTP, SCP and FTPS server for your senders and the Filerouter agent writes each completed upload into a folder on your own server. The agent connects outbound over HTTPS - no inbound ports, no VPN - so you receive SFTP uploads on-premise without running an internet-facing server.
From
SFTP / FTPS Server
To
Filerouter (on-premise)
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Filespull
Servers & protocols
SFTP / FTPS Serverhosted · you push
FTP Pull
SFTP Pull
HTTP Upload
Email
Apps & trading partners
SharePointpull
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
Cloud storage
Amazon S3s3-compatible
GCSpush
Azure Blobpush
Servers & protocols
FTP / FTPS
SFTP
Webhook
Email
Apps & trading partners
SharePoint
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.
How SFTP / FTPS Server to Filerouter (on-premise) routing works
Source
SFTP / FTPS Server
DocEvent hosts an SFTP, SCP and FTPS server for you. Customers, partners and your own systems upload to it with their own login, and every completed upload enters the channel.
DocEvent Channel
routes · retries · logs
Destination
Filerouter
Files are delivered into a local folder on your own server by the Filerouter agent.
1
File arrives via SFTP / FTPS Server
A hosted upload server, not a poll of yours: SFTP and SCP on port 22, explicit (AUTH TLS, port 21) and implicit (port 990) FTPS - cleartext FTP is refused. Usernames, passwords and SSH keys are managed in the console, with a per-service IP firewall and a browser uploader for people without a client. The login is upload-only: a file leaves the server the moment its upload completes, so nothing sits on it and there is nothing to poll.
2
Channel routes it
DocEvent's channel server matches the incoming file to your configured route, queues it for delivery, and ensures no file is ever lost — even during downstream outages.
3
Delivered to Filerouter (on-premise)
The agent connects out to DocEvent over HTTPS — no inbound ports to open — and writes each delivered file into the folder you choose, acknowledging every file so restarts and dropped connections never lose one or deliver it twice.
Common use cases
Real workflows that teams automate with a SFTP / FTPS Server → Filerouter (on-premise) channel.
- Receive partner uploads on-premise without exposing an SFTP port
- Replace an internet-facing SFTP box with an outbound-only agent
- Land files straight into the directory an application watches
- Every file acknowledged - restarts and dropped connections lose nothing
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the SFTP / FTPS Server or Filerouter (on-premise) side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
SFTP / FTPS Server
A hosted upload server, not a poll of yours: SFTP and SCP on port 22, explicit (AUTH TLS, port 21) and implicit (port 990) FTPS - cleartext FTP is refused. Usernames, passwords and SSH keys are managed in the console, with a per-service IP firewall and a browser uploader for people without a client. The login is upload-only: a file leaves the server the moment its upload completes, so nothing sits on it and there is nothing to poll.
DocEvent hosts an SFTP, SCP and FTPS server for you. Customers, partners and your own systems upload to it with their own login, and every completed upload enters the channel.Destination:
Filerouter
The agent connects out to DocEvent over HTTPS — no inbound ports to open — and writes each delivered file into the folder you choose, acknowledging every file so restarts and dropped connections never lose one or deliver it twice.
Files are delivered into a local folder on your own server by the Filerouter agent.Automatic retries with exponential back-off
Full end-to-end audit log for every file
Zero-code setup via the DocEvent UI
Reliable delivery even during downstream outages
Related channel integrations
Other destinations from SFTP / FTPS Server
Other sources to Filerouter (on-premise)
- Amazon S3 → Filerouter (on-premise)
- HTTP Upload → Filerouter (on-premise)
- Email → Filerouter (on-premise)
- AS2 → Filerouter (on-premise)
- Filerouter (on-premise) → Filerouter (on-premise)
- FTP Pull → Filerouter (on-premise)
- SFTP Pull → Filerouter (on-premise)
- S3 Compatible (pull) → Filerouter (on-premise)
- GCS Blob Pull → Filerouter (on-premise)
- Azure Blob Pull → Filerouter (on-premise)
- Azure Files Pull → Filerouter (on-premise)
- SharePoint → Filerouter (on-premise)
- DocEvent Agent (on-prem) → Filerouter (on-premise)