Question regarding updates to self hosted runner pricing

[Travis Morgenstern]

I notice this post from last week(https://www.atlassian.com/blog/bitbucket/announcing-v5-self-hosted-runners?utm_source=sfmc&utm_medium=email&utm_campaign=EML-21610&jobid=107674872&subid=1926220684) and wanted to ask a clarifying question:

• $15/month per concurrent build slot: Pricing per build slot provides significant value when compared to alternative commercial self-hosted CI tools. For most customers migrating from Bamboo, the costs of running a fleet of self-hosted runners will be significantly lower when ran on Pipelines.

Does this mean that if we have 2 self-hosted runners in our system we'll be paying 30$/month to connect those to our bitbucket pipelines?  There would not be a per job cost associated with this since we're self-hosting?

We have jobs running concurrently every 4 hours and are concerned there's a 15$/job cost based on the definition of a build slot.

[Noah Bailey]

In your example the first "build slot" would be free, but the second would cost $15/mo. 

If you had five runners, it would be 1 free slot plus four paid, totaling $60/mo. 

It's not per-build, just for concurrency. If you only ever have one build running at a time this won't effect you, but if you're frequently loading up all your runners at the same time you would indeed need additional slots. 

To be clear, I'm not agreeing with this change, just explaining it. I'm quite against them making us pay to use infrastructure that we own and operate.