System Requirements

VersityGW is built and tested on Linux, macOS, BSD, and Windows. The exact backend features available can vary by operating system and filesystem, so validate the selected backend and workload on the target platform before production deployment.

Hardware guidelines

There are no fixed processor or memory requirements. Size the system for the expected object count, throughput, and number of concurrent clients. As general guidelines:

• x86_64/arm64 is tested/supported; 4 or more CPU cores are recommended for production workloads.
• At least 1 GB of RAM is recommended for small deployments. Larger workloads may require substantially more memory.
• A 10GbE or faster network interface is recommended for high-throughput deployments.

Platform support

The repository's CI validates gateway builds and tests on Linux, macOS, BSD, and Windows, including Windows functional tests. Platform-specific filesystem behavior still applies, particularly for the POSIX backend and its optional features.

Filesystem and metadata requirements

The POSIX backend stores object metadata in extended attributes (xattrs) by default. Therefore, a filesystem used with the POSIX backend must support xattrs unless one of these options is selected:

• --sidecar stores metadata in a separate directory and can be used on a filesystem without xattr support.
• --nometa disables metadata storage and can be used on a filesystem without xattr support, with the metadata limitations described in POSIX Backend.

Other backends have their own storage requirements. See the documentation for the selected backend before deployment.

Deployment options

The gateway can run as a static binary without any dependency on system library versions. Docker images are available for containerized Linux deployments, and Linux distribution packages include systemd service scripts. Provided OCI Helm chart supports Kubernetes deployments.