Self-Hosted Secure File Transfer — Xferity Enterprise MFT
Self-Hosted File Transfer with Xferity
Section titled “Self-Hosted File Transfer with Xferity”Self-hosted file transfer means the transfer runtime, state, keys, and audit evidence stay inside infrastructure you own and control — not in a shared SaaS environment.
Why it matters
Section titled “Why it matters”- keys and certificates never leave your environment
- audit evidence stays where you decide it stays
- deployment options match your infrastructure (Linux, Windows, Docker, Kubernetes)
- change control and access control follow your policies
- no data leaves to a third-party service
What Xferity provides as a self-hosted runtime
Section titled “What Xferity provides as a self-hosted runtime”- a single Go binary — no application server, no JVM, no framework dependency
- file-backed mode for simple single-host deployments
- Postgres-backed mode for durable state, sessions, and worker execution
- Docker and Compose support out of the box
- Windows-native deployment for teams replacing Windows-based automation
Operational boundaries
Section titled “Operational boundaries”When you self-host Xferity, you own:
- the deployment host and its hardening
- the key and certificate material
- the database backup and restore
- the network routing for partner connectivity
- the audit log retention and export
Xferity provides the tools. The infrastructure boundary is yours.