JFrog’s documentation lists Artifactory OSS, its free self-managed edition, for “Maven, Gradle, Ivy, SBT, Generic” (JFrog’s Container Registry page, read 2026-10-23). npm, Docker and PyPI are not on that list. JFrog’s own pages disagree, though: the matrix lists OSS without them, while the Container Registry page, after naming Maven, npm and PyPI, also says “Those formats are available in Artifactory OSS or a commercial Artifactory subscription” (JFrog’s Feature Comparison Matrix and JFrog’s Container Registry page, read 2026-10-23). On artifactory-oss 7.146.39, we found no npm, PyPI or Docker repository type. If you need one of them, this page sets out what each page says, our own finding and your options.
What JFrog says Artifactory OSS supports
The list
JFrog’s feature comparison matrix gives the package clients each free edition supports, and for OSS it reads “OSS: Maven, Gradle, Ivy, SBT, Generic” (JFrog’s Feature Comparison Matrix, read 2026-10-23). JFrog’s open source downloads page titles the Artifactory OSS download “Artifactory OSS for Java Package Management” (JFrog’s open source downloads page, read 2026-10-23).
Docker, npm and PyPI
JFrog Container Registry (JCR) is JFrog’s free container edition, and its page says “JCR includes capabilities that OSS does not, including Docker, OCI, and Helm package types” (JFrog’s Container Registry page, read 2026-10-23). The OSS lists on that page and on the matrix name no npm, Docker or PyPI repository (JFrog’s Container Registry page and JFrog’s Feature Comparison Matrix, read 2026-10-23).
JFrog’s pages disagree
The Container Registry page says Maven, npm and PyPI are not available in JCR, then adds “Those formats are available in Artifactory OSS or a commercial Artifactory subscription” (JFrog’s Container Registry page, read 2026-10-23). The edition table on that page and the Feature Comparison Matrix both list OSS without npm, Docker or PyPI, and our own finding above matches them (JFrog’s Container Registry page and JFrog’s Feature Comparison Matrix, read 2026-10-23). That is one release, so check the package types your own server offers before you plan around either.
Your options
Stay on Artifactory OSS
If your repositories are Maven, Gradle, Ivy, SBT or Generic, JFrog lists OSS for all of them (JFrog’s Feature Comparison Matrix, read 2026-10-23). npm, Docker and PyPI are not on that list.
Run JFrog Container Registry for Docker
JFrog describes JCR as “a free, self-managed edition of JFrog Artifactory that is limited to container and Helm workflows” (JFrog’s Container Registry page, read 2026-10-23). The page lists Docker, OCI, Helm, Helm OCI and Generic for it, and says Maven, npm and PyPI are not available in it (JFrog’s Container Registry page, read 2026-10-23). That covers Docker and leaves npm and PyPI open.
Buy Artifactory Pro
JFrog’s table of its editions lists “Artifactory Pro and the JFrog Platform” for “All Artifactory package types” (JFrog’s Container Registry page, read 2026-10-23). Get a quote, then compare it with our plans.
Before you sign a quote, send it to us. We’ll give you a very competitive counteroffer.
Move to a managed repository
CloudRepo is a managed artifact repository for Maven, npm, PyPI and Docker: we run the servers, the upgrades and the patches. All four are on every plan, with unlimited repositories and users, and each self-serve plan starts with a 14-day free trial. Our docs cover Maven, npm, Python (PyPI) and Docker repositories, and the plans list what each costs.
If your Artifactory server holds local Maven repositories, cloudrepo-migrate artifactory moves them in one command. Install it, then do a dry run, which lists what would move and uploads nothing.
pipx install cloudrepo-migratecloudrepo-migrate artifactory --artifactory-url https://artifactory.example.com/artifactory --org your-org --dry-runWithout --dry-run, cloudrepo-migrate artifactory moves an Artifactory server’s local Maven repositories and reads each file back from CloudRepo to check it. Version 0.6.0 of cloudrepo-migrate is tested against a real Artifactory OSS 7.146.39 server, with local Maven repositories.
It reads your Artifactory token from ARTIFACTORY_ACCESS_TOKEN and your CloudRepo token from CLOUDREPO_TOKEN: set them in your shell, never on the command line. The Artifactory migration guide has the steps.
A repository of another format is skipped, with a reason, in the report. Copy those files with the commands you already use.
Every JFrog page this article cites was read on 2026-10-23. Vendors change their documentation, so check each page before you decide.