What is
Harbor
?
Most platform initiatives fail the same way: they start too big, get funded like projects instead of products, build for too long without testing with users, and confuse renaming an infrastructure team with building a platform team. Instead, start small, learn fast and scale deliberately.
At a glance
Attribute | Details |
|---|---|
Primary use case | Store, manage, scan, and sign container images and cloud-native artifacts |
Deployment type | Self-hosted on Kubernetes or a Docker-capable system |
Pricing model | Open source; commercial pricing not specified |
API compatibility | OCI artifacts, Docker Distribution |
Supported integrations | Kubernetes, Docker, Anchore Enterprise, replication across container registries |
Source type | Open |
Cloud provider | Cloud Agnostic |
Required skills | Docker or Kubernetes deployment and administration, container registry management, HTTPS configuration, identity integration and role-based access control |
AEP branch | Tooling |
AEP category | Integration & Delivery |
AEP subcategory | Registry |
Profile
Registry is Harbor's most specific AEP level. Harbor is an open-source registry for storing and managing container images and cloud-native artifacts. It scans images for vulnerabilities, supports trusted image signing, and provides policies and role-based access control. The project is a CNCF Graduated project and can be installed on Kubernetes or on a system with Docker support.
Focus
Harbor serves teams managing artifacts across cloud-native platforms such as Kubernetes and Docker. It provides a way to store, scan, sign, and manage artifacts while supporting access controls and replication across registries.
Background
Harbor is an open-source project and a CNCF Graduated project. Its website invites community members to help build and improve the project through community channels. The available sources do not specify its founding date or funding.
Features
Security and vulnerability analysis
Harbor helps teams assess images for vulnerabilities. It provides image scanning as part of its registry capabilities.
Content signing and validation
Harbor helps teams identify trusted images. It supports signing images and validating signed content.
Policies and role-based access control
Harbor supports controlled access to artifacts. It uses policies and role-based access control, alongside identity integration.
Multi-tenant management
Harbor supports organizing registry use across multiple tenants. Its management features include multi-tenancy.
Registry replication
Harbor supports moving artifacts across registries. It provides replication across many registries, including Harbor.
Extensible API and web UI
Harbor offers API and web interface access for managing registry operations. The metadata lists OCI artifacts and Docker Distribution as compatible interfaces.
Pros and cons
Pros
Combines artifact storage and management with vulnerability scanning, content signing, and validation.
Provides policies, role-based access control, and identity integration for managing access.
Supports replication across multiple registries, including Harbor instances.
Can be installed in Kubernetes environments or on systems with Docker support.
Cons
Harbor does not ship with certificates by default, so HTTPS access requires certificate configuration; the documentation also describes deployment without security over HTTP.
Harbor is self-hosted, so deployment and administration take place on a Kubernetes environment or a Docker-capable system.
FAQs
Harbor FAQ
How does Harbor work?
Harbor stores and manages container images and cloud-native artifacts, scans images for vulnerabilities, and supports image signing and validation. Harbor also applies policies and role-based access control and supports replication across registries.
What integrations does Harbor support?
Harbor's supported integrations are Kubernetes, Docker, Anchore Enterprise, replication across container registries.
How much does Harbor cost?
Harbor is open source; commercial pricing not specified.
What is required to run Harbor?
Harbor is self-hosted on Kubernetes or a Docker-capable system. The listed required skills are Docker or Kubernetes deployment and administration, container registry management, HTTPS configuration, identity integration and role-based access control.
What HTTPS configuration does Harbor require?
Harbor does not ship with certificates by default, so HTTPS access requires certificate configuration.
