ibee

Private registry for
container images

Store Docker and OCI images in a registry only your team can reach. Pick a storage plan, issue scoped tokens for your pipelines, and review vulnerabilities and SBOMs before you ship.

  • OCI-compatible
  • Vulnerability scanning
  • SBOM views
Container images pushed from a Docker build into a private registry, tagged and scanned, then pulled into a Kubernetes cluster
Works withDockerKubernetesOCI artifactsGitHub ActionsGitLab CIJenkins
Inside a registry

See how it fits together

~/acme-api$ 4 layers pusheddigest sha256:9f3c…a71eregistry.ibee.aiprivate · OCI-compatibleapp codedependenciesruntimebase imageapi:1.4.2 scanned ✓Managed Kubernetesnode-14 vCPUapipullingapipullingnode-24 vCPUapipullingapipullingnode-34 vCPUapipullingapipulling
  1. 1Push
  2. 2Scan
  3. 3Pull
  4. 4Run

Push an image

simulated

$IBEE_REGISTRY stands in for your registry endpoint from the dashboard.

Why container registry

A registry your pipelines and clusters can rely on

Private and public registries

Credentials required, or open for anonymous pulls.

OCI-compatible storage

Docker and OCI images for production workloads.

Selectable storage plans

250 GB, 500 GB or 1 TB — pick what you need.

Tokens for automation

Scoped credentials for CI/CD and deployments.

Security scanning

Findings by severity, with scan status per artifact.

SBOM visibility

See what's inside an artifact, where available.

Pricing

Simple registry storage pricing

Choose a fixed monthly storage plan. Outbound registry bandwidth is billed separately per GB, so storage and delivery costs stay clear.

Container Registry 250 GB

Entry
₹699/month

Smaller teams, internal images, early production.

  • 250 GB registry storage
  • Private or public visibility
  • OCI-compatible repositories
  • Access token support
  • Security and SBOM views

Container Registry 500 GB

Recommended
₹1,199/month

Active teams with multiple images, tags and repos.

  • 500 GB registry storage
  • Private or public registries
  • Repository and artifact browsing
  • Vulnerability scanning
  • Metrics and bandwidth tracking

Container Registry 1 TB

Production
₹1,999/month

Production teams, frequent builds, long image history.

  • 1 TB registry storage
  • Built for production teams
  • Security scan visibility
  • SBOM support
  • Upgrade from lower plans

Outbound bandwidth

  • Private Registry Egress
    Private registry image pulls.
    ₹3 /GB
  • Public Registry Egress
    Public registry image pulls.
    ₹3 /GB
  • Hardened Images Egress
    Hardened image pulls.
    ₹3 /GB

Estimate your monthly cost

400 GB
Container Registry 500 GB
₹1,199 /mo
Egress at ₹3/GB
₹1,200
Estimated total₹2,399

Estimate only, using the listed plan and egress rates. Taxes and other services are not included.

Storage capacity uses decimal GB. Registry plan downgrades are not supported after creation — you can upgrade to a larger plan when needed. Prices exclude applicable taxes.

Use cases

Where teams put it to work

Private application images

Backend, frontend and worker images, kept private.

CI/CD pipelines

Push from GitHub Actions, GitLab CI, Jenkins or runners.

podpodpodpodpodpod

Kubernetes deployments

Pull into clusters with registry credentials.

pullpullpull

Public image distribution

Public registries for anonymous pulls.

Hardened base images

Ship hardened bases with predictable egress pricing.

CriticalHighMediumLow

Security review

Findings, SBOMs and artifact metadata in one place.

Security & visibility

Vulnerabilities, SBOMs, and usage in one view

Track scan results by severity, inspect artifact contents, and watch storage and outbound bandwidth as your images grow.

acme-prod / artifacts
500 GB plan
Repositories
app/api:1.4.2 scanned 4m ago
Storage used241 / 500 GB · 48%
Repositories
3
Egress (est.)
400 GB
Sample data — your workspace reports live scan results and usage.

Private by default

Credentials required for push and pull.

Token-based access

Scoped tokens for automation and pipelines.

Vulnerability visibility

Counts by severity for scanned artifacts.

SBOM support

Component details where available.

Usage metrics

Storage, quota, utilization and bandwidth.

Plan upgrades

Move to a larger quota as images grow.

Questions, answered

IBEE Container Registry is an OCI-compatible registry for storing and distributing Docker and container images from your IBEE Cloud workspace.
Yes. Private registries require credentials and are suitable for internal application images, production workloads, and CI/CD pipelines.
Yes. Public registries allow anonymous pulls and are useful for public images or shared artifacts.
Available plans include 250 GB, 500 GB, and 1 TB registry storage.
Yes. You can upgrade to a larger quota. Registry plan downgrades are not supported.
Container registry egress is billed at ₹3 per GB for private registry, public registry, and hardened image pulls.
Yes. The security tab shows vulnerability findings by severity when scanned artifacts have available scan results.
Yes. The registry includes an SBOM view for supported artifacts.
Create a registry, generate an access token, authenticate with Docker, tag your image with the registry endpoint, and push it.
Yes. You can use registry credentials with Kubernetes imagePullSecrets or deployment workflows that pull from your registry endpoint.

Have more questions?

Contact Our Technical Team→

Create your private
container registry

Store Docker and OCI images, secure access with tokens, track usage, and distribute to your production workloads.