Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
upstream: github.com/project-zot/zot (opens in new tab) · github.com/goharbor/harbor (opens in new tab)
Pick zot
If you want one small OCI-native registry with a single config file, built-in authentication options, inline garbage collection and the simplest install.
Pick Harbor
If you need projects with role-based access, replication policies and audit logs for several teams, and can give it a 4 GB plan.
zot and Harbor are two of the self-hosted container registries in our catalog, and they sit at opposite ends of the weight scale. zot is a single Go binary that speaks the OCI distribution API and stores images as files. Harbor is a CNCF project with a full set of containers behind its installer: core services, a job service, a portal, PostgreSQL and Redis. Both can sit in front of your pulls as a cache, both scan for vulnerabilities, and both have a web UI. The question is how much registry management you want.
zot's own site describes an "OCI-native container image registry, simplified", shipped as "one statically built binary ... with no additional dependencies or services." It "strongly conforms to OCI Standards", does not need "elevated privileges on host", and has "all features such as security scanning, authentication, authorization, garbage collection, deduplication" in the same binary. It is released under Apache 2.0 and was accepted as a CNCF Sandbox project.
Harbor's README says it is "an open source trusted cloud native registry project that stores, signs, and scans content", built on the Docker Distribution project and hosted by the CNCF. Its feature list includes role based access control, policy-based replication, vulnerability scanning, LDAP/AD and OIDC support, image deletion and garbage collection, a graphical portal, auditing and a RESTful API with an embedded Swagger UI.
zot supports htpasswd (bcrypt only), LDAP such as Active Directory, OpenID and OAuth2 providers (GitHub, Google, GitLab and generic OIDC), API keys for Docker, Podman, containerd and kubelet, and mutual TLS. Access control is a per-repository policy file: default, user, group, anonymous, metrics and admin policies, with the longest matching repository path winning.
Harbor handles access through projects. Its role-based access control assigns permissions per project, and it can authenticate against LDAP/AD or an OIDC provider with single sign-on to the portal. If you have several teams who each want their own namespace and members, that project model is Harbor's main draw.
zot syncs from other registries in two ways: on demand, where an image is fetched from upstream on the first request and cached, or periodically, where it keeps a full copy and refreshes it when polling finds changes.
Harbor's proxy cache "allows you to use Harbor to proxy and cache images from a target public or private registry." When an image is already cached and upstream is unreachable, "the proxy cache project serves the cached image." Harbor's replication is policy-based and filter-driven for pushing and pulling between registries.
zot stores local files and can also use AWS S3, Google Cloud Storage or Azure Blob Storage. It deduplicates, and its garbage collection is inline: "it is not necessary to take the registry offline." A scrub extension scans stored images in the background to detect corruption.
Harbor offers image deletion and garbage collection "periodically" to reclaim unreferenced data, and logs all repository operations for audit.
Harbor's installation prerequisites list a minimum of 2 CPUs, 4 GB of memory and 40 GB of disk, and recommend 4 CPUs, 8 GB and 160 GB. Our page uses the 4 GB floor for Harbor and 512 MB for zot (our estimate). In our install check (GCP e2-standard-2, Ubuntu 26.04), idle at first boot with the default install snippet and no images pushed, zot used ~122 MB of RAM and ~2.6 GB of disk (November 2026), and Harbor used ~153 MB of RAM and ~2.2 GB of disk (October 2026). Those are idle numbers with an empty registry, not a registry under load; pushing, scanning and garbage collection will use more on both.
zot is 1 out of 5: a config file, an htpasswd file and one container.
Harbor is 3 out of 5: download the installer, edit harbor.yml, run
install.sh, and set up TLS before docker login works cleanly from another machine.
Choose zot if you want one small, OCI-native registry with a single config file, built-in authentication options, S3-style storage and the simplest install.
Choose Harbor if you need projects with role-based permissions, replication policies, audit logging and a registry platform for several teams, and can give it a 4 GB plan.
Both installs are verified on Ubuntu 26.04; the pinned snippets are on the zot and Harbor pages. Put TLS in front of either before pushing images from other machines, back up the storage directory (and Harbor's database), and plan disk for images, not for the registry itself.
zot lists a lower minimum: 512 MB vs 4096 MB for Harbor.
zot for a small, single-binary OCI registry with the simplest install. Harbor for projects, role-based access, replication and auditing across teams. Both idled at modest RAM in our first-boot check (~122 MB and ~153 MB), but Harbor runs several containers and lists a 4 GB minimum.
Harbor's installation prerequisites list a minimum of 2 CPUs, 4 GB of memory and 40 GB of disk, recommending 4 CPUs, 8 GB and 160 GB. Those are upstream figures, separate from our idle measurement.
Yes. zot's sync supports an on-demand mode, where an image is fetched upstream on the first request and cached, and a periodic mode that keeps a full copy and refreshes it when polling finds changes.
Harbor has proxy cache projects that cache images from a target registry and serve the cached copy if upstream is unreachable. zot covers a similar need through its on-demand sync.
Paid link — we earn a commission if you shop through it.
A multi-format artifact manager with a capped free edition, or an Apache-2.0 registry for container images and Helm charts.
A whiteboard-and-docs workspace on a plain Compose file vs. native apps on a commercial server.
A full identity platform vs. a passkey-only sign-in box.