HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
mickael-kerjean
filestash
Go2017–2026
mickael-kerjean / filestash

filestash

:file_folder: Universal File Management Platform (for humans and agents)

15Distinct people
138Mentions
1Explicit recommenders
14.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

:file_folder: Universal File Management Platform (for humans and agents)

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

If you are not ready to trust a vibe-coded app with all your digital life, I recommend Filestash[1], easy to install self-hosted frontend for virtually any type of storage.…

SergeAx used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 5:04:15 PM UTC.

Google Gemini routes personal Drive files and emails to human annotators direct repository linkCritical

The discussion centers on Google's practice of routing personal data from Consumer Gemini's connected apps to human annotators for model improvement, a policy that users find deeply invasive and deceptive. Critics argue this erodes privacy, confuses enterprise customers who believe their data is secure, and reinforces the need to migrate away from Google's ecosystem.

148 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4

Mentions over time

HN mentions by year138 dated mentions

Observed mentions: 2017-08-24 00:38:02 UTC to 2026-09-29 03:57:30 UTC.

0102030402017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 14 mentions; 4 submissions, 10 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 12 mentions; 0 submissions, 12 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 14 mentions; 0 submissions, 14 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 11 mentions; 1 submissions, 10 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 26 mentions; 0 submissions, 26 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 39 mentions; 0 submissions, 39 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC110
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC14410
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC12012
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC716
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC505
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC909
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC14014
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC11110
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC26026
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC39039

What Hacker News says

26 sources
I launched Filestash [1] as my response to the infamous “Dropbox should just be FTP” comment. Once I had a decent FTP experience, I kept going: adding support for pretty much every storage protocol, plugins to expose Dropbox (or anything else) over FTP, SFTP, MCP, or S3, and all the features I wished Dropbox had, with plugins to customize everything. The base product is open-source and I make money from custom builds, additional plugins, paid support, and the occasional extra feature for companies with specific needs. It's a bit more than noodle profitable but quite under a normal salary. [1] https://github.com/mickael-kerjean/filestash
In Ask HN: Those making $500/month on side projects in 2025 – Show and tell
This is not as simple as it sounds. Just yesterday I had a call with the Delft university of technology in Netherland, they want me to add some features on the free version of my FOSS product [1] but they did not want to pay anything. Over the last month, I was in contact with a 800B publicly traded company for a 1.8k per year invoice, once we agreed on the general direction they kept adding expectations, first was to sign tons of paperwork with their security checklist, legal stuff which took a few days but when they start asking for things that would take potentially weeks more, I invite them to do extras on a contracting basis, since them I have never heard back and of course they never paid a dime. I have literally tons of stories like this from governments to F500. In my bubble the paid support plan mostly work with US entities. [1]:
Read the rest
In What they don't tell you about maintaining an open source project
The frontend of my main OSS work was made is plain es6: https://github.com/mickael-kerjean/filestash The frameworky code is under 100 lines of code, heavily inspired by what I think is a good idea from React: "components are pure function", the simplest example of the about page beeing visible here: https://github.com/mickael-kerjean/filestash/blob/master/pub... Since the whole project was migrated over from React, I was able to improve performance to a degree that would have been impossible using React, it's a breadth of fresh air to open the performance and memory tab and to be able to optimise things from there to get 60FPS no matter what whilst preventing massive ram usage because those frameworks runs all sort of code that is out of your control. Also because there is no build system, I was able to introduce plugins to be able to pa
Read the rest
tch frontend code via patch applied dynamically by the server to create features like the recall button to recall data stored on glacier when using S3, dynamic patching of the icons to apply branding and many other things that I would have had to fork entirely before Anyway, I hope our industry would go more often the vanilla route, es6 is ready for prime time and solve all the pain point we had while internet explorer was still a thing
In Ask HN: How does one build large front end apps without a framework like React?
> using plain strings, what happens when you do a typo? The tests fails > Will your app will silently break or you’ll have a compile time error? There is no silent error. In practice, there are a couple fail safes: - using both eslint and tsc: https://github.com/mickael-kerjean/filestash/blob/master/pub... - the code is full of runtime assertions: https://github.com/mickael-kerjean/filestash/blob/1d1bad001b... - unhandled error (like most assertion) will interrupt everything to show a scary looking screen: https://github.com/mickael-kerjean/filestash/blob/1d1bad001b... - controlled error which are part of the regular error handling will stop the flow showing a screen like this: https://demo.filestash.app/?error=test
In React is winning by default and slowing innovation
I'm a counter example of your claim. Migrating away from React did made the complexity of my app a lot more manageable and unlocked new business opportunities that would have been impossible with React without following the JIRA route of making the software worse for 99% of users because 1% of those needed something. The project in question is Filestash (https://github.com/mickael-kerjean/filestash), what made me switch are those 2 reasons: - Performance ceiling. Past the point where you have used all the react specific optimisation tricks (useMemo, etc...), React just gets in the way, once you start to optimise things to reduce the memory footprint, optimise for 60FPS, dig into heap snapshots and allocation traces, your life starts to become miserable where you need a complete understanding of not only your app but also the inner working
Read the rest
of React, and the intersection of both React with your app. At that point, you either accept the ceiling or rewrite everything to vanilla JS and have complete control over every piece of the code you are shipping to the client - Extensibility. I am now shipping plugins which patch frontend on the fly without any build step. In practice, after a plugin author packaged their plugin (as a zip file containing a manifest), the patches are applied in real time by the server without a prior frontend build system (open up the demo instance with the network tab open to see this working from: https://demo.filestash.app/). This powers themes with icons swaps, new behaviors (e.g. a "recall" button for files in Glacier), and other things plugin authors come up with that that makes the app far more customizable and opened for new niches without falling onto the JIRA trap
In React is winning by default and slowing innovation
mine does support SSE (https://github.com/mickael-kerjean/filestash) but it fails before getting there, with the log looking like this: 2025/09/11 01:16:13 HTTP 200 GET 0.1ms /.well-known/oauth-authorization-server 2025/09/11 01:16:13 HTTP 200 GET 2.5ms / 2025/09/11 01:16:14 HTTP 404 GET 0.2ms /favicon.svg 2025/09/11 01:16:14 HTTP 404 GET 0.2ms /favicon.png 2025/09/11 01:16:14 HTTP 200 GET 0.2ms /favicon.ico 2025/09/11 01:16:14 HTTP 200 GET 0.1ms /.well-known/oauth-authorization-server 2025/09/11 01:16:15 HTTP 201 POST 0.3ms /mcp/register 2025/09/11 01:16:27 HTTP 200 GET 1.4ms / with the frontend showing: "Error creating connector" and the network call showing: { "detail": "1 validation error for RegisterOAuthClientResponse\n Input should be a valid dictionary or instance of R
Read the rest
egisterOAuthClientResponse [type=model_type, input_value='{\"client_id\":\"ChatGPT.Dd...client_secret_basic\"}\\n', input_type=str]\n For further information visit https://errors.pydantic.dev/2.11/v/model_type" }
In ChatGPT Developer Mode: Full MCP client access
This is exactly what I've been working on with Filestash (https://github.com/mickael-kerjean/filestash). It lets you connect to any kind of storage protocol that possible exist from S3, SFTP, FTS, SMB, NFS, Sharepoint, .... and layers its own fine grained permission control / chroots that integrate through SSO / RBAC so you can enforce access rules around who can do what and where (MCP doc: https://www.filestash.app/docs/api/#mcp)
In ChatGPT Developer Mode: Full MCP client access

Showing the 15 most recent of 26 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.