English
Filestash Hosting
Browse and manage files across SFTP, S3, and other backends from one clean web interface.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Tech
- Docker image
- machines/filestash:latest
- Default port
- 8334
How Filestash works
Filestash connects to a configured storage backend and presents its folders and files through a web interface. Depending on the selected plugin and protocol, the backend may be an SFTP server, S3-compatible object store, WebDAV endpoint, FTP service, or another supported system. Users authenticate to that backend through the connection method defined by the administrator.
The application can also expose selected data through standard gateway protocols and trigger supported workflows in response to events. Filestash does not create capacity inside an external provider account merely by connecting to it. Backend quotas, permissions, availability, retention, and charges continue to follow the storage service being used.
Key Filestash features
A storage-agnostic interface lets users browse several backend types through a consistent web experience. Supported viewers, sharing options, gateways, workflows, and plugins can extend the basic file-management flow. The value comes from joining an existing storage location to an accessible interface rather than migrating every file into a proprietary drive.
Connection credentials can grant broad access to remote data. They should be scoped to the required paths and operations, stored carefully, and rotated after exposure. Plugin capabilities, identity integrations, workflow actions, and enterprise functions vary, so the hosted page avoids implying that every optional component is bundled.
Who uses Filestash
A small team can provide browser access to an S3 bucket, an administrator can expose selected SFTP directories, and an individual can place a friendlier interface over a compatible WebDAV or FTP service. It also fits organisations that need a temporary gateway between an existing storage system and approved users.
Filestash is not the underlying object store, file server, backup repository, or data-governance programme. It cannot make an unavailable backend reachable or expand the quota assigned by another provider.
Self-hosting Filestash: requirements and cost
Resource use depends on connected backends, directory size, file previews, searches, concurrent transfers, shares, workflows, cache, and local temporary data. The catalogue assigns Filestash no PostgreSQL or MariaDB container. Filestash is storage-driven because hosted cache, previews, or locally handled files can grow even while remote backends retain independent quotas.
AvaHost maps Filestash to Plan 1 at €2. The service includes one-click provisioning, custom-domain HTTPS, automatic application updates, and scheduled backups. When local capacity is important, 50 GB on Plan 3 is a realistic starting point and 100 GB on Plan 4 better suits a larger workload. External storage accounts, backend capacity, transfer fees, provider credentials, and optional enterprise integrations are not included.
F.A.Q
Filestash starts at €2 on Plan 1. Connected backends, directory size, previews, searches, transfers, shares, workflows, cache, and concurrent users affect demand. It is storage-driven: Plan 3 provides 50 GB for a practical local starting point, while Plan 4 provides 100 GB when cached or locally handled data grows.
A custom hostname can serve Filestash with automated HTTPS once DNS points to AvaHost. Configure backend connections only after the final address is known, especially when identity providers or callbacks are involved. After a domain change, verify sign-in, browsing, uploads, downloads, previews, shares, gateways, and every integration that may reference the previous URL.
The plan hosts the Filestash application, not the remote storage it connects to. Users supply compatible S3, SFTP, WebDAV, FTP, or other backend accounts and credentials. Provider quotas, transfer charges, retention, availability, and access policies remain separate. Grant the narrowest permissions required and test with non-critical data before exposing a production store.
Remote backends retain their own quotas, while the AvaHost plan covers the application and any cache, previews, temporary files, or locally handled data in its volumes. Workloads differ by plugin and backend. Monitor both sides: increasing the Filestash plan does not expand an external bucket, and expanding a bucket does not provide more application processing capacity.