Windows
Windows is the primary desktop target. The transfer engine, interface quality, security and stability are the current priorities.
Active developmentThe roadmap uses development stages rather than artificial completion percentages. A platform moves forward when security, transfers, installation and core usability are stable enough for the next phase.
The roadmap uses development stages rather than artificial completion percentages. A platform moves forward when security, transfers, installation and core usability are stable enough for the next phase.
Windows is the primary desktop target. The transfer engine, interface quality, security and stability are the current priorities.
Active developmentPorting and compatibility work are focused on reliable behaviour across supported Linux distributions.
Early phasemacOS, Android, iOS and a web version are planned once the desktop core is sufficiently mature.
Development planThe goal is not to publish a build simply because it launches. Ghost FTP is being developed around a small set of release principles that make everyday server work safer and easier to understand.
Protocol security, clear connection state and careful credential handling are treated as core product concerns.
Progress, queue state, failures and retries should be understandable instead of hidden behind vague activity indicators.
Connection and transfer failures should surface actionable information that helps identify what went wrong.
Core file-transfer work is being designed without hidden telemetry or a mandatory cloud account.
Ghost FTP is still in active development. Windows is the primary desktop target, while Linux compatibility work is also under way. The roadmap is an indicator of progress, not a release-date promise.
Yes. SFTP, FTPS and FTP are the core protocol targets shown on the current roadmap, with SFTP providing encrypted file transfer over SSH.
The public website uses no analytics or telemetry scripts. The product is also being designed around a no-hidden-tracking principle, with core file-transfer settings intended to remain under the user’s control.
Linux is in an earlier testing and compatibility phase. macOS, Android, iOS and a web version are planned after the desktop core is sufficiently mature.
The core file-transfer workflow is being designed without a mandatory account. If future online services introduce separate account requirements, those requirements will be documented explicitly.