#2424th of 102 in Backends, databases and hosting

seaweedfs

Distributed object store and file system with S3 API and Iceberg catalog

Stars
36k
License
Apache-2.0
Last commit
Nov 2026
Last release
Nov 2026
Language
Go
Stars, last 29 weeks+4,639
21 Apr 2026: 31,384 stars28 Apr 2026: 31,629 stars5 May 2026: 31,814 stars12 May 2026: 31,974 stars19 May 2026: 32,122 stars26 May 2026: 32,258 stars2 Jun 2026: 32,426 stars9 Jun 2026: 32,571 stars16 Jun 2026: 32,731 stars23 Jun 2026: 32,887 stars30 Jun 2026: 33,009 stars7 Jul 2026: 33,171 stars14 Jul 2026: 33,307 stars21 Jul 2026: 33,443 stars28 Jul 2026: 33,602 stars4 Aug 2026: 33,739 stars11 Aug 2026: 33,872 stars18 Aug 2026: 33,995 stars25 Aug 2026: 34,148 stars1 Sept 2026: 34,284 stars8 Sept 2026: 34,424 stars15 Sept 2026: 34,626 stars22 Sept 2026: 34,818 stars29 Sept 2026: 35,018 stars6 Oct 2026: 35,216 stars13 Oct 2026: 35,411 stars20 Oct 2026: 35,606 stars27 Oct 2026: 35,759 stars3 Nov 2026: 35,889 stars10 Nov 2026: 36,023 stars

31,384 on 21 Apr 202636,023 on 10 Nov 2026

From GitHub's daily star counts.

Checked on GitHub.

Overview

SeaweedFS is a Go distributed storage system built from master, volume and filer servers. It stores billions of files as blobs in append-only volumes with one disk read per blob, and exposes them through an S3 gateway, FUSE mount, WebDAV, SFTP and HDFS. It also includes an Iceberg REST catalog, S3 Tables, and S3 Vectors backed by a separate vector engine.

Who it is for: Self-hosters and platform teams needing S3-compatible storage at scale

Strengths

  • Master is not in the read path; 16-byte in-memory index per blob, one seek per read
  • `weed mini` starts S3, filer, WebDAV, Iceberg catalog and Admin UI in one process
  • Filer metadata can live in PostgreSQL, MySQL, Redis, Cassandra, TiKV, etcd and others
  • Replication, erasure coding, cloud tiering and cross-cluster replication are built in

Weaknesses

  • Multi-component architecture (master, volume, filer, S3) is more to operate than a single-node store
  • Vector search needs a separate Rust weed-vector binary; the default installer omits it
  • Rebalancing does not run automatically; it is triggered from weed shell or the maintenance worker
  • Storage infrastructure, not an AI app starter; AI relevance is limited to S3 Vectors

What it needs

  • no GPU
  • Docker + Compose
  • Needs Optional filer metadata store (PostgreSQL, MySQL, Redis, etc.), weed-vector binary for S3 Vectors
  • port 8333

Quick answers

Is seaweedfs open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Can you run seaweedfs with Docker?

Yes. Its repository has a Docker setup: a Dockerfile, a Compose file or a published image.

Also in Backends, databases and hosting

See all 102
Also in Backends, databases and hosting
RankProjectScore
1bunJavaScript and TypeScript runtime with bundler, test runner and package manager96.7k starscustom license93 out of 100
2strapiHeadless CMS that generates REST and GraphQL APIs from content models Live demo ↗ (opens in a new tab)73.5k stars+245 (+0.3%) in 30 dayscustom license92 out of 100
3traefikHTTP reverse proxy and load balancer that auto-discovers routes from orchestrators65.5k stars+446 (+0.7%) in 30 daysMIT92 out of 100
#4appwriteBackend with auth, databases, storage, functions and an MCP server for agents Live demo ↗ (opens in a new tab)58k stars+463 (+0.8%) in 30 daysBSD-3-Clause92 out of 100
#5medusaNode.js commerce platform with modular products, carts, orders and payments37.2k starscustom license92 out of 100