Migrating to Self-Hosted Object Storage with Versity S3 Gateway

At Healthchecks.io, we handle ping endpoints using HTTP HEAD, GET, and POST methods, storing the first 100kB of POST request bodies. Initially, we used managed object storage solutions like OVHcloud and UpCloud, but faced performance issues over time. Our current storage needs include handling 14 million objects and supporting up to 150 uploads per second. We require a system that is reliable yet not as critical as our PostgreSQL database.

After evaluating options like Minio, SeaweedFS, and Garage, I opted for Versity S3 Gateway, which turns a local filesystem into an S3 server. This choice simplifies operations by eliminating the need for a separate metadata database and complex cluster management. Versity S3 Gateway allows us to use any backup tool, and its upgrade process is straightforward.

In March 2026, we migrated to a self-hosted setup using Versity S3 Gateway. Our S3 API runs on a dedicated server with objects stored on local NVMe drives in RAID 1 configuration, backed by a Btrfs filesystem. We perform regular backups using rsync and store encrypted daily backups off-site. This setup reduces latency and improves performance, although it increases costs due to the need for a dedicated server.

The transition has resulted in faster S3 operations and a reduced queue of pending uploads, with no availability issues so far. While the costs have risen, the enhanced reliability and performance justify the investment. I remain open to future migrations if a better solution emerges.