As an Edge Compute customer, you should become familiar with how the service is billed to ensure a predictable invoice each month. This article explains the different components that can make up the Edge Compute part of your StackPath bill.
We bill our Edge Compute products based on use. You will only see the invoice items mentioned below if you used them during each billing period.
Note that, throughout this document, you will see the unit of GB for various charges. 1 GB is defined as 2^30 bytes. This unit of measure is also known as a gibibyte.
Billing for VMs and Containers
Both our Virtual Machines and our Containers are offered in the following subscriptions: SP-1, SP-2, SP-3, SP-4, SP-5, SP-6, SP-7, and SP-8. Each subscription has its own given number of CPU cores, RAM, and root disk size.
On our Virtual Machine and Container price sheets, you will notice that each subscription has an effective price per hour used. This price is an aggregate of the costs incurred for each metric that makes up the subscription’s geometry; this is what will be reflected in your invoice.
For example, let’s say you ran three SP-2 Containers for 100 hours. You would be charged the following:
- SP-2 price per hour $0.098
- For 100 hours used is $9.80
- For 3 VMs is approximately $29.40
However, on your invoice, those charges would be reflected as follows:
- Container CPU at 600 CPU Core hours at a rate of $0.039421 per hour ($23.65)
- Container Memory at 1200 GB hours at a rate of $0.0043286 per hour ($5.19)
- Container Root Disk Storage at 3000 GB hours at a rate of $0.000145833 per hour ($0.44)
Adding the above charges, you would still be charged approximately $29.40 with some rounding. This billing method is applied identically to our Virtual Machines as well.
The pricing provided in the above example is sample pricing only. Please refer to the StackPath website for correct pricing.
In addition to the costs for running your subscribed instances, you will also incur charges for egress traffic. Egress traffic is billed at varying rates per GB depending on the traffic (e.g., destination location). Egress traffic originating from a VM is charged at the exact same rate as egress traffic originating from a Container.
Ingress traffic, or traffic coming from the public internet into a StackPath instance, is not charged.
Static IP addresses are included on a per instance basis, and you will not see a charge for this on your invoice.
Should you choose the optional Anycast IP Address option or request multiple static IP addresses, you will be charged per IP per hour.
If you choose to use the optional persistent storage feature, which allows you to expand overall storage space for newly created workloads, you will be charged an hourly rate for GB of storage used. While you may see this broken out regionally on your invoice, it is charged at the same rate regardless of region.
If you create your own image to run on our Virtual Machines, you will be charged for the storage needed to house that image.
Our list prices for storage show GB/mo., but on the invoice, this is charged per hour.
L3/L4 DDoS Protection
Enrolling in L3/L4 DDoS protection is a crucial step to ensure your instances are secured on the StackPath platform. We offer L3/L4 DDoS protection in three different packages: Standard, Professional, and Enterprise. Each package has a different monthly charge and a different added instance-hour rate. One instance hour is defined as protection for one instance for one hour.
The Standard package is a pay-as-you-use model where you’ll get charged a flat rate per instance hour.
Both Professional and Enterprise have a monthly recurring charge and a separate rate per instance hour above what’s included in the package.
For more information about your L3/L4 DDoS charges, you can check out this article.