SFTP / FTPS SERVER IN. DOCEVENT AGENT (ON-PREM) OUT. NO SCRIPTS.
A hosted SFTP server that delivers uploads to a folder the DocEvent Agent manages
DocEvent hosts an SFTP, SCP and FTPS server for your senders and the console-managed DocEvent Agent saves each completed upload into a local folder on your own machine. Outbound TLS only, folder chosen from the web console, every transfer audited.
From
SFTP / FTPS Server
To
DocEvent Agent (on-prem)
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 DocEvent Agent (on-prem) 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
DocEvent Agent
Files are delivered into a local folder on your own machine by the DocEvent 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 DocEvent Agent (on-prem)
The agent connects outbound over TLS — no inbound ports to open — and writes each delivered file into the folder you pick from the web console. Every file is acknowledged, so restarts and dropped connections never lose or duplicate one.
Common use cases
Real workflows that teams automate with a SFTP / FTPS Server → DocEvent Agent (on-prem) channel.
- Receive partner uploads on-premise with no inbound ports open
- Pick the delivery folder from the web console - no local config files
- Retire an internet-facing SFTP server behind your firewall
- Every file acknowledged and audited end to end
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 DocEvent Agent (on-prem) 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:
DocEvent Agent
The agent connects outbound over TLS — no inbound ports to open — and writes each delivered file into the folder you pick from the web console. Every file is acknowledged, so restarts and dropped connections never lose or duplicate one.
Files are delivered into a local folder on your own machine by the DocEvent 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 DocEvent Agent (on-prem)
- Amazon S3 → DocEvent Agent (on-prem)
- HTTP Upload → DocEvent Agent (on-prem)
- Email → DocEvent Agent (on-prem)
- AS2 → DocEvent Agent (on-prem)
- Filerouter (on-premise) → DocEvent Agent (on-prem)
- FTP Pull → DocEvent Agent (on-prem)
- SFTP Pull → DocEvent Agent (on-prem)
- S3 Compatible (pull) → DocEvent Agent (on-prem)
- GCS Blob Pull → DocEvent Agent (on-prem)
- Azure Blob Pull → DocEvent Agent (on-prem)
- Azure Files Pull → DocEvent Agent (on-prem)
- SharePoint → DocEvent Agent (on-prem)
- DocEvent Agent (on-prem) → DocEvent Agent (on-prem)