Jenkins

Automation server for building, testing and delivering software through configured pipelines.

5 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Run the official Jenkins Docker image or supported server package and attach appropriately isolated build agents.

  2. Operated by

    Your team

    Customer manages controller and agents, plugins, secrets, job permissions, storage, backups and security updates.

Deployment boundaries by provider
  • AWS: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Jenkins installation on AWS ↗ · Source checked 2026-11-12

  • Azure: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Jenkins installation on an Azure Linux VM ↗ · Source checked 2026-11-12

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodRun the official Jenkins Docker image or supported server package and attach appropriately isolated build agents.
InfrastructureServers / containers
Customer-operated Jenkins controller and build agents with persistent configuration. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.
Licensing modelOpen Source / Open Core
MIT License for Jenkins core; plugins and bundled dependencies have their own listed licenses. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.
LicenseMIT License for Jenkins core; plugins and bundled dependencies have their own listed licenses.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

The security guide documents delegating authentication to an external identity provider using SAML/OIDC. The relevant plugins are not necessarily installed; match supported plugin/controller versions and configure authorization separately.

Jenkins plugin-based security realm; not automatic core federation · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The installation guide identifies the official Jenkins image and persistent controller home. Build agents, privileged Docker access, plugins and workload resources require a separate security/capacity plan.

Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Deployment artifact ↗ (select an LTS or weekly versioned image tag) · Reviewed 2026-11-14

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The guide lists 256 MB RAM and 1 GB disk as basic minima, with 10 GB suggested for Docker. A small team is recommended 4 GB+ RAM and 50 GB+ disk; build-agent resources are separate.

Controller baseline, not total CI/build infrastructure · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

Jenkins core is MIT licensed. Plugins and bundled components have their own licences; commercial distributions, support, agents and infrastructure are separate costs.

Upstream core licence; commercial features, support and hosting priced separately · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

The reviewed upstream release is jenkins-2.591, published 2026-11-17. This is a dated release snapshot, not a support designation, a future cadence promise or approval to replace a provider package.

Upstream jenkinsci/jenkins release record; commercial editions, LTS branches and provider packages can differ · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Show all fields (7 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

Pipeline code, agents and plugins can access external source hosts, registries and deployment targets. A controller installed in an account does not contain every pipeline integration. Jenkins weekly 2.591 enables Content Security Policy enforcement on the Jenkins UI by default. Test installed plugins and custom UI integrations before adopting this weekly release; compatibility is tracked upstream. Administrators can use report-only mode while resolving incompatibilities, but disabling enforcement removes the protection.

Community & maintenance

Jenkins publishes community governance, contributor recognition and a release changelog updated in November 2026; these show sustained maintenance and community participation.

Category fit

DevOps
Automation server for continuous integration, build, test and delivery pipelines; agents and plugins provide workload-specific integrations.

Compare within DevOps

  • Argo CDGitOps continuous delivery controller and interface for deploying and reconciling applications in Kubernetes clusters.
    • AWS
    Customer-operated · Open Source / Open Core
  • Azure DevOps ServerSource control, CI/CD, work tracking, testing and package management installed on Azure virtual machines you operate.
    • Azure
    Customer-operated · Commercial Only
  • Bitbucket Data CenterCommercial self-managed Git collaboration and code-review platform for eligible existing Atlassian customers, with an announced Hybrid License transition.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • CircleCI ServerCommercial self-hosted CI/CD platform installed in a customer-operated Amazon EKS or Google GKE cluster.
    • AWS
    • Google Cloud
    Customer-operated · Commercial Only
  • CloudBees CI on Modern Cloud PlatformsEnterprise continuous-integration platform installed with Helm in a Kubernetes cluster you operate.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • GitHub Enterprise ServerCustomer-operated GitHub software-development platform deployed as a licensed virtual appliance.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • GitLab Self-ManagedSource control and CI/CD on infrastructure you operate.
    • AWS
    • Azure
    • Google Cloud
    • Oracle Cloud
    • Alibaba Cloud
    Customer-operated · Open Source / Open Core
  • HarborContainer and OCI artifact registry for managing software images within customer-operated infrastructure.
    • Railway
    Customer-operated · Open Source / Open Core

Showing 8 of 27 other listings in DevOps. These products address related workflows; read their category-fit notes before comparing scope. See all of DevOps →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Jenkins installation on AWS ↗ · AWS

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      The Jenkins project documents installing the Jenkins server on a customer EC2 instance, not merely deploying build output to AWS.

    • Jenkins installation on an Azure Linux VM ↗ · Azure

      Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      Microsoft documents installing Jenkins on an Ubuntu VM in the customer subscription. Harden public access and review the current Jenkins and Java versions rather than copying old version pins.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory