← Directory

Versity Gateway

The Versity Gateway serves as a bridge between file based, POSIX, storage systems and applications that rely on S3 object interfaces.

  • Backup
  • Cloud
  • Network Services
  • Tools & Utilities
The Versity Gateway serves as a bridge between file based, POSIX, storage systems and applications that rely on S3 object interfaces. It enables applications to interact with file storage using familiar S3 operations like put and get, allowing for easy integration and compatibility.

Platform availability

Available on 3 of 9 platforms

  • Unraid
  • TrueNAS
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

71/100 Good

Maintained
100last commit 14 days ago
Popular
692,958 GitHub stars
Easy to install
553 install platforms, install notes, Docker image
Light to run
2016 GB minimum RAM, runs on ARM

Availability: platform listings confirmed today

GitHub stars
2,958
Open issues
146
Last commit
2026-09-29
Latest release
v1.8.0
License
Apache-2.0
Activity
rising

Checked 15 days ago - source: GitHub (versity/versitygw)

Resources & Compatibility

Minimum requirements: 16 GB RAM, 4 CPU core(s), 100 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 15 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Use Helm and replace the example keys Run the Helm install command (Helm is a helper that deploys the app in containers) for a basic setup, and replace the sample access and secret keys with your own. Those keys let clients and the Web UI authenticate, and persistence keeps your buckets from disappearing when the container restarts. source
  • Set keys, WebUI port, and data folders If you use the command-line quickstart, provide your access and secret keys, choose a Web UI port like :8080, and set the IAM, versioning, and gateway data directories. The example uses /tmp, which is often cleared after reboot, so point those to a safe, persistent place if you want your setup to survive. source
  • Keep sidecar metadata separate If you turn on the POSIX sidecar option, which stores extra object details as separate files, make its directory accessible and distinct from the folder holding object data. Keeping metadata apart helps avoid missing or wrong details about your objects. source

Fetched 14 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why do some S3 clients fail with Versity Gateway if the client is left on default settings?

Versity Gateway uses path style addressing by default, while many clients default to virtual host style. Configure the client to use path style requests, or enable virtual host style with the --virtual-domain flag.

How should self-hosters handle a self-signed TLS certificate?

If you use a self-signed certificate, configure the S3 client to trust that certificate. This avoids TLS certificate errors during requests.

How can a bucket be served as a static website?

Enable a separate website endpoint and use --website-domain for virtual-host style routing, where subdomains map to bucket names. If you omit --website-domain, catch-all mode makes the full hostname the bucket name, so buckets should be named as fully qualified domain names.

Where should POSIX sidecar metadata be stored?

If you enable the POSIX sidecar option, put its directory in a location that is accessible and distinct from the folder holding object data. Keeping metadata separate helps avoid missing or incorrect object details.

What data directories need to be persistent in a command-line quickstart?

Set the IAM, versioning, and gateway data directories to a safe, persistent location. The quickstart example uses /tmp, which may be cleared after reboot.

What keys must be changed in a Helm deployment?

Replace the sample access and secret keys with your own. Those keys are used by S3 clients and the Web UI to authenticate.

Answers sourced from github.com, github.com, github.com, github.com, github.com

Community

Collected 9 days ago - public community threads