Streamline your CI/CD with Travis CI

Set up your first project in just one minute. No credit card required for Free Plan!

Free Trial

30-Day Free Trial 


10,000 credits

• Compatible with Assembla, Bitbucket, GitHub & GitLab

• Quick-start resources and guides


Starting at $30/month


Ability to run unlimited builds without any queuing of jobs

• Compatible with Assembla, Bitbucket, GitHub & GitLab

• Easy integrations


Custom Plans for Cloud and Self-Hosted Deployments


• Custom concurrency to keep
you building

• Availability of Demos and POCs

• Ability to run self-hosted

Not sure how to get started?

Compare Plans

Flexible Pricing
Adjustable Concurrency
Infrastructure: Arm, IBM, AWS, & more
VCS: Assembla, Bitbucket, GitHub, GitLab
Builds: Linux, Windows, macOS, FreeBSD
Open & Private Repositories
Cron Scheduling
High Availability

*Click the Contact Us button shown above or email us at to request a Self-Hosted/Enterprise Free Trial license. The Self-Hosted Free Trial License is fully-featured, and we would be happy to answer any questions as you get started to ensure your team’s success.

If there is a need for more than the default standard VM (2 vCPU, ~4GB RAM), the Core and Enterprise plans give you the option to run larger VM instance sizes.

Note: Available instance sizes can be selected for the following build jobs: Linux, Windows, and FreeBSD. CPU architecture is AMD64. Core plans may run larger VMs with the purchase of credit add-ons.

Pricing FAQs

What are Usage-based plans?

Travis CI now exclusively offers new cloud-hosted customers usage-based plans. Customers decide how many credits they wish to purchase upfront, then they use those credits during the subscription period. Credits are used to run builds and when new unique users trigger a build within a billing period. At the start of each new billing period (either monthly or annually), a new allotment of credits is granted based on the subscription amount. 

Due to variability in usage, customers are given the ability to customize the auto-refill of their credits within subscription periods. See FAQ “What if I run out of credits?” for further details.

What if I run out of credits?

There are two ways a customer on a usage-based plan can refill their credits in between billing periods: enabling auto-refill (available to auto-pay customers), or increasing the subscription size.

Auto-pay customers (those who have Travis CI Core plans) can enable the auto-refill feature at any time. New customers will have the feature enabled by default, while existing customers will need to enable it themselves. To enable auto-refill, go to: Settings -> Plan tab -> scroll down to the Credits section -> Credits tab. This feature is not available to Free Plan or custom Travis CI Enterprise cloud users. For more details, please read our documentation.

If the amount of credits purchased is quickly exhausted, it may mean that the chosen plan is not sufficient for the customer’s needs. Customers may increase the size of their subscription by going to Settings -> Plan tab -> Plan information section -> Change plan.

What if I do not use all my credits?

Credits that are unused during a subscription period are carried over to the renewed subscription. If the subscription is not renewed, the credits will expire one month after the subscription ends.

Can I pay for user licenses with credits under usage-based plans?

Yes! As of December 2021, Travis CI customers on usage-based plans may use credits to purchase both user licenses and build minutes. (Note: There are legacy usage-based plans where customers purchase users and credits separately.)

What is the per-user cost under usage-based plans?

The standard cost per month for 3 users is 25,000 credits (cost before any discounts), plus an additional 25,000 credits for each incremental user after the first 3. Each unique user that triggers a build during a calendar month is counted as one user for purposes of calculating the credit cost. User licenses reset at midnight GMT on the first day of each calendar month. 

Travis CI charges a per-user price under usage-based plans in order to cover the cost to support customers and provide new product enhancements.

What are Concurrency-based plans?

Concurrency-based plans were offered by Travis CI historically, and they are no longer offered to new or resubscribing customers. Concurrency plans provide customers the ability to run a set number of jobs at one time. A build is made up of multiple jobs, which means that concurrency limits can be reached due to the number of builds run at one time, the number of jobs within builds being run, or a combination of the two. When the concurrency limit is reached, the remaining builds/jobs must wait until capacity becomes available.

Linux, Windows, and FreeBSD builds are included in these plans. macOS builds on concurrency plans require the use of credits, which may be purchased as an add-on.

Can I pay annually?

You most certainly can! And you get 1 month for free – 12 months for the price of 11! Simply select the annual option when signing up for a subscription, or go to if you wish to switch your current plan to annual.

For a more flexible usage-based plan, please contact us.

Do listed prices include VAT?

Listed prices exclude VAT, which will be added depending on the purchaser’s country. Make sure to have your company’s VAT ID ready when entering billing details to remove VAT!

Am I able to upgrade my plan?

Yes! We have many plans available for your usage and concurrency needs. You can change your plan subscription at any time on the billing page or contact us if you’re looking for something custom.

Are there any restrictions on build time?

A build has 120 minutes to run. Should your build take longer, you can split it up using a build matrix.

Does every commit trigger a build composed of jobs?

Every commit triggers a build composed of jobs by default. Job concurrency limits are defined by the selected plan, or are set at a default 40 concurrent jobs for usage-based plans (reach out to discuss increasing this limit). There are several ways to control build triggering — e.g., by appointing branches, or managing repository collaborators.

See our documentation for more details.

Where can I check my credit balance?

You can check your credit balance by going to Settings -> Plan usage -> Credits. You can find a bar representing the subscribed credits pool and remaining credits. You can check the status of your Open Source Software (OSS) credits as well. 

How can I check how many credits I spent on builds and how many on user licenses?

Go to Settings -> Plan usage, then scroll down to see usage statistics. To download the data into a spreadsheet, click on “Download .csv file for more detailed information about usage” for information about credits spent on builds or Download .csv file for more detailed information about user license for information about credits spent on user licenses.

Have a question you don’t see answered above?
Our sales team are very happy to help.