At CoreOS, we use Packet to host the Quay.io build system[0]. Getting bare-metal machines from Packet that we can run our own virtualization on has saved us a s

At CoreOS, we use Packet to host the Quay.io build system[0]. Getting bare-metal machines from Packet that we can run our own virtualization on has saved us a significant portion of our expenses compared to our previous system which dynamical spun up EC2 instances. This is definitely not the traditional deployment, but if you're using things like dedicated servers on AWS, you should be evaluating Packet. In my own personal ops experience with Packet, I've actually seen less failures than Amazon; it feels like more than once a week Amazon has degraded service on the EC2 API in us-east-1 that used to cause us downtime. Not to mention, Amazon waits like 4 hours before they admit anything ever went wrong (green with a tiny yellow badge). However, I'd take this with a grain of salt, as we've replaced the Amazon control plane with a Kubernetes control plane and only interact with Packet API when we tear-down/spin-up a new cluster. [0]: https://blog.quay.io/faster-container-builds https://blog.quay.io/faster-container-builds