Comparing AWS with Packet?
Amazon defined the cloud computing market with the launch of AWS and continues to offer a powerful, expansive approach to infrastructure and platform services. With hundreds or thousands of different pricing options and service levels, AWS offers a supermarket approach to cloud computing.
We respect AWS enormously for what they've built: a seemingly infinite platform that can perform at massive scale. It offers a great solution for many use cases - however, it has downsides that include complexity, vendor lock-in, noisy neighbors, and a focus on virtualization (granted, their bare metal product is pretty snazzy).
Our main shared feature is automation. In fact, our goal when starting the company was to bring an "AWS-like experience" to bare metal, so that developers (and their software) could consume dedicated infrastructure the same way they do other public cloud resources. From quick deploys (~60 seconds) to deep integration with the DevOps ecosystem, AWS & Packet have a lot in common when it comes to consumption experience.
|Native IPv6 Support|
|Simple, Clean API|
|Deploys in Minutes|
|Extensive DevOps Integrations|
|Cloud-init / Metadata Support|
|Spot Market Feature|
|Full Hardware Access||Limited|
|Private Deployment Option|
|Local & Global BGP|
|BYO IP Space|