> 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

Many teams don't install packages straight from the public registries. Instead they route them through a private registry that acts as a proxy or mirror of a public ecosystem, such as AWS CodeArtifact proxying npm or PyPI. Because those installs go to your private registry's domain rather than the public one, Device Protection needs to know about that domain to inspect the traffic.

Adding a custom registry tells Device Protection to treat that domain as a proxy for a supported public ecosystem. Packages served through it are checked for malware in exactly the same way as packages installed directly from the public registry.

## 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** (for example, AWS CodeArtifact).
4. Enter the registry **Domain** (for example, `my-org.d.codeartifact.us-east-1.amazonaws.com`).
5. Save.

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="/files/OdNIdKxrWWjPR0ocxvvE" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.