Travis CI vs Heroku CI comparison of Continuous Integration servers

	Travis CI https://travis-ci.org	Heroku CI https://www.heroku.com/continuous-integration
Unique feature	Build Matrix, ease of use, GitHub integration	Heroku Flow
Type of product	SaaS, Self-hosted / On Premise	SaaS
Offers a free plan	Yes Free for open source projects	No (partial) For CI only, the cost starts at $10 for pipeline, plus a variable amount depending on how long the build runs for (prorated per second). The servers used for CI cost $250 for a full month, which means you get about 3 hours for $1. For hosting, there's a free tier, limited to 1 web/1 worker with 512 MB RAM. One of the more annoying limitations is that free dynos are put into sleep mode after 30 min. of inactivity, which increases loading times considerably.
Predictable pricing	Yes Clearly defined monthly plans, depending on concurrent jobs needed.	Yes Clearly defined, offers a calculator.
Support / SLA	Yes Available via email, or dedicated online interface for paid plans.	Yes
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 TravisCI makes it very easy to split your build into different stages which are then run in parallel (ie: run integration tests separate from the unit tests). TravisCI calls this a build matrix: https://docs.travis-ci.com/user/build-matrix/. You can also very easily split tests accross several VMs using the knapsack_pro gem.	Yes Up to 16 nodes. You can ask Heroku support to enable up to 32 parallel dynos.
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	N/A
Containers support / Build environment	Yes TravisCI runs each build in a isolated virtual machine. Pre-build packages include a few which support specific languages (Ruby and JavaScript included) or other software (Git, various databases), but vanilla packages such as Ubuntu Trusty are also available.	Yes Builds run in isolation on new dynos (Heroku containers). Wide support via buildpacks: https://devcenter.heroku.com/articles/buildpacks
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 Available by default in Travis (this is what most of the web UI consists of)	Yes Great visual overview built-in.
Management support How easy is it to manage users / projects / assign roles and permissions and so on	N/A	Yes One of the more mature solutions for teams on the market, Heroku Teams is available for free for 1-5 people, and comes at a cost for 6+ team members: https://www.heroku.com/pricing#team-comparison. Allows setting roles and app-level permissions with ease.
Self-hosted option	Yes	No
Hosted plans / SaaS	Yes	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.	No Specifically built around GitHub pull requests. Pipelines can be defined, but parts of the process need to be implemented separatelly in GitHub.	Yes Very easy and intuitive process that allows defining a pipeline from code commit, to code review (review apps), user acceptance testing and production deployment, via Heroku Flow. Works best if the project is also hosted on Heroku.
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 (partial) No persistent storage eliminates the possibility of code coverage reports on TravisCI alone. There is support for integrated 3rd parties such as Coveralls for reporting code coverage.	Yes
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?	No plugin support in TravisCI, plugins for other tools	Yes Wide array of 3rd party add-ons available via Heroku Elements: https://elements.heroku.com/addons. Custom buildpacks are also available for almost any stack you might be using (over 5500 buildpacks available at the moment)
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 TravisCI is designed to be a simple way to integrate CI/CD in your workflow so it has a couple of features aimed at specific languages, such as Ruby, starting from pre-built containers (with RVM already installed, for example) all the way to automatically running specific platform commands (such as detecting a Gemfile in the root of the project and automatically bundling dependencies). TravisCI also builds a Ruby SDK for easier use of the API.	Yes Although not specifically built in to Heroku, it's guaranteed that any Ruby specific need that might arise would be solved via add-ons, buildpacks or other integrations available.
Specific language support: JavaScript	Yes TravisCI is designed to be a simple way to integrate CI/CD in your workflow so it has a couple of features aimed at specific languages, such as Javascript, starting from pre-built containers (with node already installed, for example) all the way to automatically running specific platform commands (such as detecting a package.json in the root of the project and running npm test)	Yes Although not specifically built in to Heroku, it's guaranteed that any Javascript specific need that might arise would be solved via add-ons, buildpacks or other integrations available.
Integrations 1st party support for common tools (like Slack notifications, various VCS platforms, etc)	Yes By default, TravisCI is built to work with GitHub. Additionally, there is strong support for 3rd party tools like Coveralls, BrowserStack, etc.	Yes The strongest built-in integrations are with GitHub and Slack (ChatOps) but even allows integrating 3rd party CI servers in the workflow if you so require, among others.
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 Offers a feature-rich API that allows both reading data, as well as triggering or cancelling builds.	Yes Offers a feature rich API that allows CRUD operations on the most important features, such as promoting an app to production, or inspecting a specific pipeline.
Auditing	N/A	Yes
Additional notes

Programming Language	Supported test runners	Installation guide	Knapsack Pro Library README / Source
Ruby	RSpec, Cucumber, Minitest, test-unit, Spinach, Turnip	Install	knapsack_pro gem
JavaScript	Cypress.io	Install	@knapsack-pro/cypress
JavaScript	Jest	Install	@knapsack-pro/jest
JavaScript / TypeScript	Any test runner in JavaScript	How to build native integration with Knapsack Pro API to run tests in parallel for any test runner	@knapsack-pro/core
Any programming language	Any test runner	How to build a custom Knapsack Pro API client from scratch in any programming language	-

Travis CI vs Heroku CI comparison of Continuous Integration servers What are the differences between Travis CI and Heroku CI?

Travis CI

Heroku CI

Build Matrix, ease of use, GitHub integration

Heroku Flow

SaaS, Self-hosted / On Premise

SaaS

Yes

No (partial)

Yes

Yes

Yes

Yes

Yes

Yes

N/A

N/A

Yes

Yes

Yes

Yes

N/A

Yes

Yes

No

Yes

Yes

No

Yes

Yes (partial)

Yes

No plugin support in TravisCI, plugins for other tools

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

N/A

Yes

How to run parallel tests on Travis CI and Heroku CI to execute 1-hour test suite in 2 minutes?

Without Knapsack Pro

Run fast parallel CI build with Knapsack Pro

How it works

How to install it

Do you know

Start using Knapsack Pro

Sign up and speed up your tests.

Get faster feedback from Travis CI and Heroku CI server

Travis CI build matrix feature how to use it for CI parallelisation

How to leverage Heroku CI to run your tests faster?

Introduction to Knapsack Pro Heroku add-on

Travis CI parallelism integration

Heroku CI parallelism integration

Introduction to CI parallelisation with Knapsack Pro

How much can you save with faster tests on Travis CI and Heroku CI?

Features that make your tests perform better

Queue mode see video

Regular mode see video

Fallback mode

All supported test runners

Trusted solution

Start using Knapsack Pro with Travis CI or Heroku CI

Sign up and speed up your tests.

Travis CI vs Heroku CI comparison of Continuous Integration servers
What are the differences between Travis CI and Heroku CI?

How to run parallel tests on Travis CI and Heroku CI
to execute 1-hour test suite in 2 minutes?

How much can you save with faster tests
on Travis CI and Heroku CI?