Power your agent
पब्लिशर का इंस्टॉल। PlugMCP एंडपॉइंट नहीं।
Host a copy with our keys and logs.
रजिस्ट्री में अभी कोई पैकेज्ड रिलीज़ नहीं है। रिपॉज़िटरी का README देखें.
रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है
PlugMCP पर चलाएँ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
लॉन्चपब्लिशर से
Self-hosted file manager & sharing with a web UI, in one Go binary - open-source alternative to Nextcloud, Dropbox and Google Drive. Web-based file browser for local, S3, SFTP, WebDAV, FTP and SMB storage: private cloud served as S3, SFTP, NFS, WebDAV. SSO/LDAP, multi-tenant, encrypted folders, embeddable web component, desktop app, MCP server.
Self-hosted file manager & sharing with a web UI, in one Go binary - open-source alternative to Nextcloud, Dropbox and Google Drive. Web-based file browser for local, S3, SFTP, WebDAV, FTP and SMB storage: private cloud served as S3, SFTP, NFS, WebDAV. SSO/LDAP, multi-tenant, encrypted folders, embeddable web component, desktop app, MCP server.
🗂️ Every storage, one tree
Mount what you already have side by side, and copy or cut in one storage and paste in another. Point rclone, restic, WinSCP or FileZilla at the same tree.
🔗 Share and protect
Links with a PIN, an expiry and a download limit. Trash, version history and end-to-end encrypted folders.
🔑 Your accounts, your roles
OIDC, LDAP / Active Directory or the Windows and Linux accounts of the server. Roles, groups, multi-tenant.
💻 A desktop app with live folder sync
Windows, Linux and macOS (Apple Silicon): an edit on either side arrives in about a second.
🧩 Embeds in your product
The same UI as a Vue 3 component, a React component and a <filex-explorer> web component.
🤖 Apps and AI agents
Sandboxed apps - e-Signature, Convert, draw.io - a built-in MCP server an agent can drive, and an AI assistant in the explorer that can run fully local.
[!TIP] Look before you install: demo.filex.sh - sign in with
[email protected]/demo(admin role, sandbox resets nightly).
Run your own, from the folder you want to serve:
docker run -p 5212:5212 \
-e FILEX_DEFAULT_STORAGE_DRIVER=local -e FILEX_DEFAULT_STORAGE_PATH=/srv/files \
-v filex-data:/data -v "$PWD:/srv/files" \
ghcr.io/brf-tech/filex:latest
Open http://localhost:5212/admin - the first run prints admin credentials and embed instructions to the console. That URL is the operator's; the people you give accounts to get http://localhost:5212/drive, the same file manager without the panel around it. For Word, Excel and PowerPoint, install the office editor app from Admin → Plugins → Apps: it edits them in the browser and needs no other container.
That serves the folder you ran it in - open the UI and your files are already
there. /data is filex's own directory (SQLite database, search index, thumbnail cache),
which is why it is a named volume and not the folder you drop files into; the two are
separate on purpose. Point $PWD somewhere else, or add more storages from the admin
panel later - a bucket with several top-level folders can be mounted as one storage
per folder in one go (Storages → Add storage → Mount several folders at once).
The container runs as root by default, so what it writes into /data is root-owned;
set PUID/PGID to run it as yourself
(docs/DOCKER.md).
Download the archive for your platform from the latest release, extract it and run the binary (docs/INSTALLATION.md):
# Download from https://github.com/BRF-Tech/filex/releases
./filex serve
═══════════════════════════════════════════════════════════════
filex · self-hosted file manager
═══════════════════════════════════════════════════════════════
Listening on: http://0.0.0.0:5212
Admin UI: http://0.0.0.0:5212/admin
Files UI: http://0.0.0.0:5212/drive
Embed JS: http://0.0.0.0:5212/embed.js
First run detected. Initial admin user created:
Email: admin@local
Password: <printed once>
Saved to: ~/.filex/.first-run.txt (mode 0600, shown ONCE)
Change at: /admin/dashboard?settings=1
═══════════════════════════════════════════════════════════════
For a real deployment there are Compose stacks and a Helm chart: Self-host with Compose or Helm. The image is on GitHub Packages.
Most self-hosted file managers are either too small (a directory listing with uploads) or too big (a groupware suite you deploy for the file tab). filex aims at the gap. The tour below has eight parts, each with its screenshots folded under it. Every feature in full, with its limits and the guide that documents it, is in docs/FEATURES.md.
A file manager people already know how to use.
Every explorer feature in full: docs/FEATURES.md → The explorer.
The shell - what everybody lands on
Searching this folder; ⌘K / Ctrl K hands the query to the palette
Navigation panel - Home, Shared with me, My shares, Recent, Starred, Trash, and the storages you can reach
Collapsed to the icon rail
Tags - your own, or your team's; a tag opens every file carrying it, from every folder they live in
Trash - what was deleted, where it came from, and how long is left before it goes
The bell - the unread count on it, every row going where it says
All of your notifications, inside the explorer - for everybody, not only administrators
Appearance - compose a theme in your own colours, previewed as you type
Made the default, it is what everybody's explorer wears…
…and the sign-in page, before anybody has signed in
A symlink filex will not follow says so - in the listing, and in words in its details
A .csv opens in ONLYOFFICE's spreadsheet when one is connected - a look first, and no delimiter dialog: the file's own separator is passed along (CSV files)
…and its editor, which says what a save as CSV keeps; the file goes back as the same kind of CSV, and the cells nobody changed keep their text - 007 stays 007 (cells nobody changed)
Every storage in one tree, and that tree reachable from anything.
rclone,
restic, aws s3, WinSCP or FileZilla at it. The same filex permissions (per person, group
and folder), trash and quota apply as in the web UI; the POSIX bits and ACLs on the disk are
not mapped to filex users.filex mount attaches a remote server over ordinary HTTPS: a folder on Linux, a drive
letter on Windows (macOS is not supported).Every storage and protocol feature in full: docs/FEATURES.md → Storage and protocols.
Connections - the guides, built from your deployment
API keys - mint your own, in the explorer or in an embed (a person's session or token; an embed proxied with one shared app token does not get this entry)
Reaching filex from anything - S3, SFTP, FTPS, NFS, WebDAV. Every command is built from your deployment
A storage filex does not ship - installed as a plugin on Plugins → Storage plugins, describing its own config form
Share with a link you can limit and revoke. Take back a wrong delete or a wrong overwrite.
Every sharing and protection feature in full: docs/FEATURES.md → Sharing and protection.
Sharing - PIN, expiry, download limit, one-line curl
Markdown viewer
…and what the person at the other end opens. filex has ONE outward-facing screen - a shared file, a folder, a file request, an app's signing page and the PIN in front of any of them are all this page, in your instance's name
My shares - the links you created, and their PINs when you need to pass one on
Every admin table - one pinned Actions menu per row, the same menu the explorer's ⋮ opens
Who may encrypt - off, administrators only, everyone whose role allows it, or after an administrator's approval; the requests waiting, with who asked and why (who may encrypt)
…and the person's side: the request the New folder dialog opens - one new encrypted folder, asked of an administrator with a reason
The accounts people already have, and one role each.
Every feature for people and access in full: docs/FEATURES.md → People and access.
Roles - Administrator, User, Viewer and roles of your own: who holds each, what it allows, where it differs by folder, its limits (docs/PERMISSIONS.md)
Groups - named sets of people with folder access and a role; members by hand or kept in step with the groups a sign-in carries (docs/GROUPS.md)
Sharing a folder with a group, beside people - Owner is asked for in the dialog, not granted by a click
Sign-in security - the attempt limit and the addresses it never counts; trusted proxies, the locks and the sign-in trail follow on the same page (sign-in attempt limits)
…and what a locked account's sign-in form says, counting the lock down on its button
Admin panel
Demo landing
The admin menu - every page in four panels, Files & storage, People, Settings (General, Security & data, File processing & integrations) and Maintenance & records, with a short line under each; a phone gets the same pages in a drawer (docs/ADMIN-PANEL.md)
Folders on your computer stay in step with the server, live.
filex sync and filex client.Install it from the Microsoft Store (Windows 10/11) or the Snap Store (Ubuntu and other Linux with snapd):
or with a package manager:
brew install brf-tech/filex/filex-app # macOS 13+ (Apple Silicon), Homebrew tap BRF-Tech/homebrew-filex
sudo snap install filex-app # the same snap as the badge above
The Store build (filex File Manager) is the one Windows copy that is code-signed -
Microsoft signs it - and the Store keeps it up to date. The desktop app's winget package
(BRFTech.filex-app) is waiting for its first review by the winget moderators - until it is
accepted a release leaves the submission as it is - so winget install BRFTech.filex-app
does not find it yet.
Installer, portable .exe, AppImage, .deb, .rpm and .dmg are attached to the
latest release - not code-signed yet,
so expect a SmartScreen prompt from the Windows installer. Details:
docs/DESKTOP.md. The CLI alone: brew install brf-tech/filex/filex,
or winget install BRFTech.filex on Windows (docs/CLI.md).
On Linux the .deb and .rpm need nothing; on Ubuntu 23.10 and later an AppImage needs a
one-time AppArmor profile (AppImage on recent Ubuntu),
and the Snap runs inside the snap's strict confinement
(The snap and the sandbox). Every release builds
for arm64 too: the server, the images, and the desktop app on Linux, Windows on Arm and Apple
Silicon (docs/INSTALLATION.md → ARM (arm64)). Everything the
app does: docs/FEATURES.md → Desktop app, phone and CLI.
The same binary is also a client for servers, scripts and headless machines:
filex client login --url https://files.example.com
filex client upload build/report.pdf docs://ci-artifacts/
filex client mv docs://ci-artifacts/report.pdf archive://2026/ # across storages, waits for the job
filex client run convert convert docs://data/table.csv --param target=xlsx
filex sync add ~/Documents/work docs://work # the engine the desktop app uses
filex sync run --watch 30s
See docs/CLI.md and docs/SYNC.md.
A real file manager inside your own product.
The same UI ships as a Vue 3 component, a React component and a framework-agnostic
<filex-explorer> web component, backed by your own filex server. A confined token locks it
to a per-tenant folder, and the backend enforces that, not the widget. The web component
takes two lines:
<script type="module" src="https://cdn.jsdelivr.net/npm/@brftech/filex/dist/filex.js"></script>
<filex-explorer api-base="http://localhost:5212" sidenav connections ui-profile="simple"></filex-explorer>
pnpm add @brftech/filex-core
<script setup>
import { FileExplorer } from '@brftech/filex-core';
import '@brftech/filex-core/style.css';
</script>
<template>
<FileExplorer :config="{ apiBase: 'http://localhost:5212', auth: { kind: 'bearer', token: '…' } }" />
</template>
pnpm add @brftech/filex-react
import { FileManager } from '@brftech/filex-react';
<FileManager config={{ apiBase: 'http://localhost:5212' }} onError={(e) => console.error(e)} />
Styles, bundlers, the sidenav / connections / ui-profile attributes, the language an
embed speaks (its visitor's, with a Language setting of its own), confined tokens
for multi-tenant hosts, a session cookie from another origin and printing from an app:
docs/INTEGRATION.md, summed up in
docs/FEATURES.md → Embedding. ⚠ Keep the packages and the
server on one version (docs/API.md).
Shared with me - folders other people granted you, no mount instructions
Embedded in another product's page
New things to do with files, with exactly the permissions you approved.
An app is a WebAssembly module that runs inside filex in a sandbox, an interface of its own in a sandboxed frame, or both. You install it from a store link or its GitHub address, read every permission it asks for, and nothing updates itself. The people of your filex can browse a trusted store on its App store screen and ask you for an app or a storage plugin. Five ship as public repositories:
An app you allow can edit a file together with other people - filex's relay puts their changes in one order without reading them, and someone who may only read watches live - and can open a file of an encrypted folder, which your browser decrypts for it and encrypts again before it is saved.
A language pack is an app too: Spanish, German and French ship as examples.
Install one in a few minutes: docs/APP-PLUGINS.md → Install one. Every app feature in full: docs/FEATURES.md → Apps.
Dana asks a colleague on the same filex and a partner outside it to sign an agreement. The app is e-Signature; every screen is drawn by filex, and the link the partner gets is an ordinary share.
Define the boxes - name each one and say whose it is; the document comes next
Place them - choose a box, tap the page where it goes
The partner's link - filex's one public screen, in your instance's name, behind a PIN
…and what it opens: only their own boxes - here a name typed in the face the requester chose (drawn and uploaded are the other two)
While it is out - the document frozen for everybody, who has signed in its details
Installing an app - every permission it asks for, in plain words, before anything runs
An installed app - where it came from, its fingerprint, and every permission it holds in plain words (its settings and its actions follow, further down the page)
The converter, another app - every target under its category, three steps
An app that brings its own interface - the review shows the package's fingerprint, every address outside it (a live one is a permission, in yellow) and what a browser cannot promise
…and that interface open on its own file type, where filex's preview would be. It reads and saves the file through filex, in a sandboxed frame (a small example app, written for these pictures)
Editing together - Dana types, and Sam, who may only read, watches every change and her cursor arrive through filex's relay (Editing together; an example app written for these pictures)
A file of an end-to-end encrypted folder in an app you allowed - your browser decrypts it for the app and encrypts the save, and the server still holds only ciphertext (the same example app; Editing in an app)
Every app on the instance, and a language pack among them - a manifest with nothing that runs, which says how much of this filex it translates and leaves with it
Default apps - every kind of file something besides filex handles: who opens it and who draws its thumbnail, in the order you set (Default apps)
Folder previews - each folder drawn with the three files that came into it last; the SVGs are drawn by filex's built-in engine (docs/thumbnails.md)
Installing from a store - the same review, marked From store, the paid app's license key shown by its first characters (Installing from a store)
The first link from a store - its address and the fingerprints of its keys, to compare before you trust it (Trusted stores)
A license the store revoked - the app held, Unlicensed, nothing removed, and a band on every admin page (Paid apps)
An agent works in the folder you gave it, and nowhere else.
/api/ai/mcp, and a REST surface at /api/ai described in an
OpenAPI 3.1 file.claude mcp add filex --transport http https://files.example.com/api/ai/mcp \
--header "Authorization: Bearer <api-token>"
What an agent can do, what a key can never hand out, encrypted folders and upload tickets: docs/FEATURES.md → AI agents and MCP; the reference is docs/MCP.md, and the assistant's is docs/AI-ASSISTANT.md.
filex is a file manager, not a groupware suite. What that means next to four things you may be coming from (File Browser among them):
What filex does not have, whichever of these you come from:
filex-office-editor, ONLYOFFICE's
editor in the browser, no Document Server), or in an ONLYOFFICE Document Server you
connect; with neither they open in a read-only preview (docs/ONLYOFFICE.md).The docker run above is enough to try filex out. For a real deployment,
ready-made stacks live in deploy/:
deploy/compose/ - Docker Compose:
.env. Office documents need none
of them (the office editor app edits them in the browser, and its engine
draws their thumbnails and converts them on the server), and
conversion is the Convert app, not a side-car.deploy/helm/filex/ - a Helm chart for Kubernetes
(Deployment + PVC + optional Ingress), published with every release:
helm repo add brf-tech https://helm.brf.sh, then helm install filex brf-tech/filex
(or oci://ghcr.io/brf-tech/charts/filex). Every add-on above is an enabled
toggle in values.yaml - bundle PostgreSQL / Redis / an S3 server, or wire an
external ONLYOFFICE Document Server / Drawio.Step-by-step instructions for each tier are in
docs/INSTALLATION.md. To try what the next release brings,
there is a nightly build of every change that passed the nightly tests -
ghcr.io/brf-tech/filex:nightly, the desktop app on filex.sh/nightly and the Snap Store's edge channel -
not supported, and not for the data you keep
(docs/INSTALLATION.md → Nightly builds).
filex runs at the root of a host of its own or under a path of one it shares
(https://example.com/filex/): one setting, FILEX_BASE_PATH, and a proxy
that passes the full path - Caddy, nginx and Helm examples in
docs/DEPLOYMENT.md → Serving filex under a sub-path.
The guides are published as a site at docs.filex.sh, and the full documentation index lists every page.
Start with Installation, Configuration, the desktop app, protocols, apps and ONLYOFFICE. Features gives every feature an entry with its limits and its guide.
Every feature as its own entry - how it behaves, its limits and the page that documents it: docs/FEATURES.md.
See docs/ARCHITECTURE.md.
┌─────────────────────────────────────────────────────────────┐
│ filex (Go binary; image ~62 MB slim / ~241 MB full) │
├─────────────────────────────────────────────────────────────┤
│ HTTP API (chi) │ Admin UI (Vue 3, embedded) │
│ Auth Drivers: │ local · oidc · ldap · proxy-header │
│ │ pam · windows (OS accounts) │
│ Sign-in guard: │ attempt limits · IP allow-list · realms │
│ Storage Drivers:│ local · s3 · ftp · sftp · webdav · smb │
│ Served as: │ s3 · sftp · ftps · nfs · webdav │
│ DB Drivers: │ sqlite (default) · mysql · postgres │
│ Queue Drivers: │ follows the DB · redis │
│ Realtime: │ WebSocket presence + live updates │
│ RBAC: │ roles + groups + grants + share invites │
│ AI / MCP: │ /api/ai REST + native MCP server │
│ Sync Worker: │ etag / size+mtime diff + tombstone │
│ Replica Layer: │ primary→replica + rules + reconcile │
│ Protection: │ trash + versions + ClamAV (bin/clamd) │
│ E2E folders: │ client-side WebCrypto (server blind) │
│ Co-editing: │ sealed relay for apps · watchers │
│ Notifications: │ webhook + in-app bell + read/unread │
│ Search: │ Bleve (full-text, embedded) │
│ Thumbnails: │ image · svg · video · pdf · office │
│ │ heic · text · zip · folders · apps │
│ Plug & Play: │ OnlyOffice · Drawio · Mermaid │
│ Apps (wasm): │ sandboxed · e-Signature · Convert │
│ Languages: │ en · tr + language packs · RTL layout │
│ Appearance: │ operator themes · instance default │
└─────────────────────────────────────────────────────────────┘
▲
│ HTTP API
┌──────────────────┼──────────────────┐
│ │ │
@brftech/ @brftech/ @brftech/
filex-core filex filex-react
(Vue 3 SFC) (Web Component) (React adapter)
│ │ │
▼ ▼ ▼
Vue 3 apps Any framework React apps
(vanilla, Angular,
Svelte, Solid, …)
Same API, no server plugins: desktop app (Electron, Windows/Linux/macOS)
CLI client (filex client · filex sync)
filex has one maintainer, who builds it with AI coding agents (Claude Code). The maintainer
decides what filex is and how it works: the architecture, the data and security models, and
how each feature behaves. The agents write most of the code inside that direction, in
languages the maintainer works in. About 82% of the commits in the development repository
carry a Co-Authored-By: Claude line, so this is not hidden.
It is AI-assisted, not unreviewed generated code:
Issues and pull requests are welcome; before a sizeable pull request, open an issue that
says what you are about to do. docs/CONTRIBUTING.md has the
workflow, the tests a change has to pass and the documentation rules, and the project follows
the Contributor Covenant. A security problem is reported privately, as
SECURITY.md describes. What changed in each release is in
CHANGELOG.md. A release is cut every day at 10:00 Istanbul time from what
main holds then, when it holds something new; a pull request merged after the cut ships
with the next day's (Release process).
git clone https://github.com/BRF-Tech/filex.git
cd filex
pnpm install
pnpm run build:all # builds packages, web, then Go binary
./bin/filex serve
Subdirectories:
backend/ - Go HTTP service (cmd/filex, internal/*, db/queries, db/migrations)packages/core - @brftech/filex-core (Vue 3 SFC, source of truth)packages/webcomponent - @brftech/filex (Web Component wrapper)packages/react - @brftech/filex-react (React adapter via @lit/react)web/ - Vue 3 admin UI (embedded into Go binary via go:embed)desktop/ - Electron app (bundled main process, tray sync, auto-update)demo/ - Standalone HTML demos for each frameworke2e/ - Playwright suites (web, embeds, packaged desktop app) + shots/, the
scripts pnpm shots runs to take the screenshots above (published on filex.sh,
not kept in the repository)docker/ - Dockerfiles + composedeploy/ - ready-made Compose stacks + Helm chart (see deploy/)docs/ - Markdown documentationdocs-site/ - VitePress site published at docs.filex.shMIT - see LICENSE.
The store badges in docs/badges/ are the stores' own artwork, used
unmodified and not covered by that licence: Microsoft and the Microsoft Store badge are
trademarks of the Microsoft group of companies; the Snap Store badge is © Canonical Ltd.,
licensed CC BY-ND 2.0 UK.
Nextcloud, Dropbox, Google Drive, File Browser and ONLYOFFICE are the names of other parties' products, used here only to describe them. filex is not affiliated with, sponsored by or endorsed by any of them.
Self-hosted file manager & sharing with a web UI, in one Go binary - open-source alternative to Nextcloud, Dropbox and Google Drive. Web-based file browser for local, S3, SFTP, WebDAV, FTP and SMB sto
ओवरव्यू
Self-hosted file manager & sharing with a web UI, in one Go binary - open-source alternative to Nextcloud, Dropbox and Google Drive. Web-based file browser for local, S3, SFTP, WebDAV, FTP and SMB storage: private cloud served as S3, SFTP, NFS, WebDAV. SSO/LDAP, multi-tenant, encrypted folders, embeddable web component, desktop app, MCP server.
टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
Filex stdio पर लोकल चलता है।
पिछली जाँच 2026-10-27 को हुई। Self-hosted file manager & sharing with a web UI, in one Go binary - open-source alternative to Nextcloud, Dropbox and Google Drive. Web-based file browser for local, S3, SFTP, WebDAV, FTP and SMB storage: private cloud served as S3, SFTP, NFS, WebDAV. SSO/LDAP, multi-tenant, encrypted folders, embeddable web component, desktop app, MCP server.