Announcing powerful upgrades & a new pricing model for self-hosted runners

[Benjamin Löffler]

@Ash Moosa we NEED a update NOW!

[Angga Kusumandaru]

We’ve reversed our decision to deprecate free runner versions. We will continue to provide a free self-hosted runners option going forward.

First of all, thanks for listening to our feedback and for continuing to support the free Runner version.​

On the other hand, could you clarify whether the free version will stay on the locked Version 4, or if it will use a different tag than the premium version going forward?

[Liam Nunns]

@Angga Kusumandaru we will provide a better update as soon as we can, we want to make sure we get this right.
It's safe to say though that the V4/V5 tag as a method of differentiating the paid/free runner is being reconsidered in favour of a longer term approach; one model under consideration is a user could declare whether the runner is paid or free at time of registration, either via UI or API https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pipelines/#api-workspaces-workspace-pipelines-config-runners-post

[Benjamin Löffler]

If I understand this correctly:

You will update the runners, but only the currently available one (v4) is free of charge. Any future updates, fixes, or improvements will only be available if we pay for them?

So effectively, everyone will end up stuck on an increasingly outdated runner unless we pay Atlassian for the privilege of using our own hardware?

Regarding your statement:

“Additionally, many of our customers want us to continue to innovate in this space, which comes with real costs on our end. So we will continue to offer a premium tier, which we will charge for per the announced pricing.”

I have a simple question: What exactly are we paying our regular Bitbucket license for then? And on top of that, our already expensive Jira and Confluence licenses?

The pricing model as it stands seems to be:

• we pay monthly for the products we already use, and
• we have to pay extra again if we want to receive updates and improvements in this area.

This feels like we are being charged twice for the same product evolution. Honestly, the situation with Atlassian’s pricing these days comes across as increasingly unreasonable.

[Bob Eckert]

I'm still confused on how queue slots cost money.  

Basically why couldn't I run my own self-hosted fleet and have more jobs being able to be run? 

Count someone please explain why additional concurrency impacts my use of self.hosted runners?

Thanks for not charging us for using our own hardware, but you're still charging us to effectively use our own hardware.