Description
Every build on the team pulls dependencies straight from the public internet: hundreds of repeat downloads a day, a pipeline that breaks the moment an upstream package is yanked, and no way to say which machine used which version when a security issue lands.
Artifactory OSS is JFrog’s open-source artifact repository: it proxies public repositories with a local cache and takes your own builds too, so everyone fetches from one place. A dependency pulled once is served from the LAN afterwards, survives upstream deletions, and every artifact records where it came from, who uploaded it and which build used it.
The OSS edition covers Maven, Gradle, Ivy and SBT repositories plus a generic binary store — enough for a Java team. The Windows installer is 1.7 GB; Linux, Docker and Helm installs are available as well.
Remote repository proxy: proxies Maven Central and similar, caching what is pulled so builds stop depending on the internet.
Local repositories: publish your own build outputs here, versioned and shared across the team.
Virtual repositories: aggregate several local and remote repositories behind one URL so clients configure a single address.
Auth and permissions: LDAP integration and role-based access control, with read and deploy rights managed separately.
Metadata and search: every artifact carries properties and checksums and can be found by coordinates or attributes.
Several ways to deploy: Windows installer, Linux tar.gz/rpm/deb, Docker Compose, Helm chart.
Artifactory OSS is JFrog’s open-source artifact repository: it proxies public repositories with a local cache and takes your own builds too, so everyone fetches from one place. A dependency pulled once is served from the LAN afterwards, survives upstream deletions, and every artifact records where it came from, who uploaded it and which build used it.
The OSS edition covers Maven, Gradle, Ivy and SBT repositories plus a generic binary store — enough for a Java team. The Windows installer is 1.7 GB; Linux, Docker and Helm installs are available as well.
Features
Remote repository proxy: proxies Maven Central and similar, caching what is pulled so builds stop depending on the internet.
Local repositories: publish your own build outputs here, versioned and shared across the team.
Virtual repositories: aggregate several local and remote repositories behind one URL so clients configure a single address.
Auth and permissions: LDAP integration and role-based access control, with read and deploy rights managed separately.
Metadata and search: every artifact carries properties and checksums and can be found by coordinates or attributes.
Several ways to deploy: Windows installer, Linux tar.gz/rpm/deb, Docker Compose, Helm chart.
Screenshots
Tags:artifact-repository