What is included in JetBrains TeamCity Cloud?

Managed CI/CD – Hosted build and test automation service.
Cloud agents – JetBrains-hosted Linux and Windows build machines.
Pipeline configuration – Web UI or Kotlin DSL code.
Native integrations – Git, Docker, and Jira without plugins.
Performance Metric – 8,000 build credits per committer slot included.
Important – No hosted macOS agents; bring your own Mac.

What are the main benefits of JetBrains TeamCity Cloud?

TeamCity Cloud is a managed continuous integration and delivery service that runs your build, test, and deployment pipelines on infrastructure maintained by JetBrains. It removes server upkeep while keeping the same workflow used in TeamCity On-Premises.

No server upkeep – JetBrains handles patching, scaling, and maintenance.
Configuration as code – Version your pipelines using Kotlin DSL.
Hybrid agents – Mix hosted and self-hosted build machines.
Free web users – Unlimited non-committing managers, testers, and viewers.
Native tooling – Maven, Gradle, .NET, and Docker built-in.
Failure analysis – Smart analysis of failed builds and tests.

What does JetBrains TeamCity Cloud do?

TeamCity Cloud automatically builds, tests, and deploys your code whenever changes reach your version control system. JetBrains runs the server in AWS and supplies Linux and Windows build agents, so your team configures pipelines instead of maintaining build infrastructure. Pipelines can be set up through the web UI or written as Kotlin DSL and stored in source control, which keeps build logic versioned alongside the code. The service reports test results and analyzes build failures so broken changes are caught before they reach production.

Who is JetBrains TeamCity Cloud best suited for?

TeamCity Cloud fits development and DevOps teams that want CI/CD without running their own build server, especially JVM-focused shops working with Gradle, Maven, or Kotlin. Its first-class Gradle and Maven support, including dependency analysis and parallel test distribution, reduces the cache and JVM warm-up overhead that ephemeral-runner platforms struggle with. Teams already on IntelliJ IDEA or other JetBrains IDEs get tighter feedback through the bundled IDE plugins. It is a weaker fit for teams that need JetBrains-hosted macOS builds, since those still require a self-hosted Mac agent.

How does TeamCity Cloud differ from TeamCity On-Premises editions?

The main difference is who runs the server: TeamCity Cloud is hosted and maintained by JetBrains, while TeamCity On-Premises runs on your own hardware. On-Premises comes as a free Professional edition, capped at 100 build configurations and 3 build agents, and a paid Enterprise edition with unlimited configurations and full plugin support. TeamCity Cloud removes those caps and adds JetBrains-hosted agents, but exposes fewer low-level administration controls because JetBrains manages the underlying system. Cloud also receives updates more frequently than the twice-yearly On-Premises releases.

Does TeamCity Cloud provide hosted macOS build agents?

No. JetBrains-hosted build agents in TeamCity Cloud run only Linux and Windows; there are no JetBrains-managed macOS agents. To build for macOS, iOS, tvOS, or other Apple targets, you must install the TeamCity agent on your own Mac and connect it as a self-hosted agent, which uses a concurrent build slot. This matters for Apple developers, who keep responsibility for provisioning and maintaining their own Mac hardware even on the managed service. Self-hosted agents themselves support Windows, Linux, and macOS.

Which version control systems and build tools does it support?

TeamCity Cloud natively integrates with Git, GitHub, GitLab, Bitbucket, Perforce, Subversion, Azure DevOps, and Mercurial, and it preconfigures the connection automatically when you authenticate through GitHub, GitLab, or Bitbucket Cloud. For builds it includes runners for Maven, Gradle, Ant, .NET, and Docker, plus test reporting and code coverage without extra plugins. Issue trackers such as Jira and YouTrack stay updated with build and test status in real time. JetBrains states that roughly 99% of projects need no plugins because popular tools are supported out of the box.

Frequently asked questions about JetBrains TeamCity Cloud

How does TeamCity Cloud's committer-based licensing work?

Billing is based on committers — users who author 10 or more VCS changes within a 30-day period. Managers, QA staff, and other non-committing users get unlimited free access to the web interface. Each committer slot includes 8,000 build credits, 40 GB of storage, and 200 GB of data transfer.

What happens to unused build credits each month?

Build credits included with your committer slots that remain unused expire at the end of each month, and a fresh allocation is granted. These credits are spent on build time on JetBrains-hosted agents and can also be redeemed for storage, data transfer, or concurrent self-hosted build slots. Credit packs purchased separately do not expire.

Can I connect my own build agents to TeamCity Cloud?

Yes. You can install TeamCity agents on your own Windows, Linux, or macOS machines and connect them using a generated authentication token. Each self-hosted agent requires a concurrent build slot rather than consuming build-credit minutes, and TeamCity gives self-hosted agents priority over JetBrains-hosted ones to keep build costs down.

Is the TeamCity AI Assistant available in TeamCity Cloud?

The in-product AI Assistant launched first for TeamCity Enterprise subscribers, with the Cloud rollout following afterward. It gives context-aware help inside the TeamCity UI for learning features and troubleshooting builds. Check your TeamCity Cloud instance for current availability, since JetBrains ships Cloud updates more often than On-Premises releases.