Healthchecks.io Migrates to Self-Hosted Object Storage, Ditches Third-Party Providers
Key Takeaways
- ▸Healthchecks.io replaced managed object storage (OVHcloud and UpCloud) with self-hosted infrastructure using Versity S3 Gateway and Btrfs after experiencing persistent performance degradation
- ▸The platform handles 14 million objects with 30 uploads/second average traffic and 150 uploads/second spikes, demonstrating that single-system self-hosting remains viable at this scale
- ▸The company prioritized operational simplicity over feature completeness, choosing a single-node solution over more complex distributed alternatives like Minio, SeaweedFS, or Garage
Summary
Healthchecks.io, a monitoring service that stores ping request payloads, has migrated from managed cloud object storage providers to a self-hosted solution powered by Versity S3 Gateway and Btrfs filesystem. The decision came after experiencing performance and reliability degradation with both OVHcloud and UpCloud, which the company had previously evaluated as alternatives to AWS S3 due to concerns about per-request pricing and regulatory exposure under the CLOUD Act.
The self-hosted infrastructure currently manages 14 million objects totaling 119GB, with an average object size of 8KB and peak throughput of 150 uploads per second. The company evaluated several open-source alternatives including Minio, SeaweedFS, and Garage before selecting Versity S3 Gateway, ultimately choosing simplicity over feature-rich but operationally complex distributed systems.
This migration reflects a broader trend among infrastructure-focused companies of moving away from third-party managed services when those services fail to meet performance and reliability requirements at scale. For Healthchecks.io, the self-hosted approach provides greater control while maintaining acceptable levels of availability and durability for non-critical storage use cases.
