What is managed file transfer?

Managed file transfer (MFT) is the layer on top of plain file copying. It takes care of automated sending, integrity checks, central monitoring and an audit trail. An SFTP server encrypts the connection, but you still have to script sending, retries, checks and reporting yourself. Emona MFT gives small and mid-size businesses that layer without the size and cost of an enterprise MFT suite. It is built on jFiltra, our source-available transfer engine (PolyForm Noncommercial 1.0.0).

Visit emonamft.com jFiltra on GitHub

Where Emona MFT fits

• Branches and servers to one hubFiles dropped into a folder at a branch, on a server or by a partner are picked up automatically and delivered to your central server, into a separate directory per client.
• Replacing FTP and SFTP scriptsA modern replacement for fragile FTP/SFTP scripts. The client waits until a file has stopped changing, retries with backoff and deletes the original only after a verified delivery.
• Scheduled jobs and cronRun the client once from cron or another scheduler, with clear exit codes. Masks such as *.csv or report_??.txt and a send order (oldest, smallest or by name) decide what goes and when.
• Exports from business systemsERP and other systems that write export files into a folder can hand them over without custom integration code. A name clash gets a numbered name by default, or you choose overwrite, append or reject.
• Partner file exchangePartners send to a server you control, each with its own client key and storage directory. Unknown client labels and file names containing paths are rejected.
• Monitored transfersEvery Emona MFT installation includes at least one web dashboard instance, and all licensed servers connect to it, so you see your transfers in one place.

Security, honestly

Every file gets a SHA-256 hash, is GZIP-compressed and encrypted with a key unique to its client. In Emona MFT, protocol 2 (the default) authenticates client and server before any file data is sent, encrypts file names and content with AES-256-GCM and prevents replayed transfers. The product is self-hosted: files go from your clients to your own server, never to BLUEGEM or a cloud service.

Limits: the free jFiltra core does not encrypt the connection, so run it only inside a trusted network, a VPN or an SSH tunnel, and never expose its port to the internet. Emona MFT does not use TLS either. With protocol 2 an observer can still see client labels, approximate file sizes and timing, and a VPN or SSH tunnel hides those too. Emona MFT focuses on one job: moving files between your own sites and systems. It is not a replacement for an enterprise suite with many protocols. Details are on emonamft.com/security.

How BLUEGEM helps

We build the network underneath: site-to-site VPNs and firewalls for the transfer port, Linux servers for the central hub, and integration of legacy systems that exchange files. Emona MFT needs Java 8 or newer (Java 21 or 25 LTS recommended) and Apache Log4j 2, and runs on Linux, macOS or Windows. Installation is included with Emona MFT, and current versions, pricing and pre-orders are on emonamft.com/pricing.

See Emona MFT pricing and details Try the free jFiltra core

Frequently asked questions