Deep Security as a Service pricing and billing
In this article, you can learn more about:
- Deep Security as a Service pricing.
- What Deep Security as a Service considers as a protection hour.
- When Deep Security as a Service considers a computer protected.
Pricing for AWS Marketplace billing subscription, prepaid credit and credit card subscription or Azure Marketplace Deep Security Manager (BYOL) payment options are as follows:
|Instance size||Example instance types||Cost of protected instance per hour (in USD)|
|Medium or smaller||
AWS EC2: C1, M1, M3, T1, T2
Azure: 1 core
AWS EC2: C3, C4, M1, M3, M4, R3, T2
Azure: 2 cores
|xLarge and bigger||
AWS EC2: C1, C3, C4, CC2, CG1, CR1, D2, G2, HI1, HS1, I2, M1, M2, M3, M4, R3
Azure: 4 or more cores
All non-cloud instances
If you are using the prepaid credit option, Trend Micro will notify you when you have 30 days left of credit, estimated based on your current usage. If your credit runs out before you have renewed, your protection remains active but you won't be able to activate any new agents and existing agents will no longer receive any updates.
With Deep Security as a Service AWS Marketplace billing, you pay for any hours during which your computers are protected. A computer that is protected for any part of an hour will be billed for the full hour.
You can see how this is calculated in the usage scenarios below:
For more information on how to check the current number of billed protection hours, see Check your costs and usage on the AWS Marketplace.
When a computer is considered to be protected by Deep Security as a Service depends on where the instance is hosted.
Computers on a cloud service
For computers added to Deep Security as a Service from a cloud service, you are billed when the instance the agent is protecting is powered on. This means that you will continue to be billed for agents in an "Offline" state if the instances they protect are still powered on.
To avoid being billed for protection unnecessarily, we recommend that if you are considering turning off a Deep Security agent for an instance, that you instead power off that instance.
Computers not on a cloud service
For computers added to Deep Security as a Service that are not on a cloud service, you are billed when the agent is in a state other than "Offline". A computer will enter the "Offline" state if the agent protecting it misses one or more heartbeats from the Deep Security Manager.