Travis CI review

The entry plan is priced at $15, and that is the number to set your budget against. For context, the €10.33 entry mark across automation tools sits above it, so Travis CI opens below the middle of the group rather than at the premium end.

No. Travis CI has no free plan, so there is no cost-free way to see the pipeline run. The cheapest way in is the entry plan at $15, and every build counts against the 35000 build credits per month allowance.

Usage is capped at 35000 build credits per month, which gives you a fixed monthly ceiling to plan against. If your team ships many commits across several repositories, that credit pool is the number that decides whether $15 is enough or whether a larger plan is needed.

Support runs on email, help centre and community, so help comes by email, the help centre and community answers rather than a live chat line. That works well for developers who are comfortable searching documentation, and it is a familiar setup in this group.

Travis CI is listed as an automation tool, so it fits teams whose main job is getting builds and pipelines to run without local setup. Teams with steady commit volume will get value from the 35000 build credits per month allowance, while teams with occasional work would pay for credits they might not use.

Entry prices across the automation group sit around €19.65 in the middle, with €34.20 at the upper end. At $15, Travis CI lands below most of the field, which is where the cost score of 6 comes from.

The listing gives a single figure, $15, with no separate renewal amount, so plan for that as the recurring cost rather than a first-period offer. If your build volume grows past 35000 build credits per month, the bill moves because of usage, not because of a listed renewal step.

IFTTT opens at $2.99 and Infloww at $40, so both sit away from $15. IFTTT is the cheaper starting point for simple trigger automation, while Infloww asks more, and Travis CI falls between the two on entry price.