// the take
Palmr is a self-hosted file-sharing service (Fastify API + Next.js frontend, SQLite by default) aimed at teams who want a WeTransfer-style share-and-expire flow without a third party in the loop. As of this writing the project is archived by its sole maintainer, so this is a snapshot of a dead-end rather than something to adopt going forward.
Solid, boring stack choices — SQLite plus filesystem storage means zero-config self-hosting, with S3-compatible storage as an opt-in for scale. OIDC support is unusually thorough for a project this size, with working docs for Auth0, Google, Discord, Authentik, Zitadel, and generic providers. Fastify's schema validation is a good fit for an API that's mostly file-upload plumbing, and password-protected/expiring links plus reverse (upload-to-me) shares cover the two use cases people actually want from this category of tool.
It's archived — no security patches, no bug fixes, no path forward except a hypothetical fork nobody has claimed yet. It never left beta before being shelved, and the README says so explicitly: not recommended for production. Single maintainer with no succession plan is the actual root cause here, not a technical flaw, but it means anyone running this in production today is on their own for CVEs in Fastify/Next.js dependencies going forward. No mention of test coverage or CI beyond a pre-push hook, so fork maintainers inherit an unknown quality bar.
We read the README, the directory tree and a key source file in September 2026. Nobody pays to be listed. How we judge →