A private registry for your application images
Store container images, Helm charts, and other OCI artifacts in a managed Harbor registry.
Use the Harbor interface or API for projects, tags, metadata, and storage controls.
Container Registry
A private image registry, already connected to your cluster
Asergo gives your team a private place to push and pull application images, running on Asergo's EU infrastructure. You do not need to choose a registry provider, run Harbor yourself, wire it into Kubernetes, configure robot accounts, manage storage limits, or connect vulnerability scanning before your team can deploy.
From €0.20 / GiB / month
Minimum €20 / month
Harbor Registry
API Interface
Storage Management
Robot Accounts
Security Scanning
Kubernetes Integration
What you get
A private image source from day one
Kubernetes pull access already prepared
Each registry comes with a Kubernetes pull robot account ready for cluster integration.
CI/CD can push with robot account credentials, and clusters can pull without shared personal credentials.
Vulnerability scanning on pushed images
Pushed images are scanned for known CVEs so your team can review severity and decide what needs fixing before deployment.
EU-operated registry infrastructure
The registry runs on Asergo infrastructure in Europe, alongside the rest of your Asergo platform.
Included traffic inside Asergo
Traffic between the registry and Asergo endpoints is included, so registry-to-cluster pulls do not create a separate egress cost line.
What work this removes
A private image source without a separate registry project
A private registry only helps once image storage, access, pull credentials, scanning, and environment flow are connected. Asergo handles that registry layer before it becomes a separate infrastructure project for your team.
That means your team is not blocked by:
- Choosing a registry service or operating Harbor
- Configuring image storage and quotas
- Connecting authentication and project access
- Creating credentials for Kubernetes and CI/CD
- Managing pull secrets
- Connecting vulnerability scanning
- Defining image promotion between environments
- Maintaining registry availability and integration
Asergo operates the registry layer
Registry service, Harbor setup, storage integration, platform authentication, and Kubernetes pull access.
Your team owns the images
Image content, build pipeline, tagging, project structure, access decisions, and vulnerability fixes.
How it works
A registry flow that matches the deployment flow
1
Create your registry project
Create projects for applications, teams, environments, or clients. Use a structure that fits your deployment flow, such as separate projects for development, staging, and production.
2
Push images from your build pipeline
Your CI/CD system pushes images into the registry using a robot account. Accounts can be scoped, disabled, and separated by purpose.
3
Pull images into Kubernetes
Your Asergo cluster can pull from the registry using the prepared Kubernetes robot account, removing the usual setup work around image pull credentials and private registry access.
4
Review images and scan findings
Inspect tags, artifacts, storage usage, robot accounts, and CVE findings in Harbor or through the API.
Container Registry
Start deployments with a private image source already in place.
Talk through how image storage, cluster pull access, and scanning fit into your Asergo setup.