SuperPlane Enterprise Self-Hosted

Enterprise software-factory and agent-workflow platform installed with Terraform and Helm in a customer cloud account.

4 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

    Vendor Terraform modules provision EKS, AKS or GKE, managed data services and the SuperPlane Helm release

  2. Operated by

    Your team

    Customer manages the cloud account, cluster, database, object storage, runner images and VMs, DNS, TLS, backups, upgrades and connected model or tool credentials.

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.

    SuperPlane Enterprise on EKS, AKS and GKE ↗ · Source checked 2026-11-17

  • Azure: Customer cloud account · Customer-operated

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

    SuperPlane Enterprise on EKS, AKS and GKE ↗ · Source checked 2026-11-17

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

    SuperPlane Enterprise on EKS, AKS and GKE ↗ · Source checked 2026-11-17

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

Install methodVendor Terraform modules provision EKS, AKS or GKE, managed data services and the SuperPlane Helm release
InfrastructureServers / containers
Terraform provisions persistent Kubernetes application services, managed PostgreSQL and object storage, while Fleet Manager creates runner virtual machines.
Licensing modelCommercial Only
The documented AWS, Azure and Google Cloud Kubernetes installation requires a SuperPlane Enterprise license. The Apache-2.0 community engine and single-VM deployment do not grant Enterprise feature or support entitlements.
LicenseCommercial SuperPlane Enterprise license required for the documented Kubernetes deployment.

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.

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

Marketplace delivery
Not confirmedEvidence and scope for Marketplace delivery

Enterprise installation and direct commercial terms are documented; a current cloud Marketplace offer for this Kubernetes edition was not established.

Reviewed public evidence for SuperPlane Enterprise Self-Hosted; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility

Enterprise custom terms do not establish an eligible Marketplace offer, qualifying fees or cloud-commitment treatment.

Reviewed public evidence for SuperPlane Enterprise Self-Hosted; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

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

The plan comparison includes SSO in Enterprise together with Enterprise self-hosting. Confirm the required IdP protocol and configuration with the vendor; these entitlements do not apply to the separate community VM edition.

Enterprise self-hosting plan · Source ↗ · Reviewed 2026-11-17

Edition-dependent · Editor reviewed.

SCIM provisioning
Not confirmedEvidence and scope for SCIM provisioning

Enterprise includes automated user provisioning, but the pricing table does not name SCIM or document its endpoint, operations and identity-provider limitations.

Enterprise automated provisioning; protocol not established · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Compliance attestations
Not confirmedEvidence and scope for Compliance attestations

The reviewed SuperPlane Enterprise Self-Hosted material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage.

Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

The provider installation separates infrastructure provisioning, application secrets and runner management. Protect Terraform state, generated credentials and license material; configure TLS/DNS and restrict the provider permissions used by the installer.

Enterprise Kubernetes provider installation · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Air-gapped operation
Not confirmedEvidence and scope for Air-gapped operation

The standard installer downloads charts, images and provider tooling and configures public DNS/certificates. A supported offline licensing, dependency-transfer and upgrade workflow was not established in this guide.

Enterprise installation; no inference from running in a private VPC · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

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

Provider-specific Terraform creates the managed Kubernetes, PostgreSQL and storage dependencies; Helm installs the application and Fleet Manager controls runners. GCP requires building runner images with Packer rather than using the published AWS/Azure images.

Enterprise installer and provider dependencies; community VM is a different path · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

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

The Enterprise guide requires managed Kubernetes, PostgreSQL, object storage and separately provisioned runners. Runner defaults and example machine types are component settings, not a measured minimum for the complete Enterprise service.

Enterprise topology requirements; size the cluster and runners separately · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The documented AWS, Azure and Google Cloud Kubernetes installation requires a SuperPlane Enterprise license. The Apache-2.0 community engine and single-VM deployment do not grant Enterprise feature or support entitlements.

SuperPlane Enterprise Self-Hosted: software entitlement and edition boundary; infrastructure and operating costs are separate · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate

Price EKS, RDS HA PostgreSQL, storage and runner pools after the Enterprise bill of materials and active-runner concurrency are confirmed. Hosted sandbox/model charges do not price this deployment. A complete monthly operating estimate is not established.

Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Release snapshot / cadence
Not confirmedEvidence and scope for Release snapshot / cadence

The installer names component/chart revisions, while the latest GitHub release is Fleet Manager v0.1.7. Neither alone establishes the current Enterprise application bundle and supported upgrade compatibility.

Reviewed public evidence for SuperPlane Enterprise Self-Hosted; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Scope & considerations

This entry scopes only the Enterprise Kubernetes deployment on AWS, Azure and Google Cloud. The Apache-2.0 community engine and single-VM Compose installation are separate. Google Cloud public runner images are not yet published and must be built with Packer. Connected source-control, model and workflow services can move code or data outside the cluster according to their own configuration and terms.

Category fit

DevOps
Coordinates coding agents, source control, CI, review and verified software-delivery work.
Workflow automation
Defines durable automation lines, approvals, checks and repair loops for recurring engineering work.

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.

    • SuperPlane Enterprise on EKS, AKS and GKE ↗ · AWS, Azure, Google Cloud

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

      SuperPlane documents Terraform-created EKS, AKS and GKE clusters with managed PostgreSQL, object storage and Helm releases in the customer's account. Enterprise licensing is required; Google Cloud runner images must currently be built by the operator with Packer.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory