Introducing Multiple Registry Support on DigitalOcean Container Registry

Introducing Multiple Registry Support on DigitalOcean Container Registry Introducing Multiple Registry Support on DigitalOcean Container Registry What is Multi-Registry support, and why does it matter? Benefits of Multiple Registries How to use the new Multi-Registry feature on DigitalOcean 1. Via the Control Panel 2. Via the API 3. Via the CLI Handling limitations and edge cases Get started today About the author(s) Try DigitalOcean for free Related Articles Introducing Moltbot on DigitalOcean: One-Click Deploy, Security-hardened, Production-Ready Agentic AI Powering the Next Leap in AI: GPU Droplets accelerated by NVIDIA HGX™ B300 are coming soon to DigitalOcean Evaluate your AI agents faster and more effectively By Kang Xie and Ravish Ahmad Khan Published: January 9, 2026 4 min read At DigitalOcean, we’re dedicated to enhancing our container registry experience, providing users with a simple, powerful tool to organize, manage, and deploy containerized applications. Today, we’re excited to announce the General Availability (GA) of a major enhancement to our container registry: the ability to create and manage multiple registries under a single team. Available to customers on the Professional Plan at no additional cost , this feature enables the creation of up to 10 registries per team , delivering great flexibility of image rollout on DigitalOcean. Previously, although one DigitalOcean Container Registry (DOCR) account could create multiple teams, each team was limited to a single container registry. With this update, Professional Plan customers can now create up to 10 registries under a single team, each housing its own independent set of repositories and configurations. This architecture is designed for users managing distinct environments (like development, staging, production) or distributed teams, allowing for compartmentalized registry management. Environment isolation: Segregate different deployment stages (such as dev vs. prod). Environment isolation: Segregate different deployment stages (such as dev vs.