CI/CD
Compare CI/CD platforms for continuous integration, continuous deployment, and build automation.
18 results in CI/CD
Active Pro listings from this category appear first. Your sort applies within Pro and Free results.
Shortlists for CI/CD
Explore collections with tools relevant to this category, grouped by deployment, source model or workload.
Open-source CI/CD tools for engineering teams →
12 matching tools from this category
Self-hosted IT tools →
14 matching tools from this category
IT tools with an API →
14 matching tools from this category
How to choose ci/cd tools
CI/CD tools take a commit, build it, run its tests and move the result toward production through repeatable pipelines. This category spans hosted pipeline services, self-hosted automation servers, release orchestrators that manage environments and approvals, GitOps controllers for clusters, monorepo build systems and artifact repositories. It differs from version control, which stores the code, and from PaaS products, which run the finished application rather than the pipeline that ships it.
Who uses these tools
- DevOps and platform engineers
- Developers maintaining build pipelines
- Release managers coordinating environments
Capabilities to compare
- Pipeline definitions stored in the repository
- Hosted versus self-hosted runners and agents
- Build caching and affected-only test runs
- Deployment strategies, approvals and rollbacks
- Artifact and package repository integration
Operating considerations
- Runner compute minutes are the main cost driver
- Secrets exposure in build logs and forks
- Pipeline syntax ties you to one tool
- Self-hosted runners need patching and isolation
Selection checklist
- List your languages, build targets and operating systems, then confirm each one has supported runners or images.
- Run one real pipeline end to end and measure queue time, build time and cache hit rate.
- Check how secrets are stored, masked in logs and restricted for pull requests from forks.
- Estimate monthly cost from your actual commit volume, concurrency needs and runner minutes.
What belongs in this category: A product belongs here when its main job is building, testing, packaging or releasing code automatically on each change, rather than hosting repositories, running applications in production or monitoring them afterwards.
CI/CD on iThub in figures
iThub lists 18 tools in CI/CD. 12 of 18 are open source, 14 of 18 can be self-hosted, 17 of 18 have a free, freemium or open-source pricing model and 14 of 18 offer an API.
- Tools listed
- 18
- Open source
- 12
- Self-hostable
- 14
- Free to start
- 17
- With an API
- 14
- Web app
- 12
- Desktop app
- 8
Recently added: Terrateam (Stategraph Orchestration), Keyshade, GitLab, Atlantis
Typical use cases
- Running tests automatically on every pull request
- Building and publishing container images and packages
- Promoting releases through staging and production environments
- Syncing cluster state from a Git repository
Trade-offs to model
- Hosted pipelines remove server upkeep, while self-hosted servers give full control over network access, hardware and data residency.
- A single delivery platform simplifies governance, whereas pairing a lean CI tool with a separate release tool lets each part be replaced independently.
- Plugin-heavy automation servers adapt to almost anything but accumulate upgrade risk as the plugin count grows.
Common mistakes
- Copying pipeline definitions between repositories instead of using shared templates, which multiplies maintenance with every change.
- Granting deployment credentials to every pipeline job rather than only to the protected release stage.
- Ignoring flaky tests until developers stop trusting red builds and start rerunning them blindly.
Browse open source CI/CD tools →Version control and code hosting →Browse all CI/CD tools →
Continue the technical evaluation
Use the resources that match your decision stage. Profile data and linked sources were refreshed through November 11, 2026.
