# Choose a Docker registry

Nutrient Document Engine images are available in two alternative Docker registries: [Docker Hub](https://hub.docker.com/r/pspdfkit/document-engine) and [Amazon ECR Public Gallery](https://gallery.ecr.aws/pspdfkit/document-engine). Images hosted in both registries are exactly the same. Which registry to choose will depend on your image pull frequency and deployment infrastructure.

## Docker Hub

When using Docker Hub, reference the Document Engine images using the `pspdfkit/document-engine` tag. For example, to pull the latest Nutrient Document Engine image, you’d run:

```sh

docker pull pspdfkit/document-engine:1.15.0

```

### Rate limits

On 1 November 2020, Docker began imposing a limit on the number of image pulls from Docker Hub available for non-paid accounts:

- 100 pulls per 6 hours for non-authenticated users

- 200 pulls per 6 hours for authenticated users

Note that the limits don’t apply to paid accounts. You can find the details on Docker’s [pricing page](https://www.docker.com/pricing).

You’ll know that you reached the limit when you see the following error when running `docker pull`:

`You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limits.`

If you find yourself hitting the limit frequently, we recommend either signing up for a paid Docker plan, or using the images from [Amazon ECR Public Gallery](#amazon-ecr-public-gallery).

## Amazon ECR Public Gallery

When using the Amazon registry, reference the Document Engine images using the `public.ecr.aws/pspdfkit/document-engine` tag. For example, to pull the latest Nutrient Document Engine image, you’d run:

```sh

docker pull public.ecr.aws/pspdfkit/document-engine:1.15.0

```

### Rate limits

The following pull image limits apply when using the Amazon registry:

- 500 GB of image data per month for non-authenticated users

- 5 TB of image data per month for authenticated users when pulling from non-AWS managed infrastructure

- Unlimited data transfer when pulling from AWS infrastructure

The Amazon registry is a great choice if you’re deploying Document Engine to AWS, or if you’re already using Amazon ECR to host your own images.

See the [Amazon ECR pricing page](https://aws.amazon.com/ecr/pricing/#Data_transferred_from_public_repositories.3A) for more details.
---

## Related pages

- [Deploying to Amazon Web Services](/guides/document-engine/deployment/aws.md)
- [Deploying to Google Cloud Platform](/guides/document-engine/deployment/google-cloud-platform.md)
- [Horizontal scaling](/guides/document-engine/deployment/horizontal-scaling.md)
- [Backup and recovery](/guides/document-engine/deployment/backup-and-recovery.md)
- [Deploying on Kubernetes with Helm](/guides/document-engine/deployment/helm.md)
- [Deploying on Kubernetes](/guides/document-engine/deployment/kubernetes.md)
- [Document Engine deployment overview](/guides/document-engine/deployment.md)
- [Application-specific timeouts](/guides/document-engine/deployment/ingress.md)
- [Deploying to Microsoft Azure](/guides/document-engine/deployment/microsoft-azure-aks.md)
- [Product activation](/guides/document-engine/deployment/product-activation.md)