v1

Build /

Use custom build registry

By default, Northflank stores all build images in Northflank's managed Docker registry. If your organization requires builds to push to your own Docker registry instead, you can use a custom build registry integration.

This feature lets you store built images in your cloud provider's container registry (Azure, AWS, or GCP) instead of Northflank's managed registry. This is useful if you need to maintain images in your own infrastructure, comply with internal policies, or integrate with existing registry workflows.

Prerequisites

Before setting up a custom build registry, you need:

  • A provider link: You must have created a provider link with your cloud provider (Azure, AWS, or GCP) in your team integrations. Learn how to set up a provider link

  • Required permissions enabled: Your cloud provider integration must have these features enabled:

    • Docker Registries: Allows pulling images from your registry
    • Docker Registry Push: Allows pushing built images to your registry

    If these features are not enabled, you cannot use that provider link for custom build registries.

  • New project: Custom build registries can only be configured when creating a new project, not on existing projects. This is because the registry setting is applied at the project level during creation.

How it works

When you configure a custom build registry in a project:

  1. Northflank builds your code using your Dockerfile or buildpacks
  2. Instead of pushing the built image to Northflank's managed registry, it pushes directly to your cloud provider's Docker registry
  3. Your deployments pull from your custom registry instead of Northflank's

This gives you full control over where your built images are stored and who can access them through your cloud provider's access controls.

Add a custom Docker registry

Click here to add a custom Docker registry.
  1. Navigate to Integrations in your team settings

  2. Click RegistriesAdd registry

  3. Enter a registry name and select your container registry provider (Azure, AWS, or GCP)

  4. Select an existing provider integration or create a new one for Azure, AWS, or GCP Learn how to set up a provider integration

  5. Enter the provider-specific registry settings:

    • GCP: Registry URL and project ID
    • AWS: Registry URL and region
    • Azure: Registry URL and resource group
  6. Under Select the permissions you want to grant to this registry, enable Push access (write images)

  7. Click Add registry

The registry is now available for use in new projects.

Use in a project

Click here to create a new project.
  1. Create a new project

  2. Under Advanced options, expand Docker Registry settings

  3. Set Registry Mode to Self Hosted

  4. Under Registry, select your custom registry integration

  5. Click Create project

All builds in this project will now push images to your custom registry instead of Northflank's managed registry. When you deploy these images, Northflank automatically pulls from your custom registry. Learn more about creating a project

© 2026 Northflank Ltd. All rights reserved.

northflank.com / Terms / Privacy / feedback@northflank.com