> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/platform-administration/snyk-broker/snyk-broker-container-registry-agent/integrate-with-self-hosted-container-registries-broker.md).
# Integrate with self-hosted container registries
How to integrate self-hosted container registries with Snyk Broker, available on Enterprise plans
{% hint style="info" %}
**Feature availability**
Self-hosted container registries with Snyk Broker are available only with Enterprise plans.
For more information, see [plans and pricing](https://snyk.io/plans/).
{% endhint %}
Snyk can integrate with self-hosted private container registries that are not internet-accessible and can help you to better secure container images in those registries.
To enable and configure your hosted container registry, contact your Snyk team.
## **Solution components of self-hosted container registries**
Integration with self-hosted container registries contains the following components:
* Broker Server - running on Snyk SaaS backend
* Broker Client and Container Registry Agent - two Docker images deployed in your infrastructure, creating two separate services responsible for sampling your container registries in a secured manner and sending the allowed information to Snyk.
High-level architecture of the Snyk Broker Container Registry Agent
The Broker Client provides the Agent with the connection details. The Agent uses these details to connect to the container registry, scan the images, and send the scan results through the brokered communication using callbacks.
The brokered communication happens when a Broker Client connects (using your Broker ID) to a Broker server that runs within the Snyk environment.
For more details, see [Snyk Broker - Container Registry Agent](/platform-administration/snyk-broker/snyk-broker-container-registry-agent.md).
## **Supported container registries**
* Docker Hub (type: docker-hub)
* GCR (type: gcr)
* ECR (type: ecr)
* Azure (type: acr)
* Artifactory (type: artifactory-cr)
* Harbor (type: harbor-cr)
* Quay (type: quay-cr)
* GitHub (type: github-cr)
* Nexus (type: nexus-cr)
* DigitalOcean (type: digitalocean-cr)
* GitLab (type: gitlab-cr)
* Google Artifact Registry (type: google-artifact-cr)
---
# 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://docs.snyk.io/platform-administration/snyk-broker/snyk-broker-container-registry-agent/integrate-with-self-hosted-container-registries-broker.md?ask=&goal=
```
`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.
