Zot OCI Registry

AWS Storage
Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Overview

Production-ready OCI container registry - secure, serving over HTTPS in minutes with a built-in web UI. Backed by 24/7 cloudimg support.

Why the cloudimg image

This image arrives installed, configured and hardened, so there is no manual setup before you can use it. It is built on a patched base, runs with credentials generated uniquely for your instance on first boot, and passes an automated health check before every release. Every deployment is backed by 24/7 support from cloudimg engineers.

Key features

  • Secure and serving in minutes with zero manual hardening - every instance generates its own unique admin password and TLS certificate on first boot, denies anonymous access by default, and exposes only HTTPS and SSH. Unlike multi-container registry stacks that require separate hardening steps, this image is locked down from the moment it launches, with credentials stored in a root-only file and the registry port never exposed to the network.
  • Single-binary, vendor-neutral architecture with no cloud lock-in - one Go binary plus nginx, no Redis, no external database, no Docker Compose. Works with docker, podman, skopeo, oras, and any OCI-compliant client. Registry data lives on a dedicated, independently resizable disk separate from the OS, so you can scale storage without reprovisioning the instance.
  • Built-in web UI and OCI artifact support backed by 24/7 cloudimg engineers - browse repositories, inspect tags, and review per-image vulnerabilities directly in your browser. Store container images alongside Helm charts, SBOMs, and signatures. Content deduplication and garbage collection keep storage efficient, with 24/7 email and live chat support for deployment, certificate replacement, sync configuration, and upgrade planning.

See it running

Real screenshots taken while testing this image against its deployment guide.

Zot OCI Registry screenshot 1 Zot OCI Registry screenshot 2 Zot OCI Registry screenshot 3 Zot OCI Registry screenshot 4

Description

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

## Private OCI Container Registry - Secure and Serving in Minutes

Zot is a production-ready, vendor-neutral, OCI-native container image registry for storing and distributing container images and OCI artifacts. Unlike multi-container registry stacks that require manual hardening, this image delivers a single-binary registry fully installed and locked down behind an nginx HTTPS reverse proxy - ready to receive your first image push within minutes of launch.

The current release available is Zot 2.1.17.

## Why Zot

  • Single-binary simplicity - no Docker Compose stacks, no Redis, no external databases. One Go binary plus nginx, managed by systemd.
  • Vendor-neutral and OCI-native - no proprietary APIs or cloud lock-in. Works with docker, podman, skopeo, oras, and any OCI-compliant client.
  • Secure by default, not by manual effort - every instance generates its own unique admin password and TLS certificate on first boot. Anonymous access is denied out of the box.
  • Built-in web UI - browse repositories, inspect tags and manifests, and review per-image vulnerability information without installing additional tools.
  • Dedicated data disk architecture - registry configuration, OCI blob storage, and the authentication database live on a separately resizable disk, independent of the OS volume.

## Application Stack

Zot binds to the loopback interface and is fronted by nginx, which terminates TLS on the standard HTTPS port and streams image layers of any size. systemd starts both services on boot and restarts them on failure. Only the HTTPS proxy port and SSH are reachable from the network - the registry port is never exposed directly.

## Secure By Default

On first boot, a one-shot service generates a fresh admin password unique to that instance, mints a self-signed TLS certificate, and records the credentials in a file only the root user can read. No shared or default credentials and no shared TLS key ship in the image. Anonymous pull and push are denied, so nothing is readable or writable without authentication.

## Push, Pull and Browse

Log in with docker, podman, skopeo, or oras and push and pull images and OCI artifacts over HTTPS. Content deduplication and garbage collection keep storage compact. Open the built-in web UI in a browser to browse repositories, inspect tags and manifests, and review per-image vulnerability information from the bundled search extension.

## Key Capabilities

  • Content deduplication and garbage collection
  • Image signature and SBOM support
  • Registry-to-registry sync and mirroring
  • Built-in web UI with vulnerability scanning
  • Health endpoint for load-balancer and uptime checks

## Use Cases

  • Private self-hosted registry - for teams and CI pipelines that push and pull images over HTTPS without relying on external services.
  • OCI artifact storage - store Helm charts, SBOMs, signatures, and other OCI-native content alongside your container images.
  • Air-gapped or edge distribution - use registry-to-registry sync and mirroring for environments without internet access.

## Getting Started

Launch the image, retrieve the generated admin password from the instance, log in, and start pushing images. The built-in health endpoint answers on the reverse proxy for load-balancer integration. To ask pre-purchase questions or get help planning your deployment, contact cloudimg support.

## cloudimg Support

24/7 technical support by email and live chat. Our engineers help with deployment, replacing the self-signed certificate with a CA-signed one, configuring access control and additional users, setting up registry sync and mirroring, and planning storage and upgrades.

All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Related technologies

oci registrycontainer registrydocker registryprivate registryoci artifactscontainer imagesimage registryhelm chart registryregistry syncsbom storageself-hosted registrynginx reverse proxyair-gapped registrydevops