versity/versitygw

A simple to deploy but feature rich S3 object storage server for your filesystem

View on GitHub ↗Jump to charts ↓Open shareable report →

versity/versitygw has 3k+ stars and 300+ forks on GitHub, is written in Go, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on October 8th, 2026
Created on May 5th, 2023
Open Issues & Pull Requests: 130 (+0)
GitHub issues: Enabled
Number of forks: 321
Total Stargazers: 3,037 (+0)
Total Subscribers: 20 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 26.7 hours
Mean response time: 40.3 days
90th percentile: 111.1 days
Tracked items: 624

Maintainer activity

3 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 8% of issues opened in the past year have never received a reply. 93% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "testcase" is answered fastest, typically in under an hour, while "bug" waits about 2 days. 55% of tracked open issues have had no activity in three months. 84% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 100
New in 7 days: 14
Closed in 7 days: 10
Avg open age: 367 days
Stale 30+ days: 78
Stale 90+ days: 68

Recent activity

Opened in 7 days: 14
Closed in 7 days: 10
Comments in 7 days: 0
Events in 7 days: 9

Top labels

  • bug (476)
  • enhancement (116)
  • testcase (33)
  • backend (2)
  • documentation (2)
  • posix (2)
  • waiting_for_use_case (2)
  • good first issue (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Versity S3 Gateway is an S3 object storage server that translates S3 requests to filesystem storage or proxies them to other S3 backends.

The tool solves the problem of running S3-compatible applications against non-S3 storage systems. It works by accepting standard S3 API calls and translating them to operations on the underlying storage backend, whether that is a local filesystem, remote S3 storage, or other systems. This allows existing S3-dependent applications to work with alternative storage without modification. The gateway supports S3 over RDMA for high-throughput, low-latency transfers in HPC and data-intensive workloads, bypassing the kernel network stack. It also includes static website hosting capabilities, allowing S3 buckets to be served as websites with index documents, custom error pages, and routing rules.

Developers should choose this tool if they need to expose filesystem storage via S3 APIs or want to add S3 compatibility to existing storage systems. It suits single-command deployments where simplicity is valued, and it works across Linux, macOS, BSD, and Windows platforms. The project offers a web GUI for management and exploration, and supports a POSIX protocol mode that allows common file access via both POSIX and S3 interfaces simultaneously. The tool is designed to be straightforward to deploy without complex configuration.

The project maintains active community engagement through discussions and a mailing list for announcements. Documentation is comprehensive, available on the project wiki with dedicated articles covering features like S3 RDMA setup and global configuration options. The codebase is written in Go and distributed as precompiled binaries for multiple architectures and operating systems, reducing deployment friction.