FileRun — Self-hosted File Sync and Share

Authentication

Everybody already has an account somewhere. FileRun signs them in against the directory you already run — no second set of passwords to administer.
Use an existing plugin, or write your own.

Ready-made plugins

LDAP
Active Directory
SAML, ADFS and Shibboleth
Microsoft Azure
OAuth2
Authentik
WordPress
Google
Dropbox and Box

On a Windows domain

With Integrated Authentication, users who are already signed in to Windows are signed in to FileRun automatically. They type nothing.

Branding

Your users should see your company, not ours.
Start from a ready-made theme or create your own, and your users see only your brand:

Logos on the login page and throughout the interface.
Your own colors, in both light and dark mode.
Links to your privacy policy and terms of use.
Square or rounded corners throughout.
Welcome messages.

In 35 languages

FileRun is fully translated into 35 languages. You can also change any word in the interface to the one your organization uses.

FileRun's theme editor, showing the color presets and per-mode palette

Client apps under your own name

Give your users desktop and mobile apps with your own branding.
Compatible open-source clients already exist for Mac, Windows, Linux, iOS and Android,
so you have very little left to build.

The same app published under a customer's teal Nordi branding

The same app published under a customer's orange ACME branding

The same app published under a customer's red Vela branding

A complete API

Everything the web interface does, your own software can do as well. FileRun has a REST API that covers the whole product, not a handful of endpoints added afterwards.

Building on it

A full REST API, described in OpenAPI, so you can generate a client for whichever language you work in.
OAuth2, with tokens you can limit to only what the program needs.
A PHP client library, if that is what you write in.

Connecting it to your own systems

Create, change and remove user accounts from your own software, so your joiners and leavers process stays where it already is.
The API uses the same permission checks as the web interface. What a user cannot do in the browser, they cannot do through the API.
It can be turned off on its own, separately from web, WebDAV, desktop and mobile.

Fits how you already work

Authentication

Branding

Client apps under your own name

A complete API

Point it at what you already run

Product

Buying

Resources

Company