Installation Method Selection

Compare Platform methods (Helm, Ansible) vs individual product installers. Helm and Ansible are recommended for production.

Compare deploying the full JFrog Platform (Helm or Ansible) with installing individual products and choose the right installation method.

When To Use This Page

Use this page when comparing installation approaches before committing to an implementation.

Decision flowchart for selecting between Platform installation methods (Helm, Ansible) and individual product installers
⚠️

Use a Platform Method for All New Deployments

Use a Platform method (Helm or Ansible) for all new deployments, even if you only need one product today. You can enable just Artifactory and add Xray, Distribution, or others later with no reinstallation required.

Platform vs Individual Products

Full PlatformIndividual Products
Install methodSingle Helm chart or Ansible playbookSeparate installer per product
Products includedAll: enable what you needOne at a time
ManagementUnified UI and configurationSeparate per product
IntegrationNative (Artifactory + Xray share data automatically)Manual setup
UpgradesCoordinated across productsIndividual per product
Add products laterToggle in config, no reinstallSeparate installation
Best forAll deploymentsExisting standalone setups, specific constraints

Platform Methods (Recommended)

Deploy the JFrog Platform from a single installation flow with unified configuration and coordinated upgrades.

Helm chartAnsible
InfrastructureKubernetes (OpenShift as well)VMs and bare-metal
ProductsAll (Artifactory, Xray, Distribution, Catalog, Workers, Bridge Client, AppTrust, JAS)Core (Artifactory, Xray, Distribution)
Production readyYesYes
HA supportBuilt-in (replicaCount, HPA)Built-in (serial mode)
ScalingHPA / replicasManual
AutomationHelmAnsible playbooks
Secrets managementKubernetes Secrets, Vault, IRSAAnsible Vault
Best forKubernetes (including OpenShift) environmentsVM-based / bare-metal environments

Individual Product Methods

Deploy JFrog products separately, with one installer and configuration per product. Use this approach only when:

  • You have an existing standalone deployment and are not ready to migrate.
  • You have a specific constraint (for example, regulatory or tooling) that prevents using a platform method.
Docker / Docker ComposeRPM / Debian PackagesLinux ArchiveWindows
InfrastructureDocker hostsRHEL, CentOS, Ubuntu, DebianAny LinuxWindows Server
ProductsPer product (separate containers)Per product (separate packages)Per productArtifactory only
Production readyLimitedYesYesLimited
HA supportLimitedManualManualNo
ScalingManualManualManualManual
Best forExisting Docker setups, dev environmentsExisting Linux server setupsMinimal dependency installsWindows-only environments

Supported Installation Methods by Product

MethodArtifactoryXrayDistributionCatalogJASWorkersBridge ClientAppTrust
Helm (Kubernetes)✅ Supported✅ Supported✅ Supported✅ Supported✅ Supported✅ Supported✅ Supported✅ Supported
Ansible (VM/Bare-metal)✅ Supported✅ Supported✅ Supported❌ Not supported❌ Not supported❌ Not supported❌ Not supported❌ Not supported
Docker / Docker Compose✅ Supported✅ Supported✅ Supported❌ Not supported❌ Not supported✅ Supported✅ Supported❌ Not supported
RPM✅ Supported✅ Supported✅ Supported❌ Not supported❌ Not supported❌ Not supported❌ Not supported❌ Not supported
Debian✅ Supported✅ Supported✅ Supported❌ Not supported❌ Not supported❌ Not supported❌ Not supported❌ Not supported
Linux Archive✅ Supported✅ Supported✅ Supported❌ Not supported❌ Not supported❌ Not supported✅ Supported❌ Not supported
Windows Archive✅ Supported❌ Not supported❌ Not supported❌ Not supported❌ Not supported❌ Not supported❌ Not supported❌ Not supported

Next Steps