New Passkeys, OpenID Connect sign-in, and two-factor protection by default. See what is new

Use case

Replace your FTP server

An FTP replacement moves files between you and other people, without an FTP client.
FileRun does it on the same server and the same folders.

What most organizations use today

FTP and SFTP

FTP sends the password and the files unencrypted. SFTP corrects that, and keeps every other problem.
Each person needs a client program and instructions, a password is the only protection, and the record of who took which file is a text file that nobody reads.

A free transfer website

People avoid FTP. They send the files through a free transfer website or a private cloud account instead.
The company's files leave the company, and nobody knows where they went.

What makes FileRun an FTP replacement

Every item below is a standard feature, included in every plan.

For the people who use it

  • A web browser is enough. There is no client to install and no connection settings to explain.
  • Drag files and folders into the browser. FileRun streams them, so there is no size limit, and an interrupted transfer resumes from where it stopped.
  • Upload a folder with tens of thousands of files. When you upload it again, only the new and the changed files are sent.
  • Send a link to somebody with no account, with a password, an expiry date or a download limit.
  • An upload-only link replaces the anonymous FTP folder. People add files, but cannot open or download what is already there.
  • Anybody who prefers a client keeps one. Standard WebDAV works with WinSCP, Cyberduck, rclone, Windows Explorer and Mac Finder.

For the administrator

  • Everything goes over HTTPS, on the one port that every firewall already allows. There are no passive port ranges to open.
  • A second factor is on by default, and passkeys are supported. An account can be limited to certain IP addresses.
  • After a failed sign-in, the next attempt is slower, so a password cannot be guessed by trying thousands of them.
  • Seven roles decide what each person may do in each folder. They do not depend on the permissions of the operating system.
  • Storage and traffic quotas, a maximum upload size, allowed file types, and an end date for each account.
  • Every transfer is recorded with the user, the IP address and the program that made it. Transfers that failed are recorded too, with the reason.

Nothing has to move

The folders you already have

Each FileRun account is given a folder that already exists on the server.
Point it at the folders your FTP server uses now. Files are never stored in the database, and nothing is imported.

Keep FTP, or move at your own speed

FileRun and the FTP server can work on the same folders at the same time, for as long as you want.
A file uploaded in the browser can be downloaded over FTP, and a file that arrives over FTP appears in FileRun. Move people across one at a time, or keep both.

Scripts keep working

An automatic job that sent files over FTP can send them over WebDAV, with rclone or curl, or through the REST API.
Each job gets its own named password, which you can revoke without changing anything else.

What FileRun does not do

It does not speak FTP or SFTP

A scanner, a camera or an old machine that can send files only over FTP still needs an FTP server.

What to do about such a device

Let that FTP server write into a folder that FileRun also uses.
The files then appear in FileRun for everybody else.

Common questions

Is there a limit on the size of a file?

No. FileRun streams each file to the server instead of cutting it into pieces, so there is no limit to raise in the server configuration. An administrator can set a maximum upload size for an account on purpose.

Can external partners upload without an account?

Yes. Create a link on a folder and give it the Uploader role. Anybody who has the link can add files. They cannot open or download the files that are already in the folder.

Do files that arrive over FTP appear in FileRun?

Yes. A file that was placed on the server without FileRun is indexed when its folder is next opened. It can then be previewed, shared and searched like any other file. The other direction works too: a file uploaded in FileRun is an ordinary file in the folder, and an FTP client can download it or replace it.

Which server does FileRun need?

A Linux or a Windows server with PHP and MySQL, or Docker. It also runs on a NAS and on shared hosting. With Docker the installation takes about one minute.

Run it next to your FTP server

Put FileRun on the same server with a free trial license, and point it at one of your FTP folders.
Or open the live demo, where you are signed in as the administrator with no sign-up.

Other uses: a client portal and document management.