Artifactory Overview

Learn how Artifactory manages binaries, packages, and builds across your teams.

JFrog Artifactory is a universal DevOps solution providing end-to-end automation and management of binaries and artifacts through the application delivery process that improves productivity across your development ecosystem.

Artifactory supports more than 40 software build packages, all major CI/CD platforms, and DevOps tools that you already use. For more information, see Supported Package Types.

Artifactory is Kubernetes-ready and supports containers, Docker, and Helm charts. You can use Artifactory as your Kubernetes and Docker registry. Artifactory also comes with full CLI and REST APIs that you can customize to your ecosystem.

Explore JFrog Artifactory

Key Benefits of Artifactory

Artifactory helps you manage and distribute software packages across teams, tools, and environments.

  • Flexible deployment: Use Artifactory as a self-managed service, as SaaS, or across hybrid and multi-cloud environments.
  • Universal package management: Manage more than 40 package formats in one place, including container images and Helm charts. You can also use Artifactory as a registry for Kubernetes deployments. For more information, see Working with Package Management.
  • Traceable and reproducible builds: Capture package, artifact, dependency, environment, and build metadata. This information helps you reproduce builds and trace deployed software back to its source. For more information, see Build Integration.
  • Scalable and resilient operations: Support growing workloads with horizontal scaling, high availability, and live failover. You can store binaries with S3 Object Storage, Google Cloud Storage, Azure Blob Storage, and Filestore Sharding. For more information, see High Availability.
  • Integrated automation and search: Automate repository and artifact management through REST APIs, and find content with Artifactory Query Language (AQL). For more information, see OpenAPI Specifications and Artifactory Query Language.
🐸

Learn more about Artifactory at JFrog Academy!

How Your Team Can Use Artifactory

Different job roles in your organization may interact with and benefit from Artifactory. Each organization and team has its own structure, and smaller companies may have one person filling multiple job roles. The following table describes each role's primary goal and Artifactory workflow.

Job rolePrimary goalArtifactory workflow
DevOps and Platform EngineeringAutomate artifact management and standardize pipeline delivery across teams.DevOps and platform engineers install and configure Artifactory and integrations. They may also use JFrog CLI and AQL to inspect repositories and prototype commands interactively, then package those commands into reusable CI/CD pipeline templates, repository cleanup scripts, and developer onboarding tools.
DevelopersResolve and publish packages through Artifactory, and add only dependencies that pass security checks.Developers can use Set Me Up to point package manager clients to Artifactory. If JFrog Security is configured, it can scan packages that developers resolve through Artifactory for vulnerabilities, and a policy can allow or block a package based on the scan results.
Security EngineersFind vulnerabilities, license issues, and exposed secrets in your Git repositories.Security engineers may perform tasks like setting up the Frogbot Git bot to scan a repository when a pull request opens and to run a scheduled scan of the whole repository. Frogbot can also check dependency licenses and detect secrets. A DevOps engineer typically helps with the initial setup.
CI Pipeline SpecialistsIntegrate Artifactory into CI/CD pipelines.CI pipeline specialists can use JFrog SDKs to connect Artifactory to the CI/CD process so builds resolve and publish artifacts as part of the pipeline.
Data ScientistsManage machine learning models with the same traceability as other software packages.Data scientists can store and maintain machine learning models in Artifactory as part of package management, so each model stays traceable through the software development lifecycle.
Compliance Officers and Technical WritersConfirm release evidence for external audits and for release notes.With limited access to Artifactory, other team members can review the audit trail of releases after an external audit. For example, a technical writer may review JFrog Xray Release Bundle scan results to confirm resolved CVEs for release notes.

Related Topics


Did this page help you?