> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/artifact-registry/3.0/get-started/artifacts-overview.md).

# Overview

Learn what Harness Artifacts is, the artifact types and package formats it supports, and the capabilities that make it more than simple storage.

Harness Artifacts is a universal artifact registry that stores, proxies, secures, and governs every artifact type your teams build, deploy, and depend on.

## What is an artifact

An **artifact** is any file your build process produces or your application depends on at deploy time. Container images, language packages, Helm charts, compiled binaries, machine-learning models, and raw files are all artifacts. When a CI pipeline finishes a build, the output it publishes is an artifact. When a CD pipeline deploys a service, the thing it pulls is an artifact. When a security scanner checks your software supply chain, the thing it inspects is an artifact.

In a modern software delivery workflow, artifacts connect every stage: build, deploy, scan, and govern. Every team that ships software depends on artifacts, whether they think about them that way or not.

## What is Harness Artifacts

**Harness Artifacts** is an artifact registry built into the Harness platform. It stores, secures, and distributes every artifact your teams build, deploy, and depend on, under the same RBAC, policies, and audit trail that govern your pipelines.

Every artifact your software delivery lifecycle produces and consumes lives here: the image your build generates, the package your deployment pulls, the artifact your security team scans, and the audit trail compliance relies on for traceability.

***

## Core capabilities

### Universal format support

Harness Artifacts supports 26 package formats spanning every major programming language, package ecosystem, Linux distribution, and infrastructure toolchain. Whether your team builds containers, publishes Python libraries, ships Debian packages, or manages Terraform modules, you store and govern every artifact type in one place.

| Ecosystem                      | Formats                                       |
| ------------------------------ | --------------------------------------------- |
| **Containers and Kubernetes**  | Docker, Helm OCI, Helm HTTP                   |
| **Java Virtual Machine (JVM)** | Maven, Gradle                                 |
| **JavaScript and TypeScript**  | npm                                           |
| **Python and data science**    | Python / PyPI, Conda, Hugging Face            |
| **Systems and native**         | Go modules, Cargo, Conan, Swift               |
| **.NET and Windows**           | NuGet                                         |
| **Linux packages**             | Debian / APT, Alpine / APK, Wolfi / APK, RPM  |
| **Web and scripting**          | PHP Composer, Ruby / RubyGems, R / CRAN, Dart |
| **Infrastructure as code**     | Terraform, Terraform Backend                  |
| **General purpose**            | Generic / Raw, Puppet                         |

To see every format with its client tools and setup guide, go to [Supported formats](https://developer.harness.io/artifact-registry/3.0/get-started/supported-formats.md).

### Upstream proxies and caching

An **upstream proxy** sits between your team and a public registry such as Docker Hub, Maven Central, npm, or PyPI. On the first pull, Harness fetches the package from the upstream source, caches it, and serves it. Every subsequent pull comes from the cache, with no network call to the internet. Your builds continue even when the upstream source is unavailable or rate-limited.

Every format supports upstream proxies. To understand how local registries and upstream proxies work together, go to [Registries and upstream proxies](https://developer.harness.io/artifact-registry/3.0/concepts/registries-and-upstream-proxies.md).

### Automatic security scanning and quarantine

Every container image pushed to a Docker or Helm registry with scanning enabled is automatically scanned for vulnerabilities by Aqua Trivy or Grype. Harness generates an SBOM alongside the scan, recording every component, its version, its license, and its supplier.

If an image fails a security policy, it is automatically **quarantined** and blocked from being pulled until a security admin reviews and releases it. Problematic artifacts never reach production, even if a developer pushes them.

Harness Artifacts integrates with [Harness Security Testing Orchestration (STO)](https://developer.harness.io/security-testing-orchestration/) for vulnerability scanning and [Harness Supply Chain Security (SCS)](https://developer.harness.io/software-supply-chain-assurance/) for SBOM generation, providing a single, trusted software supply chain where every artifact is verified, traceable, and secure.

### Dependency Firewall

**Dependency Firewall** evaluates open-source packages at the upstream proxy boundary, before they are cached in your registry. When a developer or pipeline requests a package, Harness checks it against your configured policies. A package can be blocked, allowed through, or allowed with a warning. Five built-in policy templates cover the most common supply chain risks: CVSS vulnerability threshold, license compliance, package age, OSS health score, and malicious package detection.

To learn how Dependency Firewall works, go to [Dependency Firewall](https://developer.harness.io/artifact-registry/3.0/concepts/dependency-firewall.md).

### Lifecycle management

Registries accumulate thousands of artifact versions over time. **Lifecycle rules** automate cleanup so your registries stay manageable. A **cleanup rule** deletes versions that match your criteria (for example, older than 90 days and not downloaded in 30 days) on a schedule. A **retention rule** permanently protects matching versions from any cleanup. Retention always wins. Deleted versions go through a soft-delete recovery window before permanent removal, so a misconfigured rule does not cause irreversible data loss.

To configure cleanup and retention, go to [Lifecycle Management](https://developer.harness.io/artifact-registry/3.0/lifecycle-management/overview.md).

### Native platform integration

Harness Artifacts is not a standalone tool. It is natively integrated into the Harness platform:

* **Harness CI**: use the Build and Push step to publish artifacts directly to a registry with no external connector required.
* **Harness CD**: select artifacts from your registries as deployment sources. The Deployments tab on each artifact version shows where it is running and how many instances are active.
* **Security (STO and SCS)**: vulnerability findings and SBOMs appear directly on the artifact version details page.
* **Policy as Code (OPA)**: define and enforce custom policies for artifact publishing, promotion, and deletion.

### Fine-grained access control

Role-based access control (RBAC) applies at the registry level for all formats. Three built-in roles cover the most common access patterns:

| Role                              | What it allows                                                                                |
| --------------------------------- | --------------------------------------------------------------------------------------------- |
| **Artifact Registry Viewer**      | View registries and browse artifact contents                                                  |
| **Artifact Registry Contributor** | Push to and pull from registries, in addition to Viewer permissions                           |
| **Artifact Registry Admin**       | Full access: create, configure, and delete registries, in addition to Contributor permissions |

Registries exist at a scope: account, organization, or project. The scope determines visibility. A registry at the account scope is available to your entire organization. One at the project scope is visible only within that project.

### Multi-region replication

When you push an artifact, Harness stores it in your primary region and replicates it to a disaster recovery bucket. On the first pull from a different region, the artifact is copied to the nearest regional bucket. Subsequent pulls from that region are served locally. Supported regions include US-West, US-East, EU-West, EU-East, Asia-Pacific, and Oceania. Routing is automatic based on client IP.

***

## Frequently asked questions

<details>

<summary>How is Harness Artifacts licensed?</summary>

Harness Artifacts is a licensed module on your Harness account. Pricing is based on the storage you use. Harness stores and counts each unique file or image layer once per account, so uploading identical content does not add to your storage. To enable it, contact your Harness sales representative or <ar-interest@harness.io>.

</details>

<details>

<summary>Is there a limit on how many packages or how much data a registry can store?</summary>

No. Harness Artifacts does not enforce a limit on the number of registries, packages, or versions in your account, and it does not apply a storage quota. You pay for the storage you use.

</details>

<details>

<summary>Does one registry contain environments?</summary>

No. A registry does not contain environments. To track environments, add custom metadata (for example, `environment: production`) to a registry, package, or version. If you deploy with Harness CD, the **Deployments** tab on a version shows the environments where that version is running.

</details>

<details>

<summary>Is artifact promotion behind a feature flag?</summary>

No. To promote an artifact, copy its version from one registry to another using **Copy Version** in the UI, the `hc artifact copy` CLI command, or the Copy API. Both registries must have the same package type. Go to [Copy a version](https://developer.harness.io/artifact-registry/3.0/artifacts/copy-a-version.md) for instructions.

</details>

***

## Next steps

* To push your first artifact, go to [Quickstart: push your first artifact](https://developer.harness.io/artifact-registry/3.0/get-started/quickstart.md).
* To understand the core concepts behind Harness Artifacts, go to [Key concepts](https://developer.harness.io/artifact-registry/3.0/get-started/key-concepts.md).
* To create a registry for your format, go to [Create a registry](https://developer.harness.io/artifact-registry/3.0/registries/create-a-registry.md).
* To configure your package manager client, go to the [Client Setup](https://developer.harness.io/artifact-registry/3.0/setup/docker.md) guide for your format.
* To inspect a version's metadata, SBOM, and vulnerabilities, go to [Artifact version details](https://developer.harness.io/artifact-registry/3.0/artifacts/artifact-version-details.md).
* To automate artifact cleanup and retention, go to [Lifecycle Management](https://developer.harness.io/artifact-registry/3.0/lifecycle-management/overview.md).
* To see how Harness Artifacts fits into a broader CI/CD and security workflow, go to [How Artifacts fits your workflow](https://developer.harness.io/artifact-registry/3.0/get-started/how-ar-fits-your-workflow.md).

{% @harness-feedback/feedback %}
