Today we launch the public beta of TeamCity Cloud, a product that we’ve been busy working on in recent months. TeamCity Cloud is a managed CI/CD service designed for teams that don’t want to deal with running and scaling their own build servers, but at the same time have demanding requirements for availability and security of their DevOps pipelines.
This release was made possible not only by the hard work of several teams inside JetBrains, but also by private beta users who helped us eradicate bugs and provided invaluable feedback. We are tremendously grateful for their participation and support!
How is TeamCity Cloud different from the original (on-premise) TeamCity?
TeamCity Cloud is different from the original TeamCity in two main ways:
- The service is completely hosted and managed by JetBrains. We provide a fleet of build agents and take care of upgrades, backups, and all other maintenance tasks, allowing you to focus on building and shipping your applications instead of administering your CI/CD infrastructure. For this reason, many administration features were disabled.
- TeamCity Cloud has a completely different pricing model. Instead of purchasing yearly licenses for TeamCity Server and TeamCity Build Agents, you subscribe to a plan that gives you a certain amount of build credits. Build credits are consumed at varying rates depending on the type of instance you choose to run your builds on. This allows you to pay only for what you use, with any number of parallel builds.
While it’s in beta, you can use TeamCity Cloud completely free of charge, without any hard limits on CPU time, storage, number of users, or number of projects.
Our general plan is to keep TeamCity Cloud as close to the original TeamCity as possible. We are continuing development of the self-hosted version, and all new features will appear in both products.
To learn more about TeamCity Cloud, please visit the TeamCity Cloud page on the JetBrains website.