Skip to main content

​
Dynamic (shared) instances

Dynamic Instances provide on-demand scaling and charge you based on your actual consumption of CPU, RAM, disk, and bandwidth. This flexible model ensures you only pay for what you use, making it ideal for deployments where resource usage is not constant or easily forecasted. Dynamic instances are particularly well-suited for developers conducting experiments or proofs of concept, as they provide a cost-effective and scalable testing environment. They are also ideal for applications with unpredictable traffic patterns or workloads that experience occasional spikes and periods of low activity. By aligning costs directly with resource utilization, dynamic instances deliver an adaptable and efficient solution for scenarios requiring flexibility.

​
Cost components and rates

There are two types of cost components: based only on amount or on amount and time.
  • Cost components based on time and amount
    • CPU
    • RAM
    • Anycast IP
    • Disk usage
  • Cost components based on amount only
    • Egress traffic

​
CPU

CPU is billed per second of CPU time consumed by your containers. If your container uses an entire CPU core for one second, you pay for one second of CPU time. If it uses half a core for one second, that counts as 0.5 seconds of CPU time. If two cores are used for one second, that counts as 2 seconds of CPU time. Calculation example:
  • CPU cost: $0.02 per CPU per hour
  • Cost per second of CPU time: $0.02 / 60 / 60 = $0.000005555555556 per second
Example scenario: If your application uses 3 seconds of full CPU time per minute; every minute for the period of entire month:
  • 1 minute = 60 seconds
  • CPU usage per hour = 180 seconds ( 3 second per minute * 60 minutes)
  • Hourly CPU cost = 180 x $0.000005555555556 ≈ $0.001
  • Daily CPU cost = 24 x $0.001≈ $0.024
  • Over an entire month (31 days), your CPU cost would be roughly $0.744.

​
RAM usage

Memory (RAM) is billed in 64 MB increments per hour. Even if your application uses only 10 MB, you’ll pay for one 64 MB block. Usage is calculated hourly and aggregated at the end of the billing cycle.
For actual workload memory, please note that the total reported memory usage charged will include an additional system overhead that is variable with the workload.
Calculation example:
  • RAM Cost: $0.005 per GB per hour (1 GB ~ 16 blocks by 64MB)
  • Cost per 64 MB block per hour: $0.005 / 16 = $0.0003125
Example scenario: If your application uses 512 MB of RAM usage (8 blocks of 64 MB) per hour; every hour for the period of entire month:
  • Price per 512 MB per hour: $0.00025 x 8 = $0.002
  • Price per day: $0.002 x 24 = $0.048
  • Price per month (31d): $0.048 x 31 = $1.488

​
Anycast IP usage

The cost for Anycast IP (IPv4) is $2 for per month. If you use Anycast IP (IP is attached to the application) only for some period within the month we will charge only for that period. Calculation example:
  • Anycast IP Cost: $2 per month
  • Anycast IP Cost per minute (if 31d month): 2 / 31 / 24 / 60 = $0.000044802867384
Practical scenario: If Anycast IP is attached to your application for 10 days, 7 hours, and 15 minutes in the last month you will be charged for:
  • Anycast IP Cost per hour: $0.000044802867384 x 60 = $0.002688172043011
  • Anycast IP Cost per day: $0.002688172043011 x 24 = $0.064516129032258
  • Total Anycast cost: 10 * $0.064516129032258 + 7 x $0.002688172043011 + 15 x $0.000044802867384 = $0.664650537634417

​
Disk usage

Persistent storage (coming soon) is billed per 1 GB block, prorated hourly, ensuring you only pay for the exact disk space you consume. Calculation example:
  • Storage cost: $0.10 per GB per month
  • Daily cost per 1 GB (31 days): $0.10 / 31 = $0.003225806451613 per GB per day
Practical scenario: Let’s use the following scenario: your application uses 3 GB of storage for 3 days. Then you upload an additional 2 GB (5 GB total) and keep it for 5 days. After that, upload another 5 GB (now 10 GB total) and keep it for the rest of the month. The cost will be calculated as follows:
  • Cost for 3 days for 3 GB = 3 x 3 x $0.003225806451613 = $0.029032258064516
  • Cost for 5 days for 5 GB = 5 x 5 x $0.003225806451613 = $0.080645161290323
  • Cost for (31 - 8) = 23 days for 10 GB = 23 x 10 x $0.003225806451613 = $0.741935483870968
  • Total cost: ~$0.77

​
Network traffic usage

Network traffic is charged based on the total data transferred each month. The prices vary by region. The MC costs include the following traffic:
  • All egress traffic, except for traffic going through the CDN (CDN traffic is charged as part of the CDN service).
Region prices:
  • Europe & North America: $0.01/GB
  • South America: $0.045/GB
  • Asia & Oceania: $0.03/GB
  • Middle East & Africa: $0.06/GB
Practical Scenario: If your application served 15 GB of traffic from Europe, 10 GB of traffic from the Middle East, and 3 GB from South America, the costs would be calculated as follows:
  • Europe traffic cost: $0.01 x 15 = $0.15
  • Middle East traffic cost: $0.06 x 10 = $0.6
  • South America traffic cost: $0.045 x 3 = $0.135
  • Total: $0.885

​
Reserved instances (coming soon)

Reserved Instances, coming soon to Magic Containers, provide a fixed monthly cost for predefined resources. With this model, you pay a fixed amount every month, regardless of usage, making it easier to forecast expenses and maintain a stable budget. Reserved Instances are specifically designed for businesses with stable and predictable workloads, making them ideal for scenarios where cost predictability, consistent performance, and well-defined resource requirements are crucial. These instances will be available in multiple standardized configurations, each bundling vCPUs, memory, and NVMe storage to accommodate a variety of application needs. If you have questions or would like more information, feel free to contact our sales team for assistance.