Alternatives
Products that do what StorForge does
Built for developers and creators.
- 1

- 2CS
We started CallFS after yet another late-night “why did the uploads vanish?” incident. Our small team had stitched together rsync, a fragile NFS mount, and an S3 bucket—none of it observable, all of it waiting to bite us. So we wrote a single-process file service in Go that: • Speaks the S3 API (so existing tooling works). • Stores hot data on local disks for speed; cold data can sit in any S3-compatible bucket. • Exposes Prometheus metrics and JSON logs by default, because “what happened?” shouldn’t be guesswork. • Ships as a ~25 MB static binary—no external deps, MIT license. Today it’s…
2025 · github.com
- 3SL
S2 was on HN for our intro blog post a year ago (https://news.ycombinator.com/item?id=42480105). S2 started out as a serverless API — think S3, but for streams. The idea of streams as a cloud storage primitive resonated with a lot of folks, but not having an open source option was a sticking point for adoption – especially from projects that were themselves open source! So we decided to build it: https://github.com/s2-streamstore/s2 s2-lite is MIT-licensed, written in Rust, and uses SlateDB (https://slatedb.io) as its storage engine. SlateDB is an…
Jan 2026 · github.com
- 4ZA
Jul 2026 · zerofs.net
- 5BI
For the last month or so I've been working on bewCloud, and today I'm making its source code public and open! Right now, the Dashboard (URLs + freeform notes), News (RSS/Atom/JSON feeds), and Contacts (CardDav) are working. If you have any suggestions, comments, or recommendations, I'd love to hear it. Thank you for your attention and kindness. I really appreciate it!
2024 · bewcloud.com
- 6PD
PicoMQ is a Rust server for Durable Streams, built on Object Store. Cheap, URL-addressable, granular streams (create/append/read/long-poll/SSE), with Pico Protocol or Durable Streams Protocol as the facade. S3Stream is the stream storage primitive, used in AutoMQ, shipped as a Rust library. Coordination is a command log in Postgres.
13d ago · picomq.com
- 7ST
2020 · getstowshare.com
- 8AS
Hey everyone, I’m Hunter, the founder of Archil. Archil is transforming object storage, like Amazon S3, into infinite, local file systems that provide instant access to massive data sets. Last year, we launched Archil’s NFS-based product publicly on Hacker News (https://news.ycombinator.com/item?id=42174204), and we were absolutely thrilled to see the response of this community. Since our last launch, we took a 10 month company-wide bet to build our own, custom storage protocol to deliver true, local-like performance to cloud instances – by behaving closer to a block storage…
Sep 2025
- 9

High performance, AI-native objectstore with S3 API included
Nov 2025
- 10SS
May 2026 · github.com
- 11IB
I created a 100% Open source Company-wide Self-hosted File Sharing Solution for Teams Recently, I wanted to share HD images and video files with my graphic designer. She’s exceptional at her craft but isn’t familiar with AWS S3 So, I got an idea and built this. Github Repo: https://github.com/rohitg00/s3-file-share-for-free Detailed Guide: https://ghumare64.medium.com/i-built-a-company-wide-self-hos...
2024 · s3-file-share-for-free-35n2u.kinsta.app
- 12

- 13CM
Hello HN! We’re Dan and Vaughan, based in Cambridge, UK. We recently launched cunoFS, a filesystem for fast, POSIX object storage access. Yes, we’ve heard that “Object Storage is just not suitable for POSIX workloads” or that “workloads should be rewritten to natively support S3”. But what if it could be? And often much faster than S3-native apps? We’ve worked hard to make this possible, without the shortcomings of other approaches. Summary here: - Run (unmodified) applications with S3/AZ/GCP or “S3 compatible” storage, for example: ls s3:// az://…
2024 · cuno.io
- 14OS
2024 · github.com
- 15

- 16

- 17SA
2021 · github.com
- 18

- 19MS
2016 · github.com
- 20ZT
Sep 2025 · github.com
- 21SA
SlateDB is an embedded storage engine built as a log-structured merge-tree. Unlike traditional LSM-tree storage engines, SlateDB writes data to object storage (S3, GCS, ABS, MinIO, Tigris, and so on). Leveraging object storage allows SlateDB to provide bottomless storage capacity, high durability, and easy replication. The trade-off is that object storage has a higher latency and higher API cost than local disk. To mitigate high write API costs (PUTs), SlateDB batches writes. Rather than writing every put() call to object storage, MemTables are flushed periodically to object storage as a…
2024 · github.com
- 22SA
Last night, while trying to figure out the best way to implement caching in my app, I had an idea for a dirt-simple caching system based on a dependency graph. The premise I started with is that one of the hardest things to manage in a cache is dependencies between entities. In order to cache items effectively, you inevitably have to duplicate "child" data inside of "parent" entries. Then, when a child is changed, you have to invalidate the child and its parents, and its parents' parents, and so on. To try to help this, I hacked together a simple Node.js library called Stash, which models…
2012
- 23SV
I've already posted yesterday, but I'd really love to get comments, any kind of questions, suggestions and help would be greatly appreciated as it's an Open Source project of mine (and was for others during my studies at the University of Konstanz 6 years ago). Since then I spent countless ours to bring forth the idea of a versioned storage system, especially well suited for analytical tasks for timd-varying data. Especially I'd love to discuss what documentation you need, which next steps are necessary (JSON, Cloud...), API additions or changes... I've updated the README quiet a bit, such…
2018
- 24GA
2023 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →