Healthchecks.io Now Uses Self-Hosted Object Storage

4 hours ago

Healthchecks.io uses HTTP HEAD, GET, and POST for ping endpoints, storing up to 100kB of request body in PostgreSQL (small) or S3 (large).
Migrated from managed to self-hosted object storage using Versity S3 Gateway with a Btrfs filesystem due to performance and reliability issues with OVHcloud and UpCloud.
Requirements include handling 14M objects (119GB), ~30 uploads/sec (spikes to 150), constant churn, with moderate latency needs and availability less critical than PostgreSQL.
Evaluated self-hosted options like Minio, SeaweedFS, and Garage but found them operationally complex; chose Versity S3 Gateway for simplicity, single binary, and active development.
Setup includes a dedicated server with RAID 1 NVMe drives, Btrfs filesystem, rsync backups every 2 hours, and daily encrypted off-site backups for durability.
Results show reduced S3 latencies, smaller upload queues, no availability issues initially, higher costs but improved performance and reliability, with openness to future migration.

Hasty Briefsbeta