> 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/registries/create-a-registry.md).

# Create a registry

Create a registry to store and manage artifacts of any supported format, at account, organization, or project scope, and set up client access.

A registry is the storage unit in Harness Artifacts. Each registry holds artifacts of a single format: Docker images, Maven packages, npm modules, Helm charts, and so on. You create one registry per format and give it a name that is unique across your entire Harness account, regardless of scope.

Registries can be created at **Account**, **Organization**, or **Project** scope. The scope determines who can see and use the registry. Navigate to the scope you want before you create the registry.

## Before you begin

Your role must include **Create/Edit** permission on Artifact Registry at the scope where you want to create the registry. Go to [RBAC and permissions](https://developer.harness.io/artifact-registry/3.0/reference/rbac-and-permissions.md) to review permission requirements.

## Create a registry

1. In the navigation menu, select **Registries**.
2. Select **Create registry**.
3. In the **Create a new artifact registry** drawer, select the registry type that matches the package format you want to store.
4. Enter a **Registry Name**.

   Registry names must start with a letter and can only contain lowercase letters, numbers, underscores (`_`), hyphens (`-`), and periods (`.`).
5. Optionally, enter a **Description**.
6. Set **Visibility** to **Private** or **Public**.

   * **Private**: Only users or service accounts with the required permissions can view and pull from this registry.
   * **Public**: Anyone can view the registry contents and pull artifacts without authentication.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>The <strong>Public</strong> option may not appear if public registry visibility has not been enabled for your account. Go to <a href="https://developer.harness.io/artifact-registry/3.0/registries/set-registry-visibility.md">Set registry visibility</a> for details.</p></div>
7. Select **Create registry**.

The new registry opens immediately. Select **Setup Client** from the row menu to get the authentication commands for your format.

## Supported registry types

Harness Artifacts supports the following formats. Select the type that matches your toolchain when you create the registry.

| Format            | Use for                                                         |
| ----------------- | --------------------------------------------------------------- |
| Docker            | Container images (OCI-compatible)                               |
| Helm OCI          | Helm charts stored as OCI artifacts                             |
| Helm HTTP         | Classic Helm chart repositories (`helm repo add` / `helm pull`) |
| Maven             | Java packages (Maven, Gradle, SBT)                              |
| npm               | JavaScript and Node.js packages                                 |
| Python / PyPI     | Python packages (`pip`, `Poetry`, `uv`)                         |
| NuGet             | .NET packages                                                   |
| Cargo             | Rust packages                                                   |
| Go                | Go modules                                                      |
| Generic / Raw     | Arbitrary files by path                                         |
| RPM               | Red Hat, CentOS, Fedora packages                                |
| Debian / APT      | Debian and Ubuntu `.deb` packages                               |
| Alpine / APK      | Alpine Linux packages                                           |
| Wolfi / APK       | Wolfi Linux packages                                            |
| Terraform         | Infrastructure as Code modules and providers                    |
| Terraform Backend | Terraform remote state backend                                  |
| Hugging Face      | Machine learning models and datasets                            |
| Conda             | Python and R packages (Anaconda-compatible)                     |
| Dart              | Dart and Flutter packages                                       |
| PHP Composer      | PHP packages (Packagist-compatible)                             |
| Swift             | Swift packages (SwiftPM)                                        |
| Conan             | C and C++ packages                                              |
| Ruby / RubyGems   | Ruby gems                                                       |
| R / CRAN          | R packages (CRAN-compatible)                                    |
| Puppet            | Puppet modules (Puppet Forge-compatible)                        |

Go to [Supported formats](https://developer.harness.io/artifact-registry/3.0/get-started/supported-formats.md) for the full list with protocol details and client setup links.

## Next steps

* [Set registry visibility](https://developer.harness.io/artifact-registry/3.0/registries/set-registry-visibility.md): switch an existing registry between Private and Public
* [Create an upstream proxy](https://developer.harness.io/artifact-registry/3.0/registries/create-an-upstream-proxy.md): proxy requests to Docker Hub, Maven Central, or other external registries
* [Add and prioritize upstream proxies](https://developer.harness.io/artifact-registry/3.0/registries/add-and-prioritise-upstream-proxies.md): attach one or more upstream proxies to a registry

{% @harness-feedback/feedback %}
