How to use the Cloud Hosting Cost Calculator
This calculator gives a rough monthly cloud bill for an app from four inputs: active users, stored data, how media heavy the app is and the main region. It adds a fixed $50 floor to per-user costs for compute, database, bandwidth and CDN, adds a per gigabyte cost for storage, then applies a region multiplier. It is for founders and product teams who need a hosting budget before the architecture is settled.
Step by step
-
Set your monthly active users
Drag the Monthly active users (MAU) slider from 100 up to 1,000,000, in steps of 100. It starts at 10,000 and the current value shows beside the label. Use the number of people who use the app at least once a month, not total signups.
-
Enter the data you keep
Type your Stored data in GB, meaning files, uploads and other data held in object storage. The default is 50 GB, the arrows move it in steps of 10, and the field's maximum is 500,000 GB.
-
Say whether the app is media heavy
Under Media-heavy app?, choose No for an app that is mostly text and data, or Yes if it serves images, video or file downloads. Yes multiplies storage, bandwidth and CDN costs by 2.2 and raises the database line by 48%.
-
Pick the primary region
Under Primary region, choose US for the baseline, EU to add 5% or Asia to add 10%. The multiplier applies to every line of the estimate.
-
Read the estimate and the breakdown
The Estimated monthly cloud bill updates on every change. Below it are three cards and five bars that show where the money goes, so you can see which input moves the total most.
Reading the result
- The large figure is the monthly total. With the defaults (10,000 users, 50 GB, not media heavy, US) it is $764 a month.
- Annual run-rate is the monthly figure times 12, $9,162 with the defaults. Cost per 1,000 users divides the monthly bill by your users, $76 with the defaults, which helps when you compare against revenue per user. Region multiplier shows the factor in use, ×1.00 for US, ×1.05 for EU and ×1.10 for Asia.
- The bars split the bill into Compute, Database, Storage, Bandwidth and CDN: $200, $120, $5, $315 and $74 with the defaults. They add up to about $50 less than the total (a little more for EU and Asia, since the region multiplier applies to the floor too), because the fixed floor for load balancing, monitoring and base instances is not shown as a bar.
- The colored note reads as low cost under $500 a month, a mid-sized workload from $500 to $5,000, and a heavy workload above $5,000, with a short hint on what to tune at that size.
Tips and common mistakes
- Bandwidth is usually the largest line. The model assumes about 0.35 GB served per user each month at $0.09 per GB, so switching Media-heavy app? to Yes raises the default estimate from $764 to $1,293.
- Use the result as a range for budgeting, not a quote. Real bills depend on the provider, instance types, reserved pricing and traffic spikes.
- Try your launch numbers and a growth case, for example 10,000 and 100,000 users, to see how the bill scales before you commit to an architecture.
- Stored data barely moves the total at small sizes ($0.10 per GB a month). Check it again if you keep large media libraries or long backup histories.
Privacy and limits
The estimate is calculated in your browser from the inputs on this page. Nothing you enter is sent anywhere or saved, so reloading the page returns it to the defaults.
How it works
This calculator builds a monthly estimate the way a real cloud bill stacks up: a fixed floor for the always-on parts of a production stack, plus variable costs that grow with your monthly active users and stored data. Compute and managed database scale with how many people use the app; storage scales with how much data you keep; bandwidth and CDN scale with how much you serve out.
The media toggle matters because images, video, and file downloads move far more bytes per user and take more room in object storage, so it lifts the storage and bandwidth side of the model. The region setting applies a small multiplier because the same workload costs a little more in EU and Asia regions than in a US baseline.
Egress is often the surprise line item. We assume roughly a third of a gigabyte served per active user each month at commodity per-gigabyte rates, with a CDN offloading part of that delivery at a lower price. That mirrors how real stacks blend origin bandwidth with edge caching.
monthly = (base + compute + database + storage + bandwidth + CDN) × region multiplier
Treat the output as a planning baseline for budgeting, not a committed price. Once the architecture is nailed down, a proper software development cost estimate and a build-vs-buy comparison will sharpen both the build and run numbers.
FAQs
How accurate is this cloud hosting cost estimate?
It is a rough order-of-magnitude figure meant for early budgeting. Actual bills depend on your cloud provider, instance types, reserved or spot pricing, database engine, and real traffic patterns, the estimate can easily swing by 2x either way, so use it to frame a range, not to sign a contract.
Why is bandwidth such a big part of the bill?
Egress, data leaving the cloud to your users, is billed per gigabyte and is one of the few costs that grows almost linearly with usage. Media-heavy apps push far more bytes, which is why toggling media on raises the estimate noticeably. A CDN reduces this by caching content at the edge and serving repeat requests more cheaply.
Does this include the cost to build the software?
No. This tool estimates ongoing hosting and infrastructure only. The one-time cost to design and build the application is separate, use the software development cost calculator for that, or browse our services to scope a project.
