Roadmap

Customer feature and improvement requests are the main drivers of SFTPPlus MFT development. We work with customers to validate new functionality before making it publicly available.

Release schedule ​

Regular minor releases are based on a rolling update development model at intervals varying between 4 and 6 weeks.

Critical-bugfix releases are made as soon as a defect is fixed, usually within one week after it has been initially discovered and reported.

Security issues have top priority and a fix is released in one or two days.

Features planned for the near future ​

SFTPPlus is under continuous development and we add features with each new release.

The following is a list of features planned for the following releases as updated on 2026-08-31:

  • Allow sharing files over the web interfaces, without requiring an account. [#3933]
  • Add client-side support for pushing and pulling files to Amazon Web Services S3 buckets. [#5375]
  • Add client-side support for pushing and pulling files to Google Cloud Storage buckets.

Bug fixes are prioritized according to severity, including the impact on the production environment or security. The most urgent bug fixes are worked on continuously until fixed and escalated through the support and development team as necessary.

Check all our release announcements in our news section

Development led by customer needs ​

Feature and improvement requests from our customers guide the development of SFTPPlus MFT. We focus on functionality that addresses real file transfer requirements and will be used in production. This approach has resulted in specialized capabilities for specific workflows, including features that are not available in competing managed file transfer products.

From request to public release ​

New functionality is developed and released through four stages:

  1. Proof of concept and demonstration. We create a focused proof of concept in our test environment and demonstrate it to the customer who requested the functionality. This stage validates the expected behavior and helps shape the implementation, documentation, and Web Manager interface. The focus is functional testing, with performance testing included when it is relevant.
  2. Private release and automated testing. Once the proof of concept is agreed, we prepare a private SFTPPlus release containing the new functionality. We also add automated tests to cover its behavior and protect it from regressions in future releases.
  3. Validation in the customer environment. The customer tests the private release in an environment representative of their actual file transfer workflow. Their feedback is used to improve the implementation, documentation, Web Manager experience, and automated tests.
  4. Public release. After the customer validates the private release, the functionality is included in a public SFTPPlus release.

During this process, the customer requesting the functionality is our development partner. We combine our product and file transfer experience with their knowledge of the actual environment and workflow. This collaboration helps ensure that the new functionality works as intended and makes the file transfer process easier and safer.

If you have a file transfer requirement that SFTPPlus MFT does not yet cover, contact us to discuss it.