Supercharge your GitOps journey

Get started with our 45 day free trial – no credit card needed.

Codefresh GitOps Cloud
Manage your Kubernetes clusters efficiently and deliver new ideas to production faster.
$4,170 / year
What’s included

*Time limited offer – expires May 31st, 2025.

Need more
Clusters?
Scale up with additional destination clusters
$1,500 per cluster
Need more
Applications?
Deploy beyond 200 apps to expand your workloads seamlessly.
$1,500 per 100 apps
Need more
Support?
Get priority support from the experts when you need it most.

Trusted and powered by Codefresh

“I would describe Codefresh as the holy grail of CI/CD solutions. It’s Kubernetes focused and uses GitOps.”
Bryan Lokey
Director of Engineering, Kandji
“We had more Jenkins errors in a week than we have Codefresh in a year.”
Stacey Snyder
Senior Director of Engineering, Recurly
“We’re saving about 40% and we’re able to deploy all of our services through Codefresh.”
Joe Grabenstein
Senior Infrastructure Engineer, Crux
“Everything just worked out of the box”
Renato Stoco
Principal Engineer, Pismo
Frequently asked questions

At the end of your trial, you can upgrade to a paid plan—either GitOps Professional or GitOps Enterprise (contact sales for Enterprise pricing). If you choose not to upgrade, your Codefresh account will be locked.

The free trial lasts 45 days, during which you can explore the features of the GitOps Professional plan. No credit card is required to start the trial.

The Codefresh runtime is installed on your Kubernetes cluster and includes essential components like Argo CD, enabling the control plane to function. A single runtime can manage deployments across multiple Kubernetes clusters.

Target clusters are Kubernetes clusters where your applications and resources are deployed using Argo CD. These include:

  • The cluster where Argo CD is installed (self-managed cluster).
  • Any additional clusters that Argo CD manages for deploying applications.

Codefresh Environments are logical groupings representing destinations for application deployments. An environment can include multiple clusters and namespaces or be defined using Kubernetes labels on Argo CD applications.

Codefresh Products represent software with multiple versions deployed across different environments. A product typically consists of multiple Argo CD applications with a shared structure deployed to various clusters and namespaces.

Applications are Argo CD applications that continuously monitor and synchronize the desired state (defined in Git) with the actual state in your Kubernetes clusters.

Yes, the Professional plan is limited to 4,500 Kubernetes resources across all Argo CD instances. For higher limits, contact sales about the Enterprise plan.

Yes, Codefresh supports fully on-premises and air-gapped installations, available exclusively with the GitOps Enterprise plan. Contact sales for more details.

Yes, Codefresh supports connecting to an existing Argo CD instance already installed on your cluster. However, not all versions of Argo CD are supported—please refer to our support matrix for compatibility details.

Codefresh’s package includes up to 5 destination clusters. The way we count target clusters is based on the total number of clusters managed by Argo CD across all your connected instances:
  • The cluster where Argo CD is installed counts as a target cluster.
  • Each additional cluster managed by Argo CD also counts as a target cluster.
  • If you connect the same cluster to multiple Argo CD instances, it will be counted separately for each instance.
Example:
  • Cluster A has Argo CD installed → Counts as 1 cluster
  • Cluster B is managed by this Argo CD → Counts as 1 additional cluster
  • Cluster A is connected to another Argo CD instance → Counts again (now counted twice)
This means that the total number of target clusters is the sum of all clusters managed by all Argo CD instances, not just unique clusters. If you need more than 5 target clusters, additional clusters may require an upgrade.
Ready to Get Started?
  • safer deployments
  • More frequent deployments
  • resilient deployments