Switching Image Registries Is Easy
Joe Zeng, software engineer at Statsig, on using Docker
This shows Docker Hub is a weak lock in point, while Docker’s stronger hold comes from sitting on the developer desktop and inside daily build workflows. For a team already running Kubernetes on Azure, swapping the image registry mostly means repointing image URLs and credentials, not rewriting apps. That is why a Docker Hub outage could push temporary traffic to Azure Container Registry, and why price sensitivity shows up first at the registry layer, not in core container workflows.
-
At Statsig, Docker was a small enough line item that the team stayed put, but the stated churn threshold of above $1000 per month shows registries are judged like commodity infrastructure. If another registry can store the same images and serve the same pulls, pricing discipline matters more than product attachment.
-
Docker rebuilt the company around monetizing developers and their managers, not around charging ops teams for orchestration. The paid wedge was low cost seats on Docker Desktop and Docker Hub, then expansion into team features like SSO, usage controls, and security signals once usage was already established.
-
The practical reason switching is easy is that containers are built to be portable. Teams can run the same image format across Docker Desktop, Kubernetes, AWS, and Azure. The registry is mostly the storage and distribution endpoint where those images live, so replacing it is much easier than replacing the broader container toolchain.
The next step is for registries to become less of a standalone business and more of a bundled surface for security, policy, and developer workflow products. That pushes Docker to keep moving up the stack, into desktop tooling and build time safety, where switching costs are higher and where customers will pay for more than simple image storage.