JFrog Container Registry Capabilities

JFrog Container Registry (JCR) is a non-commercial, self-managed Artifactory edition. This page lists capabilities that apply to JCR. For the full JFrog Platform subscription matrix (Pro X, Enterprise X, and Enterprise+), see Feature Comparison Matrix.

JCR installers, images, and Helm charts ship as jcr and artifactory-jcr. The product name in logs and REST paths remains Artifactory.

Included in JCR

Package Types and Clients

JCR onboarding and repository creation support Generic, Docker, OCI, Helm OCI, and Helm only. Docker V2, OCI, and Helm OCI share the same registry API surface. You can use the Docker client, Podman, Helm 3, ORAS, and JFrog CLI Docker commands against those repositories. Other package types such as Maven, npm, and PyPI are not available.

Artifact and Repository Management

JCR includes local, remote, and virtual repositories. You can proxy and cache remote registries, apply include and exclude patterns, and move, copy, and delete artifacts in the UI. JCR uses checksum-based storage with deduplication and the Artifactory REST API for repository and artifact operations. Smart remote repositories are available. Federated repositories and repository replication are not.

Search and Metadata

You can search by name, archive, property, or checksum, annotate artifacts with searchable properties, and query with Artifactory Query Language (AQL). Among non-commercial editions, this search and AQL set is JCR-specific. It is not in Artifactory OSS or Community Edition for C/C++.

Security

JCR includes LDAP authentication and role-based authorization for users, groups, and permissions. LDAP groups, SAML, and additional identity providers that appear on commercial editions are outside this edition. For more information, see Permissions.

Storage and Operations

JCR can use local disks and cloud object storage (Amazon S3, Google Cloud Storage, and Azure Blob). That cloud filestore option is not available in Artifactory OSS. Filestore sharding and high availability clustering are not included. Backups, garbage collection, and in-place upgrades to a newer JCR or to Artifactory Pro follow the Artifactory operations topics, including Regular Maintenance Operations and Upgrading Artifactory.

Automation

REST APIs and JFrog CLI work with JCR for the supported package types. CI servers can publish build-info, but build artifact promotion, demotion, and cleanup are commercial Artifactory features and are not part of JCR. Groovy user plugins are not supported on this edition.

Not Included in JCR

The following are commonly mistaken for JCR features because they appear in general Artifactory documentation:

All package types other than Docker, OCI, Helm, Helm OCI, and Generic
JFrog Xray, JFrog Catalog, and other JFrog Platform security products
High availability, multiple Artifactory nodes, and load-balanced clusters
Build promotion and release bundle workflows
Repository replication and federated repositories
User plugins
Advanced authentication such as SAML, Crowd, and multiple LDAP trees, as documented for Enterprise editions
Access Federation, Distribution Edge, and JFrog Mission Control license buckets

Frequently Asked Questions

This section provides answers to frequently asked questions.

plusFAQs

Q: Which package types does JFrog Container Registry support?

A: JCR supports Generic, Docker, OCI, Helm OCI, and Helm only. Maven, npm, PyPI, and other Artifactory package types are not available. For more information, see Package Types and Clients.

Q: Does JCR include build promotion or JFrog Xray?

A: No. Build promotion, demotion, and cleanup are commercial Artifactory features. JFrog Xray and other JFrog Platform security products are not included. See Not Included in JCR.

Q: Can JCR use Amazon S3 or other cloud object storage?

A: Yes. JCR can use local disks and cloud object storage such as Amazon S3, Google Cloud Storage, and Azure Blob. That cloud filestore option is not available in Artifactory OSS. For more information, see Storage and Operations.

Q: How does JCR compare with Artifactory OSS?

A: JCR includes Docker, OCI, and Helm package types, AQL, searchable properties, and cloud object storage. Artifactory OSS is aimed at Maven, Gradle, Ivy, SBT, and Generic repositories and does not include that JCR-specific search and storage set.