Your own private
container registry
Push private images from CI, pull them onto your servers, and never hand your containers to a third party. Registries, repositories, robot accounts and retention policies — in the same panel that runs your infrastructure.
prod-registry
staging-registry
0
Third parties in the path
3
Access levels (read/write/admin)
1
Click to push from CI
Auto
Retention rules
Everything a registry needs
Create registries, organise repositories within them, and browse tags and image history — all from the panel. Each registry is isolated and addressable by repository and tag, just like any Docker registry, but it lives on your infrastructure.
Private Registries
Multiple isolated registries, each independently managed
Repositories
Organise repositories within a registry by name
Tags & History
Browse tags and image history for any repository
Robot Accounts
Non-human identities scoped to specific repositories for CI
Access Tokens
Short-lived tokens with read, write, or admin permissions
Permissions
Per-repository read, write, and admin for users, teams, and robots
Robot accounts for CI pipelines
Robot accounts are non-human identities scoped to specific repositories, so a pipeline never carries a personal credential. When someone leaves the team, their access is revoked — the robot account keeps running.
- Per-repository scope — a pipeline can only touch what it needs
- Revoke a robot account without disrupting people or other pipelines
- Separate from user accounts — no shared personal credentials in CI
ci-pipeline-prod
prod-registry/frontend
ci-pipeline-api
prod-registry/api-server
staging-deploy
staging-registry/*
Scoped to repositories — no personal credentials in CI
Scoped access tokens
Short-lived tokens with defined permissions, issued and revoked from the panel. Use them for temporary access, service-to-service authentication, or time-boxed CI runs.
- Short-lived with configurable expiry
- Defined permissions — read, write, or admin
- Issued and revoked from the panel, no CLI required
deploy-token
Expires in 2h 14m
read-only-audit
Expires in 5d 3h
admin-temp
Expires in 18m
Short-lived, scoped, revocable from the panel
Storage quotas and usage tracking
Quotas per registry with live usage tracking and history, so storage growth is visible before it becomes a bill. The panel shows how much space each repository consumes and warns you as you approach the limit.
- Configurable storage quota per registry
- Live usage tracking with historical trends
- Per-repository breakdown of storage consumption
- Warnings before the quota is reached
Retention and auto-delete rules
Rules that prune old tags automatically; without them a registry grows forever. The trade-off is honest: aggressive retention can delete an image you still need to roll back to. Configure retention to match your rollback window, not to keep storage tidy at all costs.
- Auto-delete rules that prune old tags on a schedule
- Configurable retention count or age per repository
- Honest trade-off — aggressive retention can remove a rollback image
- Set retention to match your rollback window, not just storage limits
frontend
AutoKeep last 10 tags
Daily at 02:00
api-server
AutoKeep tags < 30 days
Weekly
worker
AutoKeep last 5 tags
Daily at 03:00
Set retention to match your rollback window — aggressive rules can delete an image you still need.
Shared registries across your team
Shared registries across a team with member management and an activity log. See who pushed what, when a robot account was created or revoked, and which permissions changed.
Shared registries across a team or organisation
Member management with role assignment
Activity log tracking pushes, pulls, permission changes, and robot account lifecycle
frontend:v2.4.1
by ci-pipeline-prod
api-server:v1.8.0
by prod-server-01
staging-deploy
by admin@team
worker repo
by admin@team
old-ci-bot
by admin@team
Everything around your registry
Pair your container registry with the tools that deploy, manage, and protect your infrastructure.
Yes. SharkCluster runs a private container registry on your own server. You push images from your CI pipeline, pull them onto your servers, and your images never pass through a third-party service.
Robot accounts are non-human identities scoped to specific repositories — a pipeline uses them instead of a personal credential. Access tokens are short-lived credentials issued to a human or service for authentication. Robot accounts survive person-level changes; tokens expire.
Each registry has a configurable storage quota with live usage tracking. When you approach the limit, the panel warns you before it becomes a problem. You can raise the quota, delete old tags, or set up auto-delete retention rules to reclaim space automatically.
Ready to take control
of your hosting?
Deploy servers, run self-hosted business apps, and keep your data on your own VPS — with a dedicated DevOps manager by your side.