compare
LFSX vs Rudolfs
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | LFSX | Rudolfs |
|---|---|---|
| Language | Rust | Rust |
| Licence | MPL-2.0 | MIT |
| Stars | 2 | 525 |
| Latest | v1.23.3 | 0.3.8 |
| Last push | 2026-10-06 | 2026-09-15 |
| Release cadence | about 1 day between releases | too few releases |
| Active contributors | 1+ commit authors on the default branch in the last 90 days | 2 commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
LFSX replaces Rudolfs. Alternatives to Rudolfs →
Full replacementS3 with a local disk cache and encryption at rest like Rudolfs, plus access checked against the forge and file locking.
Both replace GitHub LFS storage. Alternatives to GitHub LFS storage →
Full replacementLFSXThe repository stays on GitHub; only LFS objects move to your own disk or bucket, with access checked against GitHub.
PartialRudolfsThe repository stays on GitHub and LFS objects go to S3 or disk, without client authentication, so it belongs on an internal network.
Both replace lfs-test-server. Alternatives to lfs-test-server →
Full replacementLFSXRust server with S3 and local storage, built for self-hosting.
Full replacementRudolfsCaching server with S3 or local storage.
LFSX
- v1.23.32026-10-03fix(cli): reach /health and /ready above a named forge's prefix in doctor (#519)
- v1.23.22026-10-03fix(server): title a named forge's repository page as acme/game (work) (#517)
- v1.23.12026-10-03fix(dashboard): say a named forge with an empty allow-list serves nothing (#514)
- v1.23.02026-10-03feat(auth): serve repositories from several forges under /-/{forge}/ (#513)
- site@2026.10.52026-10-03feat(auth): serve repositories from several forges under /-/{forge}/ (#513)
Rudolfs
This repository publishes tags, not GitHub releases.
LFSX
✓ signed The latest release, v1.23.3, carries a signature GitHub verified.
Loading the security report
Rudolfs
unsigned The latest release, 0.3.8, carries no signature GitHub could verify.
Loading the security report