← All posts

Three Weeks After Launch

v0.2.0 shipped three weeks ago. Here's what happened next.

Hardening what shipped

Before adding anything new, we stress-tested what was already out there. Seven automated UAT passes caught 11 bugs: auth middleware mismatches, mobile overflow, React crashes on undefined data. All fixed before anyone reported them.

The kind of bugs you only find by running the full system end-to-end, not unit tests. Billing pages returning 401 because the wrong auth middleware was applied. Queue pages crashing because a transfer status was undefined and the filter function choked. Mobile navigation overflowing at 375px because three nav items didn't fit.

Each pass found progressively fewer issues. Pass 7 was clean.

We also shipped Polar.sh billing integration (subscription management directly in the dashboard), configurable rate limiting (admins can now tune API limits per tier), and standardized the brand across every surface. Logo, favicon, colors, all consistent now.

Network discovery

This is the big one.

mft-discover is a standalone CLI tool that scans your enterprise network for file transfers you didn't know about. The ones running in cron jobs, scheduled tasks, shell scripts, and saved FTP client configs. The shadow IT of file transfer.

How it works:

  • Passive scanning only — reads local configs and crontabs, no network probing
  • Cross-platform — SSH into Linux machines, WinRM into Windows machines, auto-detects the OS
  • Risk flagging — every finding is analyzed for hardcoded credentials, unencrypted protocols, missing retry logic, no audit logging
  • Dual output — JSON for automation pipelines, styled HTML for executive review
  • Dashboard upload — scan results can be imported directly into the MFTPlus dashboard for filtering, dismissing false positives, and importing findings as transfer jobs

What it finds: SFTP, FTP, FTPS, SCP, Rsync, HTTP, HTTPS, SMB transfers across crontabs, shell scripts, batch files, PowerShell, Windows Task Scheduler, FileZilla configs, WinSCP configs, and PuTTY sessions.

The output report is both a security audit and a migration planning tool. "You have 14 unencrypted transfers, 3 with hardcoded credentials" is a finding that drives action, whether that's consolidating into MFTPlus or just fixing the security gaps.

Built in Rust, cross-compiled for Linux and Windows in CI, released alongside the agent binaries.

Full docs: Network Discovery documentation

What's next

Two things on the immediate roadmap:

Transfer triggers. Event-driven transfers: file appears in a directory, auto-transfer fires. The number one ask from enterprise teams. Currently transfers are either scheduled (cron) or on-demand (CLI/API). Triggers add the third mode: reactive, real-time, zero-touch.

Smart retry with resume. Breakpoint resume for interrupted transfers. Today a failed transfer retries from the start. With resume, it picks up where it left off. For large files on unreliable networks, this is the difference between "transfer eventually succeeds" and "transfer keeps failing at 80%."

Both are in design. Both will ship when they're ready, not before.

The pace hasn't slowed since launch. If anything, it's accelerated. We have a real product now, and every new feature builds on something that already works.

A
Armin Marxer

Building MFTPlus. Spent years managing file transfer infrastructure before deciding there had to be a better way.

FAQ

What is mft-discover and how does it work?

mft-discover is a standalone CLI tool that passively scans your network for file transfers. It reads cron jobs, scheduled tasks, shell scripts, and FTP client configurations across Linux and Windows machines via SSH and WinRM. It does not probe the network or send data externally.

Is the network discovery tool free to use?

Yes. mft-discover is a free, standalone tool. You don't need an MFTPlus account to download and run it. Scan results can optionally be uploaded to the MFTPlus dashboard for guided remediation.

What protocols and tools does mft-discover detect?

It detects SFTP, FTP, FTPS, SCP, Rsync, HTTP, HTTPS, and SMB transfers configured in crontabs, shell scripts, batch files, PowerShell scripts, Windows Task Scheduler, FileZilla, WinSCP, and PuTTY configurations.

What are transfer triggers?

Transfer triggers are event-driven transfers. Instead of running on a schedule, a trigger watches a directory and automatically starts a transfer when a file appears. This is useful for real-time data pipelines where files arrive unpredictably.

When will smart retry with resume be available?

Smart retry with breakpoint resume is currently in design. It will allow interrupted transfers to resume from where they stopped, rather than restarting from the beginning. No ship date yet — it will be released when it's ready.

Find the transfers you don't know about

Network Discovery docs →