TeamCity Professional
JetBrains CI/CD server with powerful build pipelines, test reporting, and Docker support. Free Professional tier for commercial use.
Best for teams using JetBrains IDEs who want a powerful self-hosted CI/CD with excellent test reporting and IDE integration.
Use Cases
Free Tier
100 build configurations, 3 build agents, unlimited users, all features, commercial use allowed
How to Maximize the Free Tier
TeamCity Professional is free forever with 100 build configurations and 3 parallel agents — no feature limitations, no user caps, and commercial use is permitted. Maximize it by using build chains to split complex pipelines into reusable steps, leveraging built-in test reporting with flaky test detection, and setting up the Docker runner for containerized builds without extra config. Use personal build triggers for developer-specific branches to avoid cluttering the main queue. The 100-configuration limit is per server, so combine related builds into pipeline chains to stay under the cap. Since it's self-hosted, allocate at least 4GB RAM to the server for smooth operation.
Getting Started
Download TeamCity from jetbrains.com/teamcity/download → run the installer (or use Docker) → access the web UI at localhost:8111 → complete the setup wizard → create a project → connect your VCS (GitHub, GitLab, Bitbucket) → add build steps (build, test, deploy) → configure build triggers (VCS trigger, schedule, manual) → run your first build and review the test reports.
Pros
- Free for commercial use: No feature limitations, unlimited users, and no time limit — rare for enterprise-grade CI/CD tools
- Test intelligence: Built-in test reporting with flaky test detection, test history, and code coverage integration out of the box
- IDE integration: Deep integration with IntelliJ IDEA and other JetBrains IDEs for a seamless development-to-deploy workflow
Cons
- Self-hosted only: Professional tier is self-hosted only — you manage servers, backups, upgrades, and maintenance yourself
- Configuration limit: 100 build configurations per server can be restrictive for large organizations with many projects
- Resource intensive: Java-based server requires significant memory (4GB+ recommended) — not ideal for small VPS instances