# Travis CI Software Reviews, Demo & Pricing - 2026

> Review of Travis CI Software: system overview, features, price and cost information. Get free demos and compare to similar programs.

Source: https://www.softwareadvice.com/continuous-integration/travis-ci-profile

---

[Home](https://www.softwareadvice.com/)

/

[Continuous Integration Software](https://www.softwareadvice.com/continuous-integration/)

/

Travis CI

Software Advice offers objective insights based on verified user reviews and independent product and market research. When our advisors match you to a software provider, we may earn a referral fee.

Overview

[Reviews](https://www.softwareadvice.com/continuous-integration/travis-ci-profile/reviews/)[Alternatives](https://www.softwareadvice.com/continuous-integration/travis-ci-profile/alternatives/)

# Travis CI 2026: Benefits, Features & Pricing

On this page

-   Overview
    
-   User Interface
    
-   Popular Alternatives
    
-   Pricing and Plans
    
-   Features
    
-   Integrations
    
-   User Reviews
    
-   Popular Comparisons
    

## Overview

Travis CI

4.1

[(129)](https://www.softwareadvice.com/continuous-integration/travis-ci-profile/reviews/)

Pricing

Starting at $69.00 per month

Top Alternatives

### About Travis CI

Travis CI is a cloud-based continuous integration platform designed to help developers test projects and update production or staging as the tests pass. Key features include authentication, change management, role-based permissions, data synchronization, continuous deployment, custom development and testing management.

Teams using Travis CI can push their codes to the cloud platform and gain greater control over security by integrating the system with Github.com. The solution uses OAuth for authentication, which enables managers to sync user permissions to ensure team members only have access to the necessary repositories. Supervisors can use SAML and LDAP to manage user access. The platform utilizes a 'clean room', which lets businesses, where each build is run in a clean, new consistent environment.

## Travis CI User Interface

## Popular Travis CI Alternatives

Main Product

Travis CI

4.1

[(129)](https://www.softwareadvice.com/continuous-integration/travis-ci-profile/reviews/)

Ratings Breakdown

-   3.92Ease of use
-   3.86Value for money
-   3.32Customer support
-   4.16Functionality

Pricing

Starting at $69.00 per month

Alternative Product

[Jira](https://www.softwareadvice.com/project-management/atlassian-jira-profile/)

4.4

[(15398)](https://www.softwareadvice.com/project-management/atlassian-jira-profile/reviews/)

Ratings Breakdown

-   4.08Ease of use
-   4.28Value for money
-   4.20Customer support
-   4.44Functionality

Pricing

Starting at $7.91 per month

Alternative Product

[Cycloid](https://www.softwareadvice.com/cloud-management/cycloid-profile/)

5.0

[(2)](https://www.softwareadvice.com/cloud-management/cycloid-profile/#reviews)

Ratings Breakdown

-   5.0Ease of use
-   5.0Value for money
-   5.0Customer support
-   5.0Functionality

Pricing

Starting at €29.00 per month

Alternative Product

[GitHub](https://www.softwareadvice.com/project-management/github-profile/)

4.8

[(6181)](https://www.softwareadvice.com/project-management/github-profile/reviews/)

Ratings Breakdown

-   4.41Ease of use
-   4.63Value for money
-   4.34Customer support
-   4.66Functionality

Pricing

Starting at $4.00 per month

Alternative Product

[Jenkins](https://www.softwareadvice.com/continuous-integration/jenkins-profile/)

4.5

[(572)](https://www.softwareadvice.com/continuous-integration/jenkins-profile/reviews/)

Ratings Breakdown

-   4.13Ease of use
-   4.57Value for money
-   4.04Customer support
-   4.52Functionality

Pricing

Available upon request

Alternative Product

[GitLab](https://www.softwareadvice.com/project-management/gitlab-profile/)

4.6

[(1222)](https://www.softwareadvice.com/project-management/gitlab-profile/reviews/)

Ratings Breakdown

-   4.37Ease of use
-   4.49Value for money
-   4.20Customer support
-   4.57Functionality

Pricing

Starting at $29.00 per month

## Travis CI Pricing and Plans

Starting price: $69.00 per month

Free Trial

Free Version

Basic

$69.00

per feature, per month

No plan information available

## Travis CI Features

-   Popular features found in Continuous Integration
    
    Automated Testing
    
    Continuous Delivery
    
    Continuous Deployment
    
    Debugging
    
-   More features of Travis CI
    
    Access Controls/Permissions
    
    API
    
    Approval Workflow
    
    Authentication
    
    Build Log
    
    Change Management
    
    Collaboration Tools
    
    Configuration Management
    
    Continuous Integration
    
    Dashboard
    
    Data Synchronization
    
    KPI Monitoring
    
    Projections
    
    Quality Assurance
    
    Release Management
    
    Reporting/Analytics
    
    Role-Based Permissions
    
    Testing Management
    
    Version Control
    

## Travis CI Integrations

Project Monitor

Integration rated undefined from -1 review

Positive User

Integration rated undefined from -1 review

GitHub

Integration rated undefined from -1 review

## Travis CI User Reviews

Overall Rating

4.1

Ratings Breakdown

5

47%

4

29%

3

17%

2

2%

1

5%

Secondary Ratings

Ease of Use

3.9

Value for money

3.9

Customer support

3.3

Functionality

4.2

Ian M.

Verified reviewer

Internet

2-10 employees

Used monthly for more than 2 years

Review source

Reviewed February 2020

CI tool that has a lot of value for the money

5

I started using Travis initially because I needed a way to have consistent builds of our desktop software (built on Electron). Travis has just the tools I needed to make this happen. Doing local builds of the software was processor intensive, I had to go check the status of the build and I was always changing software on my local machine so sometimes builds would fail because I changed something. Travis has completely containerized build machines so you get the same result every time. We now use it for building all our software. I don't know what we'd do without it.

Ratings Breakdown

4

Ease of use

5

Value for money

5

Functionality

Pros:

\* Affordable (it's priced based on users/seats) \* Documentation is solid and easy to follow. I've never needed to contact support. There's good online Q&A since Travis has a large user base. \* Versatile (whatever software you're building, there's a recipe for it) \* Github integration : you get realtime build status RIGHT in Github which is awesome, once you get your system set up, you rarely ever visit Travis again. It just works.

Cons:

There's really nothing I didn't like about Travis. Some of the quirks of Electron were the trickiest things to figure out, but that's not Travis's fault. There's a little learning curve when you go from building locally to building remotely with Travis where you need to understand how to set environment variables and retrieve those values in your config/script.

Reasons for choosing Travis CI

We didn't look at other options. Circle CI would have been the likely comparison but I don't think at the time we made the selection there was much online about Circle CI supporting Electron builds. It may have been possible, but the Electron community was definitely more affiliated with Travis CI. We knew we wanted something hosted, so we didn't look at Jenkins (which, I think, requires you to host and manage it yourself).

Read More

ES

EMANUELE S.

Verified reviewer

Information Technology and Services

2-10 employees

Used daily for less than 2 years

Review source

Reviewed February 2021

CI / CD in a simple way

5

I'm very happy about Travis, until now I found always an answer for each need I had

Ratings Breakdown

4

Ease of use

4

Value for money

5

Customer support

5

Functionality

Pros:

1\. Documentation, maybe the most important value 2. Configuration flexibility in particular GIT SSH custom keys, env variables with sensitive information, build trigger (with inline configuration... very useful for testing configurations), machine SSH encrypted keys, configuration imports, custom scripts 3. Easy integration with GitHub

Cons:

Permissions check (it's not so clear understand who can build, who can view build history, who can edit configuration).

Reasons for choosing Travis CI

I already knew TeamCity but there wasn't a cloud version when I choosed Travis. Ionic has a ready to use mobile app configuration and we use it. I never had enough time to setup a Travis configuration build successfully a ionic app.

Read More

MW

Matthew W.

Verified reviewer

Internet

1001-5000 employees

Used daily for more than 2 years

Review source

Reviewed June 2021

Static matrices and changes to OSS terms mean I cannot recommend the product

3

Our initial years with Travis were successful, and we were quite happy with the product. But over time, the lack of flexibility meant struggling to create and deploy our CI definitions. But the part that killed Travis for us was the change to OSS terms late in 2020. We'd already noticed that our queues would become long, particularly if we had many contributors or maintainers working simultaneously. But with the changes in terms, we quickly ran into a scenario where we ran out of hours by mid-month. This left us with an untenable situation; as an OSS project, we have limited funds, and we would quickly run through those if we purchased a plan. As a result, we are within 1-2 weeks of moving off the platform entirely.

Ratings Breakdown

3

Ease of use

2

Value for money

1

Customer support

2

Functionality

Pros:

When we first started using the product, it was one of the few that existed, and it provided us exactly the assurances we needed to have predictable, stable software releases. Idempotent runs made it possible to know exactly when and why something failed.

Cons:

Since we produce OSS libraries, it's important for us to test against each language version we support. Unfortunately, there is no way in Travis to dynamically create a matrix based on the library/package definition itself. For instance, we produce PHP libraries, and our package management solution, Composer, allows us to specify in the package the versions we support. Unfortunately, when we change those, we also need to remember to change the Travis definitions to reflect those changes. This becomes a source of error very quickly - Travis may report all is green, but it turns out we haven't added the new PHP version to the matrix, so it's a false sense of assurance. On top of that, it's impossible to succinctly make discrete jobs that do different things. For instance, I don't need to run coding standards checks, static analysis, and documentation linting for every single job in the matrix; I really only need to run these once. But to do that, Travis forces me to define env variables for jobs, and then use conditionals to determine what to run. This makes the CI definitions very convoluted, and, if you have a lot of repositories that need to do the same, hard to distribute when you have changes to make. Other CI systems address this.

Read More

GR

Griffith R.

Verified reviewer

Research

5001-10000 employees

Used monthly for more than 2 years

Review source

Reviewed March 2021

Largely self-taught, test driven developer

4

It's the core, it's the standard, and it does work fairly well. I'm kind of surprised it isn't as straightforwardly automatic to sort from GitHub, and there are some confusing elements to enabling it (and I don't quite understand why it's not more integrated with GitHub actions but maybe I'm wrong on that) but it's the standard, and automating test suits is crucial to good, maintainable code (especially if maintained by a community).

Ratings Breakdown

4

Ease of use

5

Value for money

3

Functionality

Pros:

It's free if your code is open source and lots of other services (like zenodo, netlify etc.) already sort out interoperability, usually a bit sooner than gitlab.

Cons:

It might be a lot quicker/better maintained for non-free use, but the options for testing packages in R, for example, are kind of weak and very slow (assuming the examples I've come across are standard). The fact that they only include python2 by default, plus some permission issues means packages using reticulate (for python/R interoperability) have a bit of a pain to get going (and it takes a long time to test). I guess if default options could be better maintained that would be much appreciated.

Reasons for choosing Travis CI

I didn't choose it, my employer did and to work with colleagues this was the only real option.

Read More

JD

Jiří D.

Verified reviewer

Computer Software

10000+ employees

Used daily for more than 2 years

Review source

Reviewed July 2021

My OpenSource projects got accustomed to free CI; Travis is no longer that

4

I feel disappointed by the pricing change

Ratings Breakdown

3

Ease of use

2

Value for money

3

Functionality

Pros:

Established service; Easy to configure; Supports macOS and AArch64 Linux

Cons:

Pricing structure for free and Open Source projects

Reasons for choosing Travis CI

It was one of the first services of this kind that was available. Afterwards, I never had a sufficient reason to make a switch.

Read More

TW

Thomas W.

Verified reviewer

Food & Beverages

Self-Employed

Used daily for less than 6 months

Review source

Reviewed February 2021

Great product - Pricing is insane for someone on a single team

5

Good experience - got hooked on the free trial, but it's time to move on as its costing an arm & a leg.

Ratings Breakdown

5

Ease of use

2

Value for money

5

Functionality

Pros:

I really like Travis CI, creating .travis.yml files is easy enough & I love the interface for seeing my build progress. That said I'll be moving off of this platform very shortly.

Cons:

The cost is insane - Azure DevOps offers pipelines for free, my AWS sites (5 of them) cost less to host than my Travis CI subscription, AWS has a DevOps implementation that is about $15/mo - even if Travis CI was at $20-$25/mo I would consider it as a solution.

Reasons for choosing Travis CI

I was working through a tutorial on AWS & this was offered as the CI / CD solution, since the trial was free I opted for it. Now that my project is in production though this pricing is my highest cost service & needs to be addressed.

Read More

Elliott L.

Verified reviewer

Computer Software

11-50 employees

Used daily for more than 2 years

Review source

Reviewed July 2019

Really simple to use continuous integration.

5

Ratings Breakdown

5

Ease of use

5

Value for money

5

Customer support

5

Functionality

Pros:

We use it to run php unit tests whenever we commit code to a repository. All we have to do is include a file in the root of the project and enable the project in the travis interface. Takes less than 5 minutes to set up fully automated unit testing. Much more easy than setting up your own CI pipeline with the huge amount of different apps that exists. Generous free tier.

Cons:

Can be slow at times, documentation can on occasion be more minimal than I would like. As a developer you get used to this though, there are always loads of examples online.

Reasons for choosing Travis CI

Travis works on all major providers.

Read More

Ondřej P.

Verified reviewer

Computer Software

51-200 employees

Used daily for more than 2 years

Review source

Reviewed February 2021

Past Glory

1

We started using Travis in September 2016. Over the years we used it for both CI and CD pipelines for most of our applications - we had about 300 pipelines. For many years it was a truly great service. Now days we're trying to move away as fast as we can.

Ratings Breakdown

5

Ease of use

2

Value for money

1

Customer support

4

Functionality

Pros:

Worked like charm years ago and did everything we ever wanted to. Neat debugging feature.

Cons:

In past 2 years Travis is dying in painful agony. The service is unreliable, sometimes not working for days. Status page is not updated at all. Support is non-existent - time to first response to an issue is a month now. Out of about 20 issues we raised in past year, not a single one was resolved.

Reasons for choosing Travis CI

It was much easier to use then Jenkins and was a great service in the past.

Read More

Bruce B.

Verified reviewer

Research

11-50 employees

Used daily for more than 2 years

Review source

Reviewed February 2019

Powerful, free and easy DevOps

5

Travis hasn't let me down yet. This services handles more than 90% of our builds.

Ratings Breakdown

4

Ease of use

5

Value for money

5

Customer support

5

Functionality

Pros:

Travis does a few things really well: 1. Documentation - the documentation is extensive and complete, and one never has the feeling that there are "hidden features" that only the power users know about. 2. Speed - waiting for more than a few seconds for a build to start is extremely rare. 3. Deploy integrations - builds can be deployed to a set of services easily. This is probably the easiest way to set up continuous deployment if you're on a tight budget.

Cons:

The build environment can be somewhat restrictive, forcing one to choose language-specific base images and not giving access to the underlying VM.

Read More

Charlie M.

Verified reviewer

Industrial Automation

10000+ employees

Used weekly for more than 2 years

Review source

Reviewed August 2021

Fair, but unclear

5

Good, but can be

Ratings Breakdown

4

Ease of use

4

Value for money

5

Customer support

4

Functionality

Pros:

Travis is the only ci tool that have VT-x enabled! It's also well known, simple to use.

Cons:

Paid compared to github action. At least it could be cool to have come montlhy free credits, for just a few to maintain some OSS project in RUN mode. Not so configurable: I can't come with my own VM ISO so I'm forced to download all prerequisite package every time for each builds: most of my credits go there... As I'm part of multiple orgs, it's hard to know which credits are spent where. Also, the authorization mecanism is not that clear: I don't know exactly what travis sees from my github infos.

Reasons for choosing Travis CI

No VT-x on the others: I use the others for my non VT-x test suites, so travis is not my first choice when looking at CI for OSS (and even company project where we have our own autoscaled gitlab runners.

Reasons for switching to Travis CI

Travis was free

Read More

Showing 1 - 10 of 129 Reviews

[See All Reviews](https://www.softwareadvice.com/continuous-integration/travis-ci-profile/reviews/)

## Travis CI Popular Comparisons

[GitHub vs Travis CI](https://www.softwareadvice.com/project-management/github-profile/vs/travis-ci/)[Jenkins vs Travis CI](https://www.softwareadvice.com/continuous-integration/jenkins-profile/vs/travis-ci/)[GitLab vs Travis CI](https://www.softwareadvice.com/project-management/gitlab-profile/vs/travis-ci/)[Bitbucket vs Travis CI](https://www.softwareadvice.com/ide/bitbucket-profile/vs/travis-ci/)[CircleCI vs Travis CI](https://www.softwareadvice.com/continuous-integration/circleci-profile/vs/travis-ci/)[SonarQube vs Travis CI](https://www.softwareadvice.com/continuous-integration/sonarqube-profile/vs/travis-ci/)

[Compare All Alternatives](https://www.softwareadvice.com/continuous-integration/travis-ci-profile/alternatives/)

## See what companies are saying about Software Advice