Codefresh is responsible for the _availability of Hosted GitOps Runtimes_.<br>

The Argo CD applications created in Hosted GitOps Runtimes are the customer's responsibility. Codefresh Support is happy to assist as needed.

|Kubernetes cluster | Server version 1.18|

|Target Kubernetes clusters | {::nomarkdown} <ul><li>At least one target cluster to which to deploy Argo CD applications. <br>The actual number of target clusters depends on package sizing.</li><li>Must have public access from Internet</li></ul>{:/}|

|Argo CD managed CRDs (Custom Resource Definitions) | Between 300 and 400 CRDs |

|Git provider | {::nomarkdown}<ul><li>GitHub</li><!---<li>GitLab Cloud</li>--><li>Bitbucket Cloud (contact Support)</li><li>Gerrit (contact Support)</li></ul>{:/}|

|Git repo for manifests | Up to 100MB|

|CMP (Cloud Management Platform) plugins | Only for Enterprise customers |

For a comparison between Hosted and Hybrid GitOps Runtimes, see [Hosted vs. Hybrid GitOps]({{site.baseurl}}/docs/installation/installation-options/#hosted-vshybrid-gitops).

Based on the Git provider you select, you need to authorize access through OAuth or an access token, and then select the Git organizations or accounts in which to create the required Git repos.

This article walks you through the process of installing Hybrid GitOps Runtimes in your Codefresh accounts using Helm charts. You can install a single GitOps Runtime on a cluster. To install additional Runtimes in the same account, each account must be on a different cluster. Every Runtime within your account must have a unique name.

For Hosted GitOps Runtimes, see [Hosted GitOps Runtime Setup]({{site.baseurl}}/docs/installation/gitops/hosted-runtime/).

description: "Understand different installation options supported by Codefresh"

The Codefresh platform supports different installation options for Codefresh pipelines and Codefresh GitOps, all compliant with [SOC2 - Type2](https://us.aicpa.org/interestareas/frc/assuranceadvisoryservices/aicpasoc2report){:target="\_blank"}.

While Codefresh can still help with maintenance of the On-Premises platform, we would recommend the Hybrid Runner installation for Codefresh piplines as it combines flexibility without compromising on security.

**Codefresh GitOps installation options**

GitOps is a full-featured solution for application deployments and releases powered by the Argo Project. Codefresh uses Argo CD, Argo Workflows, Argo Events, and Argo Rollouts, extended with unique functionality and features essential for enterprise deployments.

GitOps supports Hosted and Hybrid Runtime installation options.

See [GitOps](#gitops).

For customers who want full control over Codefresh pipelines, Codefresh also offers on-premises installation option. Both the UI and builds run on a Kubernetes cluster fully managed by the customer.

Codefresh GitOps supports SaaS and hybrid installation options for GitOps Runtimes. For the main differences between Hosted and Hybrid GitOps, see [Hosted vs. Hybird GitOps]({{site.baseurl}}/docs/installation/installation-options/#hosted-vshybrid-gitops).

The Hosted GitOps Runtime is installed and provisioned on a Codefresh cluster, and managed by Codefresh.

The Hybrid GitOps Runtime is installed in the customer's cluster, and managed by the customer.

Hybrid GitOps is optimal for organizations with security constraints, wanting to manage CI/CD operations within their premises. Hybrid GitOps strikes the perfect balance between security, flexibility, and ease of use. Codefresh maintains and manages most aspects of the platform, apart from installing and upgrading Hybrid GitOps Runtimes which are managed by the customer.

For more information on Hybrid GitOps, see [Hybrid GitOps Runtime requirements]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/#minimum-system-requirements) and [Hybrid GitOps Runtime Runtime installation]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/).

The table below highlights the main differences in functionality and resources between Hosted and Hybrid GitOps.

|Feature |Functionality | Hosted | Hybrid |

| | Number per account | One Runtime | Multiple Runtimes, one per cluster |

| | Target cluster | {::nomarkdown}<ul><li>Managed by customer</li><li>Number supported depends on package size and can range from 5 to 20 or higher</li><li>Network access: Public access from internet</li></ul>{:/} | {::nomarkdown}<ul><li>Managed by customer</li><li>Any number</li><li>Network access: Public or private access</li></ul>{:/} |

|Resources |Argo CD managed CRDs (Custom Resource Definitions)| Between 300 and 400 CRDs |Unlimited |

| |Mono Git repo for manifests | Max size up to 100MB | Unlimited |

| | CMP (Cloud Management Platform) plugins |Only for Enterprise customers |N/A |

| CD Ops |Applications |{::nomarkdown}<ul><li>Deployment supported only on target clusters</li><li>Self-healing interval: 90 seconds<br>See <a href="https://argo-cd.readthedocs.io/en/stable/user-guide/auto_sync/#automatic-self-healing">Argo CD automatic self-healing</a></li></ul> {:/} | {::nomarkdown}<ul><li>Deployment supported on both in-cluster and target clusters</li><li>Self-healing interval: 5 seconds (Argo CD default)<br>See <a href="https://argo-cd.readthedocs.io/en/stable/user-guide/auto_sync/#automatic-self-healing">Argo CD automatic self-healing</a></li></ul> {:/}|

|Dashboards |Home | Hosted Runtime and deployments|Runtimes, deployments, Delivery Pipelines |

| |GitOps Apps | Supported |Supported |

| |GitOps Environments | Supported |Supported |

| |GitOps Products | Supported |Supported |

| Characteristic | Hybrid Runner | On Premises | GitOps

[Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration)