이미지: 버셀
Summary
- Vercel Container Registry added public repository access, allowing any team with a Vercel account to pull images.
- Public access is limited to read-only, and repositories remain private by default.
- Repository visibility can be changed through three methods: the dashboard, CLI, or REST API.
What changed
Vercel Container Registry added public repository access on August 7, 2026. Previously, the registry's sharing feature only allowed granting read access to up to 100 designated teams. As the number of teams grew, managing that team list became a manual burden, and there was no way to open images to an unspecified pool of Vercel users.
With this update, switching a repository to "public" status lets any team with a Vercel account pull and use the images without any additional permission setup. Unlike the previous team-based sharing, there's no cap on how many teams can access a public repository. Repositories remain private by default, and switching to public requires an explicit configuration change.
Scope and limits of public access
Public access is designed to be read-only. While pulling and using images is allowed, pushing new images, deleting existing ones, or otherwise modifying repository contents is not permitted. This clearly limits public repositories to functioning solely as an image distribution channel.
Public images also integrate with Vercel Sandbox. When calling Sandbox.create(), passing a team-scoped image reference in the format their-team/their-project/their-repository:latest to the image field will load the public image directly. Vercel described this as working "the same way shared images work in Sandbox." Public access is limited to "teams with a Vercel account." External users without a Vercel account cannot access public repositories.
How to configure it: dashboard, CLI, API
Repository visibility can be changed through three methods. The first is via the project dashboard. Navigating to Images → repository → Settings → Public Access brings up a screen for setting visibility, and confirming the change requires typing in the repository name manually. This confirmation step acts as a safeguard against accidentally making a repository public.
The second method uses the Vercel CLI. The following commands switch a repository to public and back to private, respectively:
vercel vcr config <repository> --public true
vercel vcr config <repository> --public false
The third method is through the REST API. Vercel stated that the same visibility settings can be configured via the API, with details available in the official Vercel Container Registry documentation.
Context
Vercel describes itself as "agentic infrastructure for every app and agent," positioning its platform around humans and agents building software together. The container registry is an infrastructure component that aligns with this direction. Vercel Sandbox, an isolated execution environment for agents to run code, operates based on container images. The newly added public registry feature appears aimed at scenarios where multiple teams share a common base image to standardize agent environments, or distribute images externally.
This announcement did not arrive in isolation. Around the same time, GitHub Copilot released an API update that separates usage tracking by individual agent, and OpenAI announced improvements to GPT-5.6 Sol for Plus and Pro users alongside plans to switch free-tier users to a new default model — part of a broader wave of agent-focused infrastructure and tooling updates. Vercel's public container registry feature arrives within this trend, aimed at reducing friction in image sharing between teams.
