Ross ROSS = Recommend OSS · open-source software intelligence for agents

seaweedfs/seaweedfs

SeaweedFS is a distributed storage system for object storage (S3), file systems, and Iceberg tables, designed to handle billions of files with O(1) disk access and effortless horizontal scaling. observed · 2026-08-28

github.com/seaweedfs/seaweedfs · homepage · Go · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

95/100

  • Activity 99
  • Release rhythm 87
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 6.0
  • age_days: 4433
  • days_rel: 11
  • days_push: 7
  • n_releases_24m: 67

Full methodology

Adoption not part of the score

34299 stars · 2968 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

SeaweedFS is a fast distributed storage system written in Go that provides S3-compatible object storage, a POSIX-compliant distributed file system, and an Iceberg table catalog, designed to handle billions of files with O(1) disk access and effortless horizontal scaling. It supports replication, erasure coding, tiered storage, FUSE/kernel mounts, and HDFS compatibility, with an optional paid Enterprise edition adding data recovery, point-in-time recovery, and automated Iceberg table maintenance.

Use cases

  • self-host an S3-compatible object storage cluster
  • store and serve billions of small files fast
  • mount distributed storage as a POSIX filesystem on Linux
  • replace HDFS with a lighter distributed file system
  • run erasure-coded blob storage on commodity hardware
  • host Iceberg tables with a built-in REST catalog
  • back up cloud object storage to local hardware to avoid egress fees

When to choose

  • you need massive-scale object or file storage with O(1) reads and horizontal scaling
  • you want S3 API compatibility on your own hardware without per-request or egress fees
  • you need both object storage and a POSIX filesystem from one cluster
  • you want erasure coding to cut storage overhead versus 3x replication
  • you need HDFS-compatible storage for Hadoop/Spark workloads

When to avoid

  • you need a fully managed storage service with zero operational burden
  • your dataset is small enough for a single machine or a simple NAS
  • you require Enterprise features like point-in-time recovery or data recovery but cannot license the paid edition
  • you depend on a rich vendor ecosystem and certified integrations like commercial cloud object stores provide

Facets

service · maturity active

object-storage file-system database caching microservices cloud-computing self-hosted infrastructure-as-code big-data windows go self-hosted cloud s3-compatible distributed-storage blob-storage erasure-coding fuse-mount hdfs iceberg-catalog posix-filesystem horizontal-scaling tiered-storage replication linux macos docker kubernetes

10 sources

Member repositories

RepositoryRoleHealth v2
seaweedfs/seaweedfsmain95

For agents

markdown · JSON · MCP: product_card(name="seaweedfs/seaweedfs")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem