---
title: "Harbor private registry: the same image on every machine"
description: "When a self-hosted Harbor is worth it, what gets delivered, how storage and backups are planned, and when registry:2 is enough."
canonical: "https://localdeploy.dev/services/harbor"
source: "content/pages/services/harbor.md"
lang: "en"
altPath: "/zh/services/harbor"
---


## When you need it

Images live on one machine, so the next one has to rebuild. With a team, nobody can say which image is current and which is from last week. A private Harbor means several machines pull the same version, and a rollback is a tag change.

## What gets delivered

- Harbor deployment: Compose or Helm, whichever suits your machines.
- Projects, users and permissions: who can pull, who can push, what is public.
- Storage planning: local disk or S3-compatible object storage, and a capacity estimate.
- Garbage collection and retention: when a deleted tag actually frees space.
- Backups: configuration, database and image metadata, plus a restore check.
- An upgrade path: the intermediate versions to pass through when the jump is large.
- Migration from local images: retag, push, update the image references.

## Not included

- Auditing what is inside the images. That stays with you.
- CI pipeline changes; you get push and pull command examples.
- Storage and backup media. Disks, object storage and off-site copies are yours.

## Who it fits

You build images often, need rollbacks, or share a set of images across machines. With one machine and occasional builds, `registry:2` or plain local images is enough; Harbor is more moving parts.

## How to start

Email how many machines, roughly how many images, where they are stored now, and where backups go. Scope first, then a quote.

## Questions

### What does Harbor add over registry:2?

Project permissions, replication, garbage collection, scanning and a web UI, at the cost of more components. For a small setup registry:2 is simpler; for several users and retention rules, Harbor pays off.

### How much disk?

It depends on image count and retention. The quote includes an estimate and a cleanup fallback command.

## Related

- [Traefik reverse proxy](/services/traefik)
- [k3d / k3s](/services/k8s)
- [Pricing and payment](/pricing)

## Structured data

```json
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "localdeploy.dev",
  "url": "https://localdeploy.dev/",
  "description": "localdeploy.dev helps home labs and small teams assess the hardware they already own, then deploy a local AI assistant with Cloudflare, self-hosting and containers. Free basics, fixed-scope deployment packages, clear boundaries."
}
```
