Rancher Manager

Open-source Kubernetes management platform deployed into a customer-operated cluster.

8 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 Helm chart on a supported Kubernetes cluster

  2. Operated by

    Your team

    Customer manages the management cluster, ingress, certificates, backups, upgrades, downstream-cluster credentials and availability.

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.

    Rancher Manager on Amazon EKS ↗ · Source checked 2026-11-14

  • Azure: Customer cloud account · Customer-operated

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

    Rancher Manager on Azure Kubernetes Service ↗ · Source checked 2026-11-14

  • 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.

    Rancher Manager on Google Kubernetes Engine ↗ · Source checked 2026-11-14

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 Helm chart on a supported Kubernetes cluster
InfrastructureServers / containers
Rancher runs as persistent management services inside Kubernetes and requires ingress, certificates and durable state. The hosted Kubernetes control plane does not make Rancher serverless.
Licensing modelOpen Source / Open Core
Rancher Manager is Apache-2.0 licensed. SUSE subscriptions, hosted services and enterprise support use separate commercial terms.
LicenseApache License 2.0; commercial SUSE subscriptions and support are separate.

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 upstream authentication guide documents OIDC, SAML and OAuth integrations, including Keycloak, Okta, Entra ID, AD FS and a generic OIDC provider. Review version compatibility, local administrator access and downstream-cluster authorization separately from signing into Rancher.

Rancher Manager console federation · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

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

The Kubernetes guide publishes separate stable, latest and alpha Helm repositories. Stable is recommended for production; check the Kubernetes support matrix and certificate/HA prerequisites before installation.

Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Deployment artifact ↗ (stable Helm repository index (moving; select a supported chart version)) · Reviewed 2026-11-14

Documented · Editor reviewed.

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

For a small hosted-Kubernetes management cluster, the guide lists at least three nodes, each with 4 vCPUs and 16 GB RAM. Larger managed fleets need more. Single-node Docker is development/test only; downstream workload clusters, datastore/storage and HA headroom are additional.

Upstream management-cluster starting profile; downstream applications excluded · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

Rancher Manager core is Apache-2.0 licensed. This does not establish a SUSE support subscription price or the cost and licences of managed Kubernetes clusters and optional components.

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 publisher-designated GitHub release checked was v2.15.3, published 2026-10-29. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package.

Upstream rancher/rancher release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-14

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

This entry covers self-managed Rancher Manager, not separate hosted offerings. Rancher documents EKS, AKS and GKE installation paths. GKE Autopilot is not supported for the Rancher server because required kube-system changes are restricted.

Community & maintenance

Rancher has sustained code participation from multiple contributors and an established upstream user community. The reviewed Community release 2.15.3, published October 29, 2026, records maintenance and security fixes. Public contributor history and the official community program establish participation beyond repository popularity; commercial SUSE support remains separate.

Category fit

DevOps
Provides centralized provisioning, access control and lifecycle management for Kubernetes clusters.

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.

    • Rancher Manager on Amazon EKS ↗ · AWS

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

      The upstream guide installs the Rancher server with Helm into an EKS cluster controlled by the customer.

    • Rancher Manager on Azure Kubernetes Service ↗ · Azure

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

      The upstream guide installs the Rancher server with Helm into an AKS cluster controlled by the customer.

    • Rancher Manager on Google Kubernetes Engine ↗ · Google Cloud

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

      The upstream guide installs Rancher into a GKE Standard cluster. GKE Autopilot is explicitly unsupported for the Rancher server.

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

Suggest a correction · Back to directory