Filestash

Filestash started as a storage agnostic file manager, a browser front end for whatever your files already sit on, and grew into three products: the web client, a native client that syncs data onto your devices, and gateways that re-expose your storage over other protocols.

One rule shapes the codebase. Anything that is not a fundamental truth of the universe lives in a plugin, which keeps the core lean and the opinions replaceable, so a deep or unusual requirement ends in a plugin instead of a fork.

That choice shows up across the feature set.

• Protocol coverage: FTP, SFTP, S3, SMB, WebDAV, IPFS and roughly twenty more storage backends.
• Gateways: serve the same data over SFTP, S3, FTP, WebDAV, MCP or AS2 for tools that expect a protocol rather than a browser.
• Authentication: pluggable, including a virtual filesystem that delegates login to a WordPress site and derives role-based authorization from its roles.
• Workflow engine: chain actions on file events, from a Slack or email notification to a full managed file transfer pipeline.
• File apps: viewers for raw photography formats, astronomy images, GIS data, Parquet and Arrow, plus LaTeX and PlantUML compilers.

The web client is handwritten vanilla JavaScript, with an API alongside it for programmatic access. The declared goal is to support every storage and authentication technology on the market, which is why the plugin ecosystem, not the core, is where most of the surface area lives.