Developer toolsTravis CI at a glance
Pros
- Single .travis.yml file makes pipelines easy to read and version
- Build matrices test many language versions and environments in parallel
- Unlimited plan offers unlimited build credits for standard VMs from $78 a month
- Partner queues for IBM Power and Z architectures are free for open-source projects
- Self-hosted Travis CI Server option for on-premise or private cloud
Cons
- Credit and user-licence billing is hard to predict
- Free trial plans are currently unavailable
- Generous free open-source builds were cut back after 2020, upsetting many maintainers
- Smaller integration ecosystem than GitHub Actions or GitLab CI
- Review sites show mixed views on value and support
What Travis CI is
Travis CI is a hosted continuous integration and continuous delivery (CI/CD) service. When you push code or open a pull request, Travis CI spins up a fresh virtual machine or container, installs dependencies, runs your tests and can deploy the result. Every pipeline is described in a .travis.yml file stored in the repository.
Travis CI grew out of the open-source community in 2011 and was for years the default CI service for public GitHub projects. Idera acquired it in 2019. Today it supports repositories on GitHub, GitLab, Bitbucket and Assembla, and also offers Travis CI Server for self-hosted installations, which adds Perforce and Subversion support.
Who Travis CI is for
Travis CI fits teams that want a simple, hosted CI service independent of their Git host, projects with existing .travis.yml configuration, and organisations that need to test across several operating systems and CPU architectures, including IBM Power and Z through partner queues.
Teams starting from scratch on GitHub or GitLab should compare it carefully with GitHub Actions and GitLab CI, which are built into those platforms and include free minutes. Enterprises with strict data residency needs can consider the self-hosted Server edition.
Key features
Configuration is the main appeal. A short YAML file declares the language, versions, install and script steps, and deploy targets. Build matrices run the same tests against several language versions, operating systems or environment variables in parallel, which is valuable for libraries that must support many platforms.
Travis CI runs builds on Linux, FreeBSD and Windows. Premium VM sizes provide more CPU and RAM for heavy builds, and GPU VMs are available for machine learning workloads on Linux. Partner queues for IBM ppc64le and s390x architectures cost nothing for open-source repositories.
Usage-based plans have very high concurrency limits, starting at 80 concurrent jobs on the $15 plan, so builds rarely wait in a queue. The Unlimited plan covers unlimited standard build minutes, collaborators and repositories, with 1 to 300 concurrent jobs depending on the tier you buy.
Other features include build caching, debug mode for investigating failed jobs, build insights, deployment providers for common clouds and package registries, and Travis AI support for help inside the product.
Pricing explained
The Usage Based plan costs $15 a month for 35,000 Linux build credits, enough for roughly 3,500 standard Linux minutes. Users are charged separately in credits, so this plan suits individuals and very small teams with modest build volume.
The Unlimited plan starts at $78 a month and removes credit charges for standard VMs and per-user charges, which makes costs predictable for teams that build often. Premium VMs still use credits. Server, the self-hosted edition, starts at $34 a month, and teams of 20 or more can ask for volume discounts.
The credit model is the most common source of confusion. Builds stop when credits run out unless auto-refill is on, and a busy month with many contributors can drain the balance faster than expected.
Controlling costs
Three settings make the biggest difference to a Travis CI bill. First, restrict which users and events can trigger builds in each repository, because every new committer in a month can consume a user licence. Second, cancel redundant builds on superseded commits and avoid running the full matrix on every branch. Third, use caching for dependencies so each job spends fewer minutes installing packages.
Teams that still struggle to forecast usage should compare the Unlimited plan, which removes standard credit and user charges, with the total they spend on credits over three months. For steady, heavy workloads it is usually the cheaper and calmer option.
Ease of use and setup
Getting started involves signing in with your Git provider, activating repositories and committing a .travis.yml file. Reviewers on Capterra describe setup as quick compared with self-hosted tools such as Jenkins, with no servers to maintain.
The harder part is billing. Plan types, credits, user licences, OSS credits and concurrency rules are documented at length, and some reviewers report confusing errors when linking or unlinking Git accounts.
Integrations
Travis CI integrates natively with GitHub, GitLab, Bitbucket and Assembla, posting build status to pull requests. It supports deployments to many cloud providers and registries, notifications to Slack and email, and code coverage services such as Codecov.
Its ecosystem is smaller than GitHub Actions, which has a large marketplace of reusable actions. Reviewers note that Travis offers less flexibility than Jenkins for custom integrations.
Support and reliability
Support includes the Travis AI assistant, ticket-based support and premium support options. The public status page and community forum provide updates.
Trust took a hit during the 2020 to 2021 move from travis-ci.org to travis-ci.com and the switch to credit-based pricing. Capterra reviewers describe builds silently failing for lack of credits and open-source maintainers struggling to obtain OSS credits. The billing system is more mature now, but those experiences still shape its reputation.
What users like and dislike
Travis CI holds a 4.1 out of 5 rating on Capterra from about 130 reviews, with lower scores for value for money and customer service than for ease of use. TrustRadius gives it 7.3 out of 10. Users like the simple configuration, build matrices, caching and quick setup.
Complaints focus on the pricing changes, the credit model, reduced free access for open source, slower operating system image updates and support responsiveness.
Our verdict
Travis CI is still a capable, easy-to-configure CI service, and the Unlimited plan gives predictable costs for teams with heavy build volume. It also stands out for multi-architecture testing and offers a self-hosted edition.
For new projects on GitHub or GitLab, built-in CI is usually cheaper and better integrated. Choose Travis CI if you already depend on it, need its architecture support, or prefer a CI service that is separate from your code host.
Travis CI scores 6.7 out of 10 overall. Its strongest criterion is ease of use (7.5/10) and its weakest is value for money (6/10).
Travis CI pricing
| Plan | Price | What you get |
|---|---|---|
| Usage Based | $15/mo | 35,000 Linux build credits a month, 80 concurrent jobs, per-user licence charges, premium VMs available |
| Unlimited | From $78/mo | Unlimited build credits for standard VMs, unlimited collaborators and repositories, 1 to 300 concurrent jobs |
| Server | From $34/mo | Self-hosted on-premise or private cloud, Perforce and Subversion support, premium support options |
| Volume / custom | Custom quote | Discounts for teams with 20+ users and larger build needs |
Prices come from the Travis CI pricing page and billing documentation, read on 21 November 2026. Prices are shown before VAT and local taxes.
On usage-based plans, credits pay for build minutes: 10 credits a minute for standard Linux or FreeBSD, 20 for Windows, 20, 40 and 80 for large, x-large and 2x-large Linux VMs, and 230 or 890 credits a minute for GPU VMs. The $15 plan's 35,000 credits therefore cover about 3,500 standard Linux minutes.
Each unique person whose commit or pull request triggers a build counts as a user licence for that month. By default a licence costs 25,000 credits per user unless the plan includes users, so a team of several committers can use up the included credits quickly. Limit who can trigger builds in repository settings to control this.
Unused paid credits expire after 12 months. Annual usage plans give 12 months of credits for the price of 11. Credits can be bought on demand or auto-refilled, and builds stop when the balance runs out.
Free trial plans, which used to give new users 10,000 credits for 14 days after a $1 card check, are listed as currently unavailable. Open-source maintainers can request OSS-only credits case by case.
Prices in US dollars, checked on Nov 21, 2026. Confirm on Travis CI's own site before you buy.

