ebogdum

callfs: Serve a Distributed Filesystem over REST

CallFS is a Go-based file storage server that exposes local disks and S3-compatible storage through a REST API. It routes file operations across nodes and offers optional erasure coding, metadata coordination, and owner-based access control.

View on GitHub Compare
Stars
403
Forks
13
Stars, last 30 days
+1
Last commit
3 months ago
Contributors
2

Our take

Activerecent releases

Health score

26/100

How it is scored
Activity
49
Community
15
Issues
21
Pull requests
20

+1 stars in the last 30 days

  • Fewer contributors than 86% of the projects we track

CallFS is a feature-rich Go storage server with recent releases, but its development is heavily concentrated in one contributor and recent issue and pull-request activity is absent.

Good fit if

  • Your application needs a REST interface over local or S3-compatible file storage.
  • You want to run a single-node setup or are prepared to configure metadata and peer routing for a cluster.
  • Your team is comfortable with Go 1.25 or deploying the project with Docker.

Look elsewhere if

  • You need a project with broadly distributed development ownership; most code contributions come from one person.
  • You need an S3-only service or a storage system whose documented interface is not centered on CallFS's REST API.
  • You need directory moves across backends or instances, which the README identifies as unsupported.
All health signals
Last commit2026-07-31 (3 months ago)
Commits, last 90 days2
Releases, last 12 months7 (latest v1.6.0, 2026-07-31)
Contributors2 (top contributor: 95% of commits)
Issues closed, last 90 days0
Pull requests merged, last 90 days0
Project age16 months

Checked on 2026-10-23 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

405

Forks

13

Change since Nov 14, 2026: 0 stars·0 forks

Overview

CallFS is a Go-based storage server that exposes local filesystems and S3-compatible object stores through a REST API. It aims to give applications a common HTTP interface for file operations without relying on NFS mounts or tying storage to a single backend.

The project is intended for teams building file services or operating storage across multiple nodes. Files can be routed to the node where they live, while metadata can use PostgreSQL, SQLite, Redis, or built-in Raft. Its focus is file-oriented REST access, rather than providing only an S3-compatible object-store API.

Key Features

  • Store files on local disks or S3-compatible backends, including Amazon S3 and MinIO.
  • Upload, download, list, delete, rename, and move files through HTTP endpoints.
  • Route requests across cluster nodes and stream file transfers without buffering whole files in memory.
  • Use configurable Reed-Solomon erasure coding to distribute data and parity shards across nodes.
  • Choose PostgreSQL, SQLite, Redis, or Raft for metadata coordination.
  • Apply API-key authentication and owner-based permissions, with time-limited single-use download links.
  • Run with Docker or as a Go-built binary; expose health checks and Prometheus metrics.

Use Cases

  • A team building a file-management service can use the REST API for uploads, downloads, directory listings, and file moves.
  • A media or data pipeline can keep files on local disks or S3-compatible storage while accessing them through one API.
  • Operators needing files across several nodes can use peer routing and, where appropriate, erasure coding for shard-based fault tolerance.
  • A backup service can use single-use download links to share files without giving recipients API keys.

What you need

Detected in the repository

  • Go 1.25.0 or newer (from go.mod)
  • A Dockerfile, so it can run in a container; a Compose file sets up the related services
  • A test suite and automated checks on GitHub Actions

License in plain words

MITpermissive

  • Commercial use: yes
  • Modify and redistribute: yes
  • You must keep: the copyright and license notice
  • Share your changes: no

A summary, not legal advice: the LICENSE file is what applies.

Getting Started

Build from source and start the server with a configuration file:

go build -o callfs ./cmd/main.go
./callfs server --config config.yaml

See the CallFS README for configuration, Docker instructions, and API examples.

Alternatives

  • alist: AList unifies browsing and sharing across many existing drives via a web UI and WebDAV, while CallFS focuses on distributed storage, node routing, and erasure coding.
ProjectLanguageLicenseStarsStatus
callfsGoMIT403Active
alistGoAGPL-3.050.3kActive

Considerations

  • The project requires Go 1.25 for source builds; Docker is also supported. A metadata store must be configured, although SQLite and built-in Raft are listed alongside external services.
  • The measured health data indicates recent releases but only a small number of recent commits. Two contributors are recorded, with most code attributed to one; no issues or pull requests were closed or merged in the measured recent period.
  • The README notes that moving files to or from the erasure backend and moving directories across backends or instances are not supported.
  • Cluster setup involves configuring peer endpoints and, depending on the chosen features, metadata storage and distributed locking. The README documents these components but adoption still requires operational decisions beyond a local single-node setup.

Found this useful?

Share it with someone who would like callfs.

Comparisons