PROVIDER - the Kubernetes-native CI/CD platform

Codefresh

Codefresh launched in 2015 as a Kubernetes-native CI/CD platform with YAML pipelines, container-isolated steps and Argo CD GitOps views, and joined Octopus Deploy in 2024; cloud-native fit is the strength, while roadmap integration and ecosystem size are the variables.

Developer Tools United States 2026.11.19
3.6pts

Detailed Notes

Pros 5 items

A Kubernetes-native CI/CD platform launched in 2015 with YAML pipelines, acquired by Octopus Deploy in 2024
Every build step runs in 1 isolated container, fitting containerised and polyglot projects naturally
GitOps capability is built in, integrating with Argo CD to show 2 things: deployment state and environment drift
A Hybrid Runner places execution nodes inside your own cluster so 2 assets, code and secrets, never leave the network
Parallel stages and shared volume caching let a typical build live in 1 YAML file

Cons 4 items

Product and brand integration under Octopus Deploy is still in progress, so long-term roadmap needs attention
Fewer third-party plugins and examples than ecosystem platforms such as GitHub Actions
Self-hosted runners add operational work, and multi-cluster setups need extra architecture
The free tier is limited, with large parallel builds billed by usage

Service Overview

Codefresh arrived in 2015 as a CI/CD platform built for Kubernetes and was acquired by Octopus Deploy in 2024. It defines pipelines in YAML, runs each step in its own container, and includes GitOps deployment views.

In the development tools category it represents the container-plus-GitOps route: builds, images and deployment state close the loop in one platform.

Key Strengths

  • Container native: isolated containers per step keep dependencies and caches clean
  • YAML pipelines: configuration lives in version control, so reuse and review are cheap
  • GitOps built in: Argo CD integration shows environment drift and sync status
  • Hybrid execution: Hybrid Runners keep builds inside your own cluster
  • Parallel and cached: parallel stages with shared volume caching shorten builds

Product Ecosystem

Platform capabilities

Pipeline orchestration, image builds, test reports, artifacts and GitOps environment management.

Integrations

GitHub, GitLab, Bitbucket, Argo CD, Helm and more than 5 artifact or notification services.

Typical scenarios

Kubernetes releases, multi-environment GitOps governance, image build and scan pipelines.

Limitations

  • Roadmap integration: product and brand consolidation after the acquisition is ongoing
  • Ecosystem size: fewer plugins and community examples than GitHub Actions
  • Operational cost: self-hosted runners need cluster and network planning
  • Billing threshold: the free tier is limited and parallel builds are usage-priced

Use Cases

  • Kubernetes application delivery (★★★★★): container and GitOps chains are complete
  • Consistent multi-environment releases (★★★★): environment drift is visible
  • Keeping code inside the network (★★★★): Hybrid Runners satisfy compliance
  • Lightweight static frontends (★★★): GitHub Actions is simpler

Pricing

Item Price Notes
Free tier $0 Limited build minutes and 1 runner
Team plan Usage based Priced by parallel builds and storage
Enterprise Contract Adds self-hosting, SSO and support

Small teams validate on the free tier, then subscribe by concurrency and usage.

FAQ

  • Is Argo CD required? No. Built-in deploy steps or Helm work too, and the Argo CD integration serves GitOps flows.
  • Can it self-host? Hybrid Runners run in your cluster while the control plane stays in the cloud; fully offline setups need an enterprise discussion.
  • How does it differ from GitHub Actions? Actions has the larger ecosystem, while Codefresh focuses on container-isolated execution and GitOps views.

Code Examples

A minimal pipeline

version: '1.0'
steps:
  build:
    title: Build image
    type: build
    image_name: acme/api
    dockerfile: Dockerfile
  test:
    title: Run tests
    image_name: acme/api
    commands:
      - npm ci
      - npm test

The build step creates the image and test runs commands inside that same image.

A GitOps deployment step

deploy:
  title: Deploy to staging
  type: argocd-sync
  arguments:
    APP_NAME: acme-api-staging
    APP_NAMESPACE: argocd

argocd-sync triggers a sync and waits for the application to become healthy.

Community & Resources

Visit Codefresh Website → https://codefresh.io/
Visit Website ↗