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 $69/month


• 1, 2, and 5 concurrent plans with unlimited users

• 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 defines the Core Concurrency based plans?

Concurrency based plans are much like what Travis CI has been offering already for a long time: an ability to run a build consisting of X concurrent jobs. In Travis CI builds are executed singularly, without exceeding limitations. Therefore, if executing multiple builds at the same time or executing a build with multiple build jobs, once the concurrency limit is reached, the reminder builds/jobs must wait until there is a queue capacity available for processing.

Linux, Windows, and FreeBSD builds are included in the price of these plans. The macOS builds are paid separately on concurrency plans and can be run after purchasing the separate credits add-on. Credits are used to pay for each build job minute on macOS. Purchase only the credits you need and use them until you run out.


What if we need more than a 5 job concurrent plan?

For the majority of users, a 1, 2, or 5 job concurrency based plan should be sufficient. However, if you are running a large number of builds or users and concurrency becomes a bottleneck, please contact Travis CI asking for an Enterprise Cloud Usage based plan.


What defines an Enterprise Usage-based plan with credits and user licenses?

The Usage based plan charges users and organizations depending on the number of minutes each of the build jobs run on Travis CI infrastructure. The Usage based pricing model bills based on minutes used (via credits) and the number of users executing those builds (via user licenses). Users and organizations can run as many build jobs as they want at the same time, meaning that all builds are executed as soon as possible without limitations.

The final cost is flexible and closely related to the actual usage of the system, allowing you to scale, as per your needs.



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 more flexible, usage based plans please contact us.


Do the listed prices include VAT?

Prices listed excluding 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).

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