New server

Register a Dockerfile'd service. Harbor builds it, health-gates it, and serves it on a stable port.

Blue/green builds the new version in a second slot, health-checks it, then flips traffic atomically — no downtime, previous version kept warm for instant rollback.

New backup job

Scheduled archives with per-job retention. Archives are downloadable from the Backups page.

Import existing container

Register an EXISTING running container (Mongo/Redis) by name. Harbor inspects it read-only and gets dashboard visibility, TCP health, guarded start/stop, and backups. It never rebuilds, removes, or touches the volume — imported services can only be forgotten, never destroyed.

New data service

Create a NEW data container Harbor owns (Mongo/Redis/generic) with a named volume. It is labelled harbor.role=data and can only be removed by the guarded destroy action — never by a deploy.

New storage bucket

Create an object-storage bucket. Objects are served through Harbor's own gateway, so visibility is enforced by Harbor — not by R2.

Lowercase letters, digits and single hyphens (3–63 chars). Becomes part of the object URL.

Visibility

Deployment log