Vex Hub registry

Vex Hub repositories live at registry.vex.sc/<org>/<repository>. Vex-issued authorization supports Docker pulls and pushes and can be used by platform builders that have appropriate organization access.

That slug reference is the one to copy and share. Behind it, images are stored under your organization's immutable numeric id (registry.vex.sc/<org-id>/<repository>), so renaming an organization never moves a layer. Both references pull the same image; the numeric one is an internal storage detail that also keeps working, and it is what deploy records persist.

Set up Docker

For most workflows, configure the Docker credential helper once. It keeps credentials scoped to registry.vex.sc and refreshable through Vex.

vex docker setup
vex registry login --registry registry.vex.sc

Repositories and tags

Create or list an organization repository, then push an image with an explicit tag.

vex registry list --org <org>
vex registry create --org <org> --slug <item>
vex registry push <image> --org <org> --repo <item> --tag <tag>

Use docker push and docker pull after vex docker setup when a normal Docker workflow is the better fit.

Auth boundary

Registry authorization is scoped to the organization and repository access granted to the caller. A registry token is not a replacement for a browser session or a general control-plane token. Use hosting for deploy workflows that consume those images.