> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/aikido-device-protection/using-aikido-endpoint/custom-registries.md).

# Custom Registries

If your team installs packages through a private registry like AWS CodeArtifact or JFrog Artifactory, add its domain in Aikido. Device Protection only inspects installs on domains it knows about.

Packages served through a registered domain are checked for malware exactly like packages from the public registry, and your existing installation policies apply to them too.

## How it works

When you register a custom registry, Device Protection recognizes its domain as a proxy for a public ecosystem. Package installs that flow through that domain are inspected on the device and checked against Aikido's malware signatures, just like installs from the public registry itself. Your existing [installation policies](/aikido-device-protection/using-aikido-endpoint/configuring-installation-policies.md) apply to these installs too.

## Add a custom registry

1. Go to [Custom Registries](https://app.aikido.dev/endpoint-protection/custom-registries) in your Aikido account.
2. Click **Add Custom Registry**.
3. Select the registry **Type**: AWS CodeArtifact or JFrog Artifactory.
4. Enter the registry **Domain**, for example `my-org.d.codeartifact.us-east-1.amazonaws.com` or `my-company.jfrog.io`.
5. For JFrog Artifactory, select the **Ecosystem** that the repository proxies (for example Npm) and enter its **Repository Key** (for example `npm-remote`).
6. Save.

A JFrog repository key maps to a single ecosystem, so add a separate entry for each repository you use.

<figure><img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2Fgit-blob-84be678cdd49b2ee25b1bb5b105811921bbfa0df%2FScreenshot%202026-09-18%20at%2016.38.49.png?alt=media" alt="" width="375"><figcaption></figcaption></figure>

The registry now appears in the list with its type and domain. Use the **⋮** menu on a row to edit or remove it.

<figure><img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2Fgit-blob-ed3dd2ae8f69f01eb7fae4a4099376a3500f6843%2FScreenshot%202026-07-27%20at%2017.38.57.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.aikido.dev/aikido-device-protection/using-aikido-endpoint/custom-registries.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.