CircleCI Server

Commercial self-hosted CI/CD platform installed in a customer-operated Amazon EKS or Google GKE cluster.

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

    Official Terraform-assisted infrastructure setup and Helm installation on Amazon EKS or Google GKE

  2. Operated by

    Your team

    Customer manages Kubernetes, networking, object storage, databases, secrets, TLS, execution capacity, backups, upgrades and the CircleCI Server license.

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.

    CircleCI Server on Amazon EKS ↗ · Source checked 2026-11-16

  • Google Cloud: Customer cloud account · Customer-operated

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

    CircleCI Server on Google GKE ↗ · Source checked 2026-11-16

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

Install methodOfficial Terraform-assisted infrastructure setup and Helm installation on Amazon EKS or Google GKE
InfrastructureServers / containers
CircleCI Server runs persistent application and data-service workloads in a customer Kubernetes cluster and uses cloud object storage and provisioned execution capacity.
Licensing modelCommercial Only
CircleCI Server is an enterprise self-hosted offering that requires a commercial license supplied during installation.
LicenseCommercial CircleCI Server license required.

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.

11 of 12 fields researched (92%) · 7 documented · 4 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
Not confirmedEvidence and scope for Marketplace delivery

The reviewed vendor AWS listing is titled Cloud-Hosted CICD, while its description also mentions Server and customized packages. The public terms do not establish the exact self-hosted Server entitlement; confirm a Server-specific contract before purchase.

Mixed-offering Marketplace description; Server contract coverage remains unresolved · Source ↗ · Reviewed 2026-11-16

Sources checked — unresolved · Editor reviewed.

Single sign-on
Edition-dependentEvidence and scope for Single sign-on

Server uses GitHub or GitHub Enterprise as its identity provider. GitHub Enterprise can federate authentication through SAML; configure that upstream identity boundary rather than assuming a direct CircleCI SAML integration.

CircleCI Server 4.10; GitHub identity integration · Source ↗ · Reviewed 2026-11-16

Edition-dependent · Editor reviewed.

SCIM provisioning
Not confirmedEvidence and scope for SCIM provisioning

The operator guide describes SCIM at the GitHub Enterprise identity-provider layer. It does not establish a direct CircleCI SCIM endpoint or the full lifecycle behavior inside Server.

Delegated GitHub Enterprise provisioning; direct Server SCIM remains unconfirmed · Source ↗ · Reviewed 2026-11-16

Sources checked — unresolved · Editor reviewed.

Compliance attestations
Not confirmedEvidence and scope for Compliance attestations

CircleCI publishes corporate SOC 2/FedRAMP claims and offers security reports. The public page does not establish the current report period or assurance scope for a customer-operated Server deployment; obtain the report and map the customer’s responsibilities.

Vendor security-program claims versus the customer-operated CircleCI Server boundary · Source ↗ · Reviewed 2026-11-16

Sources checked — unresolved · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

The Server hardening guide recommends private resources, permits VPN-only access without public IPs, and requires Nomad client/server mTLS. Job SSH exposure and firewall/security-group rules need deliberate configuration; the documentation is guidance, not proof the installed cluster already enforces it.

Server 4.10 Kubernetes/Nomad/VM network hardening · Source ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Air-gapped operation
AvailableEvidence and scope for Air-gapped operation

CircleCI documents a disconnected installation with a local container registry, Kubernetes, S3-compatible storage, GitHub Enterprise and Nomad VMs. Transfer all required release images and charts before installation; follow the remaining configuration and test phases.

CircleCI Server documented air-gapped installation · Source ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

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

The Helm chart is distributed through cciserver.azurecr.io. The linked helper enumerates chart images for transfer to a private registry; it is not the chart or a complete infrastructure template. Select a compatible Server/chart release and use CircleCI-provided registry credentials.

Server 4.10 air-gap preparation; guide example chart 4.10.1 · Source ↗ · Deployment artifact ↗ (main (moving branch; guide example chart 4.10.1)) · Reviewed 2026-11-16

Documented · Editor reviewed.

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

The Server 4.10 AWS guide specifies at least four Kubernetes nodes, 24 CPU cores and 90 GB total RAM below 500 daily active users; 500+ users require six nodes, 48 cores and 240 GB. Job-execution capacity and external services require separate sizing.

Server 4.10 control/application cluster on AWS; not a total build-fleet or cost estimate · Source ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

CircleCI Server is an enterprise self-hosted offering that requires a commercial license supplied during installation.

CircleCI Server: software license terms; infrastructure and operating costs are separate · Source ↗ · Edition and license conditions ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate

The vendor identifies execution workers, per-job machine instances, Kubernetes capacity, artifacts/caches and block storage as cost drivers, and recommends retention, tagging and budget monitoring. It does not establish a workload- and region-specific operating total; concurrency, job duration, instance choices, retention and staffing still need a budget model.

Public cost-driver guidance; no dated infrastructure-and-operations estimate · Source ↗ · Reviewed 2026-11-16

Sources checked — unresolved · Editor reviewed.

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

The reviewed vendor release is 4.10.1, published 2026-08-11. This is a dated, scoped snapshot; it does not establish compatibility with another chart, cloud package or commercial edition.

CircleCI Server release; review MongoDB and other upgrade prerequisites; source supplies a publication day, not a timestamp · Source ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Show all fields (1 not researched)
Cloud commitment eligibility
Not researched Supply a public source.

Scope & considerations

This entry covers CircleCI Server, not CircleCI Cloud or cloud-connected self-hosted runners. EKS and GKE are the tested cloud environments; CircleCI labels Azure and DigitalOcean as untested. GKE Autopilot is unsupported. CircleCI Server currently supports GitHub Enterprise Cloud and GitHub Enterprise Server as version-control providers.

Category fit

DevOps
Provides self-hosted continuous integration and delivery pipelines, execution environments, policy controls and build infrastructure.

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
  • 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
  • HashiCorp Consul EnterpriseCommercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only

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.

    • CircleCI Server on Amazon EKS ↗ · AWS

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

      CircleCI documents preparing AWS networking, an EKS cluster, storage, permissions and other prerequisites before installing CircleCI Server with its Helm chart.

    • CircleCI Server on Google GKE ↗ · Google Cloud

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

      CircleCI documents preparing a customer GCP project, VPC, GKE cluster, Cloud Storage and workload identity before installing CircleCI Server. The guide states that GKE Autopilot is unsupported.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory