Travis CI 2026: Benefits, Features & Pricing

On this page

Overview
Pricing and Plans
Features
Integrations
User Reviews

Overview

Travis CI

4.1

(129)

Pricing

Starting at $69.00 per month

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 Screenshots

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

User.com

GitHub

Travis CI User Reviews

Overall Rating

4.1

Ratings Breakdown

47%

29%

17%

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

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

Ease of use

Value for money

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).

Nicholas C.

Verified reviewer

Education Management

Self-Employed

Used daily for more than 2 years

Review source

Reviewed February 2021

Easy-to-use product but support for OSS failing

Ratings Breakdown

Ease of use

Value for money

Customer support

Functionality

Pros:

I like how easy it is to deploy and get up and running with this software and configuration files, etc (e.g. it's essentially just a commandline which is nice). It was also really nice for all of my open-source projects while travis-ci.org was still running. I could deploy and have builds run without having to worry about money.

Cons:

Ever since the move to travis-ci.com, support has been terrible and I've used up all of my free trial credits on my open-source web application's Cypress integration tests (https://github.com/tutorbookapp/tutorbook). I contacted support 5 days ago and still haven't heard back about getting more open-source credits for my account. I seriously miss travis-ci.org (though I completely understand the problems with cryptocurrency mining, etc).

Reasons for switching to Travis CI

I had used TravisCI earlier for building and deployments so I already knew how to use it. I decided to switch back to using TravisCI because CircleCI's configuration just took waaaaay too long to learn and implement correctly.

Nicolas P.

Verified reviewer

Internet

2-10 employees

Used daily for more than 2 years

Review source

Reviewed June 2021

Loved Travis in the past, sad to be on my way out.

Between the cons described above, the service degradation I've observed in the past 6 months and your recent organizational and pricing changes (we are an open-source project and directly impacted), I'll be setting up Github actions to run my CI tests from here onwards (this is also about standardizing with other projects in my organization) and will deactivate my travis account.

Ratings Breakdown

Ease of use

Functionality

Pros:

It worked really nicely until about 6 months ago ! The previous unlimited open-source plan was generous, and a huge selling point.

Cons:

Service has been less than ideal since the decision to move OSS projects travis-ci.org. We have felt this throttling of resources, and it was an indication that things were about tho change for the worse. I was surprised to find that from one day to the next my CI builds weren't being run anymore. Sure enough, you had a banner announcing the change from travis-ci.org to .com , but I didn't understand it would require changes on my side, and I didn't receive an email letting me know that my CI builds would just stop if I didn't manage it. I'll admit my fault in not checking more thoroughly. Moving from .org to .com was not as easy as I would have liked (Why do I need to sign up for a beta? Why is it in beta, and why do you need more decisions from me that I don't have all the information to decide?), but I eventually got there.

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

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

Ratings Breakdown

Ease of use

Value for money

Customer support

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.

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

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

Ease of use

Value for money

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.

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

I feel disappointed by the pricing change

Ratings Breakdown

Ease of use

Value for money

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.

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

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

Ratings Breakdown

Ease of use

Value for money

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.

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.

Ratings Breakdown

Ease of use

Value for money

Customer support

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.

Ondřej P.

Verified reviewer

Computer Software

51-200 employees

Used daily for more than 2 years

Review source

Reviewed February 2021

Past Glory

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

Ease of use

Value for money

Customer support

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.

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

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

Ratings Breakdown

Ease of use

Value for money

Customer support

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.

Showing 1 - 10 of 129 Reviews

See All Reviews