With our new usage based pricing, you pay only for the number of developer collaborators you need to build CI/CD pipelines and reviewing builds. Plans start at 1,000 build minutes and have unlimited repositories. You can buy additional minutes as needed. If you need to add more collaborators to your plan, your pricing scales up $15 per month for each user.
Travis CI has been offering fixed price plans by default for many years. These plans offer unlimited build minutes, collaborators, and repositories, but limit the number of concurrent CI/CD jobs. Once you reach the concurrency limit, Travis CI queues up additional jobs to run automatically after those in progress finish processing.
With the choice of two pricing structures—and the ability to change your plan based on how your organization and its applications grow—Travis CI offers the most flexible and developer-friendly pricing in CI/CD.
Absolutely—and you’ll unlock a free month of service as our thanks for doing so. Pick the annual option on the pricing page if you’re signing up for the first time. If you already have an account, log in and visit the billing dashboard.
Yes! We have usage based and fixed price plans to fit your organization and projects. You can change your plan subscription on the billing page at any time, or contact us if you’re looking for custom resources.
For on-premises installations, please contact sales
If you’re on a usage based plan, your subsequent builds are queued up in the Travis CI system until you have sufficient credits.
You can enable auto-refill or purchase a credits add-on in the Travis CI dashboard at Settings -> Plan -> Credits. If you’re curious about Travis CI’s pricing models, we also have a pricing calculator for full transparency into your monthly or annual investment.
If you regularly run out of build minutes before they are recharged at the beginning of each billing cycle, please email our support team to design a collaborator-based plan that’s right-sized for your needs.
Yes! If you’re a student, please see our education page for details about our program. You’ll need to connect your GitHub account to their Education program to activate your build minutes and single concurrent job.
We validate open-source projects on a case-by-case basis. We support actively maintained projects that are not wholly supported by corporate donations or development time. After creating your account, contact the support team with the following information: your Travis CI account name, VCS provider and the number of build minutes your pipelines requires.
Please see our billing-specific FAQ for more details. For everything else, please contact us.
Yes. Every commit triggers a build, composed of one or more jobs, by default. If you’re on a concurrency-based plan, Travis CI will queue up jobs and run them
If you’re having trouble dealing with concurrency limits due to the volume of active developers and their commits, you can implement measures to control build triggering, like limiting to specific branches or managing repository collaborators.
Every build has 120 minutes to run before the platform cancels it and discards the VM. If your builds require more time, split or parallelize jobs using the build matrix.
Travis CI was purchased by Idera, Inc. in 2019. Idera owns a portfolio of developer-centric tools including APILayer, Embarcadero, Assembla, Yellowfin, and more, and is actively investing in Travis CI’s people and platform to further improve its simplicity, extensibility, and resilience for CI/CD pipeline of all sizes. Learn more about Idera on our website.
Travis CI is GDPR- and Privacy Shield-certified and works only with compute/storage partners with SOC 2 Type 2 or ISO 270001 certifications, like AWS and Google Cloud Platform. We were the first CI/CD platform in the cloud to isolate every build and start each build with clean VMs, and we have since deployed extensible new tools to help you secure your CI/CD pipelines. For full details, see our site security page.
