Harbor
Container and OCI artifact registry for managing software images within customer-operated infrastructure.
5 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Install Harbor on a Docker-capable host or use the documented high-availability Helm deployment on Kubernetes.
Runs in
Documented customer environment
Customer-operated registry, API/UI and supporting database/storage services
- Railway: Customer platform workspace
- Railway
Servers / containers
Operated by
Your team
Customer manages artifact storage, database, TLS, identity, scanner configuration, replication, backups and upgrades.
Deployment boundaries by provider
- Railway: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Harbor community deployment on Railway ↗ · Source checked 2026-11-12
Source for the Harbor Railway core wrapper ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Install Harbor on a Docker-capable host or use the documented high-availability Helm deployment on Kubernetes. |
|---|---|
| Infrastructure | Servers / containers Customer-operated registry, API/UI and supporting database/storage services. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support. |
| Licensing model | Open Source / Open Core Apache License 2.0 for upstream Harbor. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms. |
| License | Apache License 2.0 for upstream Harbor. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
Harbor 2.15 documents OIDC browser login and group claims. Choose the authentication mode before adding ordinary local users; Docker/Helm clients use a CLI secret rather than interactive OIDC redirects.
Harbor 2.15 OIDC UI and separate registry CLI authentication · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
Harbor documents both a Docker-host installer and Kubernetes Helm deployment. Configure HTTPS, image storage and the supported dependency versions; HA has separate prerequisites.
Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The Docker-host prerequisites list 2 CPUs, 4 GB RAM and 40 GB disk minimum, with 4 CPUs, 8 GB and 160 GB recommended. Image volume, scanning, retention and HA affect actual sizing.
Harbor deployment prerequisites; not per-node HA sizing or a cost estimate · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate.
Upstream core licence; commercial features, support and hosting priced separately · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The publisher-designated GitHub release checked was v2.15.5, published 2026-11-12. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package.
Upstream goharbor/harbor release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
Scanning, signing and replication depend on the components and endpoints configured. Sending images to a remote registry or scanner changes data boundaries. Harbor v2.15.5 bounds audit and manifest request bodies, enforces actual decompression byte limits, redacts sensitive pagination and upload locations in rejection errors, and updates dependencies for high-severity CVEs. Operators on the 2.15 line should upgrade to v2.15.5 or a later supported patch.
Community & maintenance
Harbor is a CNCF Graduated project with documented foundation oversight and continuing upstream release maintenance.
Category fit
- DevOps
- Private registry for container and OCI artifacts with project permissions, artifact policies, replication and optional security integrations.
Compare within DevOps
- Argo CDGitOps continuous delivery controller and interface for deploying and reconciling applications in Kubernetes clusters.
- AWS
- Azure DevOps ServerSource control, CI/CD, work tracking, testing and package management installed on Azure virtual machines you operate.
- Azure
- Bitbucket Data CenterCommercial self-managed Git collaboration and code-review platform for eligible existing Atlassian customers, with an announced Hybrid License transition.
- AWS
- Azure
- Google Cloud
- CircleCI ServerCommercial self-hosted CI/CD platform installed in a customer-operated Amazon EKS or Google GKE cluster.
- AWS
- Google Cloud
- CloudBees CI on Modern Cloud PlatformsEnterprise continuous-integration platform installed with Helm in a Kubernetes cluster you operate.
- AWS
- Azure
- Google Cloud
- GitHub Enterprise ServerCustomer-operated GitHub software-development platform deployed as a licensed virtual appliance.
- AWS
- Azure
- Google Cloud
- GitLab Self-ManagedSource control and CI/CD on infrastructure you operate.
- AWS
- Azure
- Google Cloud
- Oracle Cloud
- Alibaba Cloud
- HashiCorp Consul EnterpriseCommercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.
- AWS
- Azure
- Google Cloud
Showing 8 of 27 other listings in DevOps. These products address related workflows; read their category-fit notes before comparing scope. See all of DevOps →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Official installation and runtime ↗goharbor.io
- Upstream project and capabilities ↗github.com
- Current upstream license ↗github.com
- Registry functionality ↗goharbor.io
- Harbor v2.15.5 security hardening and dependency updates ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Harbor community deployment on Railway ↗ · Railway
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The community recipe provisions Harbor core, portal, job service, registry, registry control, scanner and proxy roles with PostgreSQL, Redis and object storage. Its component wrappers derive from upstream Harbor images. Review consistent image versions, TLS, authentication, registry storage and scanning/update operations; community packaging does not imply CNCF or project support.
- Source for the Harbor Railway core wrapper ↗ · Railway
Community template · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The inspected core wrapper derives from the upstream goharbor/harbor-core image (v2.15.2). Review the corresponding versions and configuration of every Harbor component before deploying the full community template.
- Harbor community deployment on Railway ↗ · Railway
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- CNCF graduation and project governance ↗www.cncf.io
- Current release history ↗github.com