Why we are not leaving the cloud

This post details GitLab's decision to remain in the cloud for GitLab.com, reversing an earlier consideration to move to bare metal. It summarizes community feedback received on cost, performance, storage, and network proposals related to the bare metal migration. Key themes from the feedback include the significant operational overhead and expertise required for managing bare metal infrastructure, the importance of application architecture over deployment environment, potential performance trade-offs with certain hardware choices (e.g., 8TB drives, CephFS), and the complexities of networking and storage management in self-hosted environments. The post emphasizes that the decision was based on a comprehensive evaluation of these factors and a commitment to making GitLab.com fast and stable in the cloud.