How does Packet compare to Amazon Web Services
Amazon defined the cloud computing market with the launch of AWS and continues to offer a powerful, expansive walled garden approach to infrastructure and platform services. With hundreds or thousands of different pricing options or services levels, AWS is a supermarket approach to cloud computing.
What We Have in Common
Actually, we don't have a lot of overlap. We respect AWS enormously for what they've built: a seemingly infinite platform that can perform at massive scale (think Netflix!). It offers a great solution for many use cases - however, it has critical downsides that include complexity, vendor lock-in, noisy neighbors, and a focus on virtualization.
How We Differ
Packet believes in a simple mission: to provide on-demand instances of the most powerful bare metal cloud servers in locations across the globe. AWS has 900 ways to price an EC2 instance, Packet has 2.
And Packet supports native container technologies that allow you to develop and deploy on Packet, but do so without any vendor-lockin through proprietary services or APIs.
What Type of AWS Instances Does Packet Compare To?
Packet's Type 1 "application" server compares nicely to several AWS instances:
| Packet Type 1 | AWS m3.2xlarge | AWS C3.2xlarge | |
|---|---|---|---|
| Price | $0.40 | $0.532 | $0.42 |
| CPU Cores (hyperthreaded) | 8 | 8 | 8 |
| RAM | 16GB | 30GB | 15GB |
| HDD | 2 x 120GB SSD | 2 x 80GB SSD | 2 x 80GB SSD |
| Network | 2 x 1Gbit | 1 x 1Gbit | 1 x 1Gbit |
Packet's Type 3 "High IO" server compares nicely to several AWS instances:
| Packet Type 3 | AWS i2.4xlarge | AWS C3.8xlarge | |
|---|---|---|---|
| Price | $1.75 | $3.41 | $1.68 |
| CPU Cores (hyperthreaded) | 32 | 16 | 32 |
| RAM | 128GB | 122GB | 60GB |
| HDD | 2 x 120GB SSD | 4 x 800GB SSD | 2 x 320GB SSD |
| NVME Flash | 2 x 800GB | n/a | n/a |
| Network | 2 x 10Gbit | 1 x 1Gbit | 1 x 10Gbit |
