Can someone at Unity better explain the pricing of Unity Cloud Build (now 'Automation')

Hello @ianstead1p and apologies for the delay.

Thanks for sharing your concerns! Your input is invaluable. We aim for transparent, flexible pricing so you can make smart choices and keep using our services with ease.

Please allow me to provide some detailed explanations to your specific questions, below:

  • Storage Costs: We calculate the cost of storage based on the average hourly storage (GB-hours) over the entire month to more accurately reflect not just how much you store but for how long you store it. When calculated hourly, these values would be:

  • 5 GB free each month = 5 GB x 1 month x (31 days / 1 month) x (24 hours / 1 day) = 3720 GB-hours for free per month

  • $0.1387 per GB for each month = ($0.1387 / 1 GB-month) x (1 month / 31 days) x (1 day / 24 hours) = $0.00019 per GB-hour

In months with fewer than 31 days, you would be able to store slightly more than 5 GB for free because we used the longest month to determine the size of the free tier to accommodate all months in a year.

Example 1: If you store 15GB for an entire month, you will store 15GB for an average of 730 hours per month (672 in february, or 744 on 31-day months, for 730 average per month). That results in 15GB * 730 hours = 10950 GB-hours. However, because we offer the 3720 GB-hours as part of the free tier, you would only be charged for 10950-3720=7230 GB-hours at a rate of $0.00019/GB-hour. The total charge would be 7230GB-hours * 0.00019/GB-hour = $1.3737 total.

Example 2: If you store 100 GB for 4 days and then delete the data, the end of month bill would work out to be: (100 GB x 96 hours - 3720 GB-hours) x $0.00019 per GB-hour = $1.1172

Your Example: if you produce 10x 1GB builds per day, every day continuously, spread out evenly across the day, and never delete any build ever, you will then create an average of 150GB per month, and each month will start with the 300GB total that was produced in the previous month. This means that after the first month you will pay for 150 GB-months, or 109500 GB-hours (using 730 hour months as the yearly average of hours per month) minus the 3720 free GB-hours. So the first month will be 109500 - 3720 = 105780 GH-hours, or $20.09. At the end of the next month there will be 300GB from the previous month, and a new 150GB, so the total will be 450GB * 730 hours/month = 328500 GB-hours, minus the free tier. Costing $62.415 assuming you are never deleting any builds. At the end of the year, you will have 11 months of 300GB being produced, and 1 month with only 150 average, and since no builds are ever deleted then it will accumulate to 11*300 + 150 = 3450GB stored, which will bring the monthly bill to 2518500GB-hours, or $478.515.

  • Instance Costs: Your first machine is free. If you decide to add additional concurrency, then yes, these will be billed at a rate of $0.50 per machine per day up to 3 machines, and anything beyond 3 machines will incur a charge of $2.00 per machine per day. An instance only incurs cost when it is used, so for many customers this will result in savings since most customers are not building 24x7 using all their available concurrency.

  • Seats: Seats pricing does not apply to UBA, only to users of Version Control in DevOps. To your point about whether you would need to pay extra for additional Build Automation ‘users’, the answer is no.

I hope this helps provide clarity to our pricing model. Please don’t hesitate to respond with any further questions or clarifications needed, we’ll be happy to help! If you would like some more specialized advice based on your specific account, please send a support ticket so that we can look into the specifics of your usage.