Skip to main content

Harness Open Source and Free Edition FAQs

This article addresses some frequently asked questions about Harness Open Source and Free Edition deployments.

Do you have a free version of Harness CD?​

Harness CD has two free options to get started.

warning

As of Dec 2023, the Harness CD Community Edition (CE) is retired in favor of Harness Open Source.

What can I do with Harness CD Community Edition?​

  • Today, Harness CD Community Edition can perform Kubernetes deployments only. This means pulling remote manifests and artifacts and deploying them to a local or remote Kubernetes cluster.
  • You can also use Harness CD features such as automated rolling, canary and blue green deployments, automated infrastructure provisioning, integrated approvals and notifications, full YAML-based development, and Harness Git Experience.
  • In the near future, Amazon Web Services (AWS) (Elastic Container Service (ECS), Auto Scale Groups (ASG), CloudFormation, Lambda, etc), Microsoft Azure (Virtual Machine Scale Sets (VMSS), WebApps, Azure Kubernetes Service (AKS), Azure Container Registry (ACR), Azure Resource Manager (ARM), Blueprint), .NET, Google Cloud Build, VM, Tanzu Application Services (TAS), Serverless, and traditional (Tomcat, etc) deployments will be supported.

Can I upgrade to a paid plan from Harness CD Community Edition?​

Yes, you can upgrade from within Harness in Account Settings > Subscriptions or by contacting Harness Sales.

What data does Community Edition collect?​

By default, Harness CD Community Edition shares minor usage details with Harness. These details help us understand and improve how the system behaves in real-world scenarios.

When you install an instance of Harness CD Community Edition, Harness collects the email address used to sign up in Harness, the number of users added to your Harness CD Community Edition, and the number of builds, deployments, and pipelines, and the information described above.

Harness uses this information for sales, support, product updates, security updates, policy updates, and license compliance.

The use of this information is governed by our Privacy Policy.

If you would like us to stop processing your data, or if you have any other questions or requests concerning your data, please contact the Harness Privacy Team. For more information on how we process your data, go to our Privacy Policy.

The current documentation advises us to use the Drone plugin model. How similar will this be with the move to Gitness?​

Gitness is using Drone plugins so rework is not necessary. The only changes with Gitness is you need to provide an additional mapping file that defines inputs and maps those inputs into the plugin container.