Jenkins is one of the clearest examples of open-source software pricing: the platform itself is publicly positioned as free, while the real cost comes from how you run it. The official Jenkins site describes it as an open-source automation server with hundreds of plugins for building, deploying, and automating projects, and the supplied TrustRadius pricing reference says there are no pricing plans listed and that a free version is available. For buyers, that means there is no conventional subscription page to decode. Instead, the relevant questions are what it will cost to host, secure, patch, scale, and support the system in your own environment.
That distinction matters because Jenkins is self-hosted by design. Teams that choose it are usually trading license fees for operational control, which can be a good fit when you need deep customization, unusual runtime support, or broad integration flexibility. In practice, the expense is often not the binary itself but the surrounding stack: controller and agent infrastructure, artifact storage, plugin maintenance, and the staff time needed to keep pipelines stable. If you want an officially published seat price, minimum commitment, or discount schedule, the supplied documents do not provide one for Jenkins core. In that sense, the page is simple: Jenkins software is free, but total cost is environment-specific and buyer-run.