JFrog Artifactory Self-Hosted
Universal artifact repository installed on Kubernetes clusters or servers you operate.
6 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
JFrog Artifactory unauthenticated authentication bypass
CVE-2026-82329 is a critical unauthenticated authentication bypass affecting default-configured Artifactory deployments.
Scope: JFrog lists fixed builds 7.161.20, 7.146.38, 7.133.29, 7.125.20, 7.117.28, and 7.111.21 across maintained branches.
The vendor identifies default configuration as affected; exact branch applicability follows the advisory matrix.
Action: Upgrade to the fixed or later supported build for the installed branch and review administrative access.
Primary source · Reviewed 2026-11-18
What lands where
Supplied by
Vendor or project
Helm chart, Docker or Docker Compose, or native OS package or archive
Runs in
Documented customer environment
Customer-operated Artifactory service with persistent filestore and database.
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- AWS
- Azure
- Google Cloud
Servers / containers
Operated by
Your team
Customer operates the cluster or servers, database, filestore, backups, upgrades and availability configuration.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Artifactory Helm installation on EKS, AKS and GKE ↗ · Source checked 2026-11-17
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Artifactory Helm installation on EKS, AKS and GKE ↗ · Source checked 2026-11-17
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Artifactory Helm installation on EKS, AKS and GKE ↗ · Source checked 2026-11-17
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Helm chart, Docker or Docker Compose, or native OS package or archive |
|---|---|
| Infrastructure | Servers / containers Artifactory runs as server or container workloads with persistent database and filestore dependencies; the listed Helm path uses customer-operated Kubernetes infrastructure. |
| Licensing model | Open Source / Open Core JFrog publishes Artifactory OSS as an open-source edition and separately sells proprietary self-managed Pro X, Enterprise X and Enterprise+ subscriptions. Other community editions have different capability limits. |
| License | Open-source Artifactory OSS; commercial Pro X, Enterprise X and Enterprise+ editions. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
12 of 12 fields researched (100%) · 10 documented · 2 unresolved. Evidence coverage is not a feature score.
- Marketplace delivery
Edition-dependentEvidence and scope for Marketplace delivery
The self-hosted subscription agreement explicitly permits procurement through supported cloud marketplaces, with fees and terms in the offer/order form. This is software procurement, not proof that a SaaS offer deploys in the buyer account.
Self-hosted subscription procurement · Source ↗ · Reviewed 2026-11-17
Edition-dependent · Editor reviewed.
- Cloud commitment eligibility
Edition-dependentEvidence and scope for Cloud commitment eligibility
JFrog states approved cloud Marketplace purchases can draw down committed spend. Obtain confirmation for the self-hosted offer and buyer agreement; this is a conditional procurement statement, not universal credit eligibility.
JFrog Marketplace purchasing; provider contract and selected offer govern · Source ↗ · Self-hosted Marketplace contracting ↗ · Reviewed 2026-11-17
Edition-dependent · Editor reviewed.
- Single sign-on
Edition-dependentEvidence and scope for Single sign-on
SAML SSO is included from Pro X, including Enterprise X and Enterprise+; it is excluded from the non-commercial editions in the reviewed matrix.
Self-managed Artifactory edition matrix · Source ↗ · SAML configuration ↗ · Reviewed 2026-11-17
Edition-dependent · Editor reviewed.
- SCIM provisioning
Edition-dependentEvidence and scope for SCIM provisioning
SCIM identity management is included in Enterprise X and Enterprise+, and excluded from Pro X and non-commercial editions. The API uses the Access SCIM v2 endpoint and a restricted identity-management token.
Self-managed Enterprise X / Enterprise+ · Source ↗ · SCIM endpoint and token permissions ↗ · Reviewed 2026-11-17
Edition-dependent · Editor reviewed.
- Compliance attestations
Not confirmedEvidence and scope for Compliance attestations
The reviewed JFrog Artifactory Self-Hosted material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage.
Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited · Source ↗ · Reviewed 2026-11-17
Sources checked — unresolved · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
The edition matrix distinguishes LDAP/RBAC from paid SAML, identity management, HA and scanning features. Xray and Advanced Security are separately entitled capabilities; do not assume the free Artifactory distribution includes them. Current advisory review: CVE-2026-82329 is a critical unauthenticated authentication bypass affecting default-configured Artifactory deployments. Upgrade to the fixed or later supported build for the installed branch and review administrative access.
Self-managed component and feature entitlements; not an attestation JFrog lists fixed builds 7.161.20, 7.146.38, 7.133.29, 7.125.20, 7.117.28, and 7.111.21 across maintained branches. · Source ↗ · Prior security-controls source ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
- Air-gapped operation
Edition-dependentEvidence and scope for Air-gapped operation
Artifactory 7.77+ documents an air-gap setting and offline entitlement-file workflow. Obtain and renew the correct entitlement files and stage all dependencies; the 14-day license grace period can end in service disruption.
Licensed self-managed air-gap configuration · Source ↗ · Reviewed 2026-11-17
Edition-dependent · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
JFrog supplies Helm installation paths for EKS, AKS and GKE. Configure master/join keys, persistent storage and the database, and pin compatible chart/application versions rather than treating Helm defaults as production sizing.
Self-managed Artifactory Helm installation · Source ↗ · Reviewed 2026-11-17
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
Artifactory sizing is based on active clients: the baseline starts at 4 cores/6 GB RAM for up to 20 clients, rising to 8 cores/18 GB for 101–200 clients. Database, HA, Xray and storage are additional sizing decisions.
Artifactory active-client matrix; users are not necessarily simultaneous clients · Source ↗ · Reviewed 2026-11-17
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
JFrog publishes Artifactory OSS as an open-source edition and separately sells proprietary self-managed Pro X, Enterprise X and Enterprise+ subscriptions. Other community editions have different capability limits.
JFrog Artifactory Self-Hosted: software entitlement and edition boundary; infrastructure and operating costs are separate · Source ↗ · Reviewed 2026-11-17
Documented · Editor reviewed.
- Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate
Determine active artifact clients, package traffic, HA edition, database/filestore design and whether Xray/Workers are included. A 100-person headcount does not determine concurrent repository clients or scanning load. A complete monthly operating estimate is not established.
Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit · Source ↗ · Reviewed 2026-11-17
Sources checked — unresolved · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The reviewed current self-managed Artifactory release is 7.173.21. Older maintained branches have separate CVE-2026-82329 fixed builds; verify the selected branch before upgrading.
JFrog Artifactory self-managed release notes · Source ↗ · Self-managed lifecycle policy ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
Scope & considerations
This entry covers self-hosted Artifactory, not JFrog SaaS. Edition capabilities differ substantially: Artifactory OSS is limited and does not include cloud object storage, while high availability and broader repository, security and platform capabilities require the applicable commercial entitlement. Production deployments should use an external PostgreSQL database and durable filestore. The separate Amazon ECS path is single-node, limited to 16 vCPUs and cannot connect to Xray or Distribution. CVE-2026-82329 is a critical unauthenticated authentication bypass under default configuration. JFrog lists fixed builds across maintained branches, including 7.161.20, 7.146.38, 7.133.29, 7.125.20, 7.117.28, and 7.111.21; move to a fixed or later supported build.
Category fit
- DevOps
- Artifact, package and container registry for software delivery pipelines.
Compare within DevOps
- Argo CDGitOps continuous delivery controller and interface for deploying and reconciling applications in Kubernetes clusters.
- AWS
- Azure DevOps ServerSource control, CI/CD, work tracking, testing and package management installed on Azure virtual machines you operate.
- Azure
- Bitbucket Data CenterCommercial self-managed Git collaboration and code-review platform for eligible existing Atlassian customers, with an announced Hybrid License transition.
- AWS
- Azure
- Google Cloud
- CircleCI ServerCommercial self-hosted CI/CD platform installed in a customer-operated Amazon EKS or Google GKE cluster.
- AWS
- Google Cloud
- CloudBees CI on Modern Cloud PlatformsEnterprise continuous-integration platform installed with Helm in a Kubernetes cluster you operate.
- AWS
- Azure
- Google Cloud
- GitHub Enterprise ServerCustomer-operated GitHub software-development platform deployed as a licensed virtual appliance.
- AWS
- Azure
- Google Cloud
- GitLab Self-ManagedSource control and CI/CD on infrastructure you operate.
- AWS
- Azure
- Google Cloud
- Oracle Cloud
- Alibaba Cloud
- HarborContainer and OCI artifact registry for managing software images within customer-operated infrastructure.
- Railway
Showing 8 of 27 other listings in DevOps. These products address related workflows; read their category-fit notes before comparing scope. See all of DevOps →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Artifactory installation with Helm charts ↗docs.jfrog.com
- Artifactory installation methods and Amazon ECS limits ↗docs.jfrog.com
- Self-managed edition feature comparison ↗docs.jfrog.com
- JFrog open-source offerings ↗jfrog.com
- JFrog security advisories ↗docs.jfrog.com
- Artifactory release notes ↗docs.jfrog.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Artifactory Helm installation on EKS, AKS and GKE ↗ · AWS, Azure, Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.
JFrog's current Artifactory Helm guide explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as cluster types and documents installation into the customer's cluster. Provider storage, database, ingress and support details vary by edition.
- Artifactory Helm installation on EKS, AKS and GKE ↗ · AWS, Azure, Google Cloud
- Infrastructure evidenceChecked
- Licensing evidenceChecked