TeamCity Cloud Pricing For Self Hosted Build Agents

We've been trialling TC Cloud for a little while and we have 6 committers on our team. £70ish seems reasonable for the hosted service. We currently have a self-hosted TC server with 6 self-hosted build agents that we have paid for and we want to carry on using (for various technical reasons relating to speed of build and the occasional bit of special configuration). 

We are pretty horrified to discover that having paid for these build agents once, TC Cloud requires us to pay a monthly fee to carry on using them. This pretty much doubles the cost of our monthly subscription and makes TC Cloud not economically viable for us. It also leaves an unpleasant taste in the mouth and a faint sense of being ripped off by having to pay for something again (in perpetuity) that we have already paid for in full.

This is a poor business model, JetBrains! Please remove the fees for us using our own Build Agents.

3 comments
Comment actions Permalink
Official comment

Hi Nick,

Thanks for your honest feedback! TeamCity Cloud is a very new service from JetBrains, so we are keen to hear this type of feedback in order to decide how we can make improvements to this new offering and the associated pricing model.

While we do have some customers interested in moving from TeamCity On-Premises to TeamCity Cloud, it’s important to highlight that the licensing of both solutions is completely separate at this time (as you have mentioned). 

We will be looking to offer additional licensing options in the future, which could include the ability to exchange on-premises build agent licenses for additional self-hosted build agent concurrency on TeamCity Cloud. 

I wanted to highlight (and this is a benefit of TeamCity Cloud) that we don’t charge for the connection of each self-hosted build agent to a TeamCity Cloud server - instead we just charge for the concurrency of builds on self-hosted build agents. This means you can have any number of self-hosted build agents connected to your server, and you are just charged a flat monthly rate for the number of concurrent builds you wish to run on any of those self-hosted agents. For example, you could have 100 self-hosted build agents connected to your TeamCity Cloud server, and if you redeemed 60,000 credits per month for 3 self-hosted agents (3 x 20,000), you would be able to run 3 builds concurrently on any of those 100 self-hosted agents.

While the ability to transfer TeamCity On-Premises build agent licenses to TeamCity Cloud isn’t an option at this time, please email me (via teamcity-cloud-info@jetbrains.com), and I would be happy to go over your requirements and see how we may be able to make TeamCity Cloud a more viable option from a cost perspective.

Please let me know if you have any additional questions.

Thanks!

Comment actions Permalink

Hi

I understand what you mean here, but from my point of view, I can run 6 builds simultaneously on self-hosted TC now using our own build agents on our own build servers. We'd like to move the TC UI to the cloud and carry on using our own Build Agents. Paying again to use our own build servers seems like a crazy pricing model. Is the burden of us using our own Build Agents really that high on the TC cloud infrastructure? Aren't we doing all the work in this scenario and TC Cloud is just performing a simple lightweight build monitoring process?

It seems like a lot of additional cost for a worse product.

Nick.

 

0
Comment actions Permalink

Hi Nick,

I do understand your point of view. Please reach out to me (via teamcity-cloud-info@jetbrains.com), and I would be happy to discuss a way forward if you are still keen on using TeamCity Cloud.

Thanks!

Daniel

0

Please sign in to leave a comment.