Overview
TeamCity is a continuous integration and continuous delivery server from JetBrains, the same vendor behind IntelliJ IDEA, PyCharm, ReSharper, and Kotlin. First released in 2006, TeamCity has long been recognised for the polish of its web UI, the depth of its build agent management, and tight integration with JetBrains IDEs. The product is available in three forms: TeamCity On-Premises (self-hosted), TeamCity Cloud (managed by JetBrains), and the newer TeamCity Pipelines (preview, configuration-as-code first).
TeamCity has historically punched above its weight against Jenkins for organisations that value out-of-the-box experience and a maintained vendor relationship. It has a smaller plug-in ecosystem than Jenkins but a noticeably higher baseline quality and a paid commercial roadmap. The 2024.x line introduced an OpenTelemetry tracing exporter, the new Kotlin DSL configuration improvements, and expanded MCP integration with JetBrains AI Assistant. TeamCity remains particularly strong for .NET and JVM teams that need build chains with complex dependencies, parallel testing matrices, and rich artefact retention policies.
Key Features
- Configuration-as-code via Kotlin DSL, with import from existing UI configurations
- Build chains, snapshot dependencies, and parallel test splitting across agents
- Polished web UI with build history, test history, code coverage, and flakiness detection
- Native integration with JetBrains IDEs (build status in IDE, remote run, pre-tested commit)
- Versioned settings in VCS for full audit and rollback
- Build agents on Linux, Windows, macOS, ARM, and Docker; cloud agents on AWS, Azure, GCP, Kubernetes
- Self-hosted runners with auto-scaling cloud agents
- Comprehensive REST API and webhooks for integration with internal tooling
- Project and build configuration permissions, audit log, and per-project agents
- SAML 2.0 SSO, LDAP, and AD integration (Enterprise tier)
- OpenTelemetry export for pipeline observability in Datadog, Honeycomb, Grafana
- TeamCity Cloud: SaaS with included build minutes and no infrastructure operations
Pricing
| Edition | Model | Cost |
|---|---|---|
| TeamCity Professional (on-prem) | Self-hosted, free | $0 (up to 100 build configurations, 3 build agents) |
| TeamCity Enterprise (on-prem) | Annual subscription | From $2,749/year for 3 agents and unlimited build configurations; scales by agent |
| TeamCity Cloud | Monthly or annual subscription | From $45/month for 3 committers, 24,000 build credits |
| Additional Cloud build credits | Pay-as-you-go | $0.01–$0.04 per build credit depending on tier |
Pricing verified May 2026 on jetbrains.com. JetBrains offers significant discounts for open-source projects, startups, classroom use, and All Products Pack subscribers. Annual contracts for self-hosted Enterprise scale linearly by build agent count.
Strengths
- Best-in-category UI and developer experience among on-premise CI servers
- Kotlin DSL is a more ergonomic configuration-as-code than YAML for complex pipelines
- Out-of-the-box build chain visualisation and flaky test detection
- Tight integration with JetBrains IDEs for engineering teams already on those tools
- Strong on-premise story without the operational burden of Jenkins
- OpenTelemetry export gives first-class observability into pipeline performance
Limitations
- Plug-in ecosystem is significantly smaller than Jenkins or GitHub Actions
- TeamCity Pipelines (the modern config-as-code first product) is still in active preview
- Cloud edition build credits can be expensive for high-volume CI workloads
- Community visibility and shared examples are smaller than GitHub Actions or GitLab
- No native security scanning suite — relies on integrations with Snyk, SonarQube, Checkmarx