TeamCity vs Github Actions comparison of Continuous Integration servers

	TeamCity https://www.jetbrains.com/teamcity/	Github Actions https://github.com/features/actions
Unique feature	Technology awareness	Best GitHub integration possible
Type of product	On Premise	SaaS / On Premise
Offers a free plan	Yes They offer a great free professional plan, limited to 100 build configurations and 3 build agents. From there, you pay for each aditional agent you want (discounts if you purchase more than 1 agent at a time). They also provide a free plan for open source, non commercial projects, and steep 50% discounts for startups.	Yes The on premise plan (not yet available) will be free, 2000 build minutes included in the free cloud plan. Completely free plan for open source projects.
Predictable pricing	Yes They have a clear list of prices per number of agents.	Yes (partial) While it's clear what the cost is (priced per build-minute), figuring out costs can be a hassle, especially as the price can vary quite a bit depending on commits to the project. One advantage for GitHub Actions is that the tiers define a maximum amount of minutes, so it's easier to predict the final cost. You can also purchase aditional runners with pricing dependent on the platform (MacOS, Linux, Windows)
Support / SLA	Yes	Yes Community support available for any tier, unclear at what point and if dedicated support is available. Safe to assume that eneterprise clients can access technical support.
Paralellism Every CI servers tends to address this differently (parallel, distributed, build matrix). Some of it is just marketing, and some is just nuance. For this table, parallel means that tasks can be run concurrently on the same machine, distributed means that tasks can be scaled horizontally, on multiple machines How to split tests in parallel in the optimal way with Knapsack Pro	Yes	Yes Matrix builds allow concurrent jobs, even multi-platform.
Distributed builds distributed means that tasks can be scaled horizontally, on multiple machines How to split tests in parallel in the optimal way with Knapsack Pro	N/A No specific mention that we could find, but judging by the wording used it would appear that tasks can be divided accross different machines.	N/A No specific mention, but given the fact that tasks can be run on multiple platforms, it's likely that distributed builds are also available.
Containers support / Build environment	Yes First class Docker support, among others	Yes Linux, macOS, Windows, and containers, or run directly in a VM.
Analytics / Status overview Analytics and overview referrs to the ability to, at a glance, see what's breaking (be it a certain task, or the build for a specific project)	Yes Great system overview, even allows building your own dashboards in order to see everything you're interested in at a glance.	Yes Minimal status overview definitely available, with live logs and GitHub integration. Unclear how far it goes.
Management support How easy is it to manage users / projects / assign roles and permissions and so on	Yes Allows assigning roles, LDAP and Windows domain integrations and more.	N/A Unclear from the available documentation
Self-hosted option	Yes	Yes Coming soon, not available yet.
Hosted plans / SaaS	No	Yes
Build pipelines A continuous delivery pipeline is a description of the process that the software goes through from a new code commit, through testing and other statical analysis steps all the way to the end-users of the product.	Yes Unlike most options in the CI/CD space, TeamCity allows defining pipelines using a Kotlin-based DSL. This unlocks a lot of potential, such as templates for common CI/CD tasks, and deep integration with various IDEs (not just JetBrains IDEs)	Yes Called GitHub Action Workflows, they are defined in separate Docker containers, using the YAML syntax (they used to support HCL, but they're migrating away from that)
Reports Reports are about the abilty to see specific reports (like code coverage or custom ones), but not necesarily tied in into a larger dashboard.	Yes Something that stands out from the rest, allows integrating third party reports, as long as they produce HTML output.	N/A Unclear from the available documentation
Ecosystem Besides the official documentation and software, is there a large community using this product? Are there any community-driven tools / plugins that you can use?	Yes JetBrains has a rich ecosystem of plugins in general.	Yes Thanks to the large following, GitHub Actions already enjoys a wide varierty of available pre-made workflows, which you can browse right on the homepage: https://github.com/features/actions
Specific language support: Ruby Some CI servers have built-in support for parsing RSpec or Istanbul output for example and we mention those. Some others make it even easier by detecting Gemfiles or package.json and automate parts of the process for the developer.	Yes Using what they call 'Technology Awareness', promises great intehration with Ruby projects, with features such as testing framework support, static analysis and code coverage available out of the box, with no additional work required: https://www.jetbrains.com/teamcity/features/technology_awareness.html	Yes Unclear how, but they mention Ruby support specifically on the homepage
Specific language support: JavaScript	No (partial) Unlike Ruby, there's no first class support for Javascript, although they do advertise the fact that their large collections of plugins can cover any use case for Javascript projects: https://plugins.jetbrains.com/teamcity	Yes Unclear how, but they mention Javascript (Node.js) support specifically on the homepage
Integrations 1st party support for common tools (like Slack notifications, various VCS platforms, etc)	Yes Great cloud integrations (Google Cloud, AWS, VMWare, etc) as well as 'key' integrations (VSCode, Jira, even NuGet)	Yes Integrations made possible via the shared third party workflows available (AWS, Azure, Zeit, Kubernetes and many more)
API Custom integreation is available, via an API or otherwise, it's mentioned separately as it allows further customization than any of the Ecosystem/Integration options	Yes Unlike most tools, which offer just a Rest API, TeamCity provides ample opportunity for extension via plugins, their own API, and service messages (formatted messages on stdout)	N/A Unclear at the moment, but assume GitHub Actions will be integrated with the GitHub GraphQL API (one of the more mature GraphQL API implementations available)
Auditing	Yes	N/A
Additional notes	Great ecosystem, with a strong focus on integration with other tools (not only JetBrains).

TeamCity vs Github Actions comparison of Continuous Integration servers What are the differences between TeamCity and Github Actions?

TeamCity

Github Actions

Technology awareness

Best GitHub integration possible

On Premise

SaaS / On Premise

Yes

Yes

Yes

Yes (partial)

Yes

Yes

Yes

Yes

N/A

N/A

Yes

Yes

Yes

Yes

Yes

N/A

Yes

Yes

No

Yes

Yes

Yes

Yes

N/A

Yes

Yes

Yes

Yes

No (partial)

Yes

Yes

Yes

Yes

N/A

Yes

N/A

GitHub Actions testing Ruby on Rails with RSpec and parallel jobs (matrix feature)

How to run Jest tests on GitHub Actions - JS parallel jobs with matrix feature (NodeJS YAML config)

GitHub Actions Cypress.io E2E testing parallel jobs with matrix feature (NodeJS YAML config)

Github Actions parallelism integration

Start using Knapsack Pro with TeamCity or Github Actions

Sign up and speed up your tests.

TeamCity vs Github Actions comparison of Continuous Integration servers
What are the differences between TeamCity and Github Actions?