TeamCity is JetBrains' commercial CI/CD server, free as TeamCity Professional within build configuration and agent limits and licensed per agent as Enterprise; these pages cover replacing it with Jenkins, Woodpecker CI or GitLab CI/CD.
Comparing TeamCity with Jenkins for self-hosted CI: Kotlin DSL against Jenkinsfiles, build chains against pipeline stages, bundled features against plugins, agent licensing against unlicensed agents, and the operating work each server needs.
Comparing TeamCity with Woodpecker CI: when a lightweight container-based engine is enough for Linux builds on GitHub, Gitea, Forgejo, GitLab or Bitbucket, and when TeamCity's build chains, IDE integration and Windows agents still matter.
Comparing TeamCity with GitLab CI/CD on self-managed GitLab: a standalone CI server against CI built into the forge, build chains against parent-child pipelines, agents against GitLab Runner executors, and licensing on each side.
Moving TeamCity projects to Jenkins: using versioned settings in Kotlin DSL or XML as the inventory, mapping build configurations, build chains and snapshot dependencies to Jenkinsfile stages, templates to shared libraries, and agent requirements to labels.
Cost of ownership by component: TeamCity Enterprise and agent licenses, Enterprise Plus true-up billing and the free Professional tier, against Jenkins servers, agents, plugin maintenance, migration and support.
TeamCity Professional stops at 100 build configurations, 10 pipelines and 3 agents, and blocks new builds when agents exceed licenses. This page weighs buying Enterprise or agent licenses against moving to Jenkins or Woodpecker CI.
Getting projects out of TeamCity: enabling versioned settings to commit a .teamcity directory in Kotlin DSL or XML, build history, artifacts and logs, parameters and secure values, and turning the export into a migration inventory.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.