What it does
TeamCity Cloud is JetBrains’ hosted CI/CD product. Its Cloud documentation describes build configurations as sequences of build steps with triggers, parameters, features, and agent requirements; it also supports storing versioned settings in Kotlin DSL.
A build configuration can be edited through the UI or maintained as Kotlin DSL alongside the code. The DSL can be versioned, and its static typing enables IDE completion. When a team starts a new project, decide whether it needs a classic build configuration or a pipeline: the Cloud guide describes these as different objects and says they cannot be converted after creation.
The pricing page opened during research returned only a minimal page shell, so current Cloud plan terms and prices remain unknown. JetBrains also offers TeamCity On-Premises, a separate deployment choice not covered by this entry.
Strengths
- Build configurations can define steps, triggers, parameters, and agent requirements.
- Kotlin DSL can keep TeamCity settings in version control and provides IDE completion through Kotlin’s static typing.
Watch out for
- Build configurations and pipelines have different structures and execution behavior, and cannot be converted into one another once created.
Best for
- Teams that want a hosted CI/CD service with configurable build steps and triggers.
- Teams that prefer to version TeamCity project settings as Kotlin DSL alongside their code.
Sources
- TeamCity | CI/CD solution by JetBrains (Oct 25, 2026)
- Creating and Editing Build Configurations | TeamCity Cloud Documentation (Oct 25, 2026)
- Kotlin DSL | TeamCity Cloud Documentation (Oct 25, 2026)
- Buy TeamCity: Pricing and Licensing, More Build Agents (Oct 25, 2026)