What is the DanubeData Container Registry?

A private OCI-compatible image registry at cr.danubedata.ro. Push images from Docker or your build pipeline, then pull them from Rapids, a VPS, Kubernetes or your laptop. Each team has its own repository namespace.

How does authentication work?

Create a pull-only or push-and-pull access key in your team dashboard. Its username and one-time secret token work with docker login. The registry exchanges those credentials for a short-lived signed token. You can revoke the access key when it is no longer needed.

Can Rapids pull my private images?

Yes. An internal pull credential is provisioned when your team creates its first Rapid. Select DanubeData Container Registry as the credential for a Docker-image deployment to pull from your team namespace.

Where are images stored?

Image blobs and manifests are stored in our Ceph-backed object storage in Falkenstein, Germany.

Which clients can I use?

The registry uses CNCF Distribution and works with OCI-compatible clients, including Docker, Podman, Buildah and Skopeo. Kubernetes workloads can pull images with a standard image-pull secret.

How does image retention work?

Set a team default or a repository override to keep the newest distinct images. Retention counts image digests, not tag names, and keeps every tag pointing to a retained image. Images used by Rapids deployments are protected from automatic pruning. You can also delete images from the console or API; deleting one removes every tag on that digest.

How is the registry priced?

Plans set the storage and repository limits for your team. Current plan prices and limits are listed above. For different limits, contact us about a custom plan.

Private container images, hosted next to your apps.

Push to cr.danubedata.ro. Pull from Rapids, your VPS, Kubernetes or your laptop. Your existing image workflow, with private team repositories hosted in Germany.

European-owned
EU hosted
German data centers

Try the Docker commands or manage your registry with the danube CLI.

Replace the example username with your access key username. Enter the one-time token at the prompt.

read -r -s REGISTRY_TOKEN
printf '%s' "$REGISTRY_TOKEN" | docker login cr.danubedata.ro \
  --username dd-acme-ci-xxxxxx --password-stdin
unset REGISTRY_TOKEN

Replace acme with your team namespace and api:v1 with your local image.

docker tag api:v1 cr.danubedata.ro/acme/api:v1
docker push cr.danubedata.ro/acme/api:v1

docker pull cr.danubedata.ro/acme/api:v1

What customers say

“As a developer and cloud enthusiast, I’ve tried a lot of infrastructure platforms — but DanubeData genuinely stands out as one of the most intuitive, modern, and reliable cloud services I’ve used. From signup to deployment, everything feels thoughtfully designed and developer-centric. Deploying a VPS, cache, or database instance takes under a minute — and that’s not an exaggeration! Their intuitive dashboard and instant provisioning make launching new services effortless, even if you’re just getting started with cloud infrastructure”

Keoma WrightCEO/Founder at OpenWeb.co.za

“I’m running my new project’s backend on DanubeData and the experience has been smooth from day one—deployment is fast, the dashboard feels genuinely developer-friendly, and everything has been stable with no issues so far. Any time I had a question or hit a small blocker, the support was excellent: quick to respond, clear in explanations, and focused on getting me unblocked rather than sending me in circles. If you want EU-based infrastructure without the usual DevOps friction, DanubeData delivers.”

Cristian TorzsaCEO at InnovaSoftware SRL

“ruby/Sinatra invoicing application on a Docker container. Danube data was an obvious choice given its incredibly user friendly dashboard and automatic deployment directly from my GitHub repository via webhook. I've used many other platforms (Google, AWS, Azure), but Danube is the clear winner in terms of ease to configure, clear and honest pricing not to mention the excellent response time. Everything works perfectly so I hardly ever have to pull up the dashboard since I moved to Danube Data.”

Bo PereiraParis-Brest srl

Control who pushes, pulls and keeps your images.

Access, retention and deployment credentials stay with your team.

Scoped access keys
Pull-only keys for hosts that run images; push and pull keys for builders. Create separate keys for your environments and revoke them from the dashboard.
Team namespaces
Private repositories live under your team namespace. The token service limits each key to the images and actions it can access.
Automatic Rapids credentials
Select your internal registry credential for a Docker-image Rapid. Your team’s pull credential is provisioned with its first Rapid.
OCI-compatible clients
Use Docker, Podman, Buildah or Skopeo with CNCF Distribution. Kubernetes pulls use the usual image-pull secret.
Image retention
Keep the newest distinct images with a team default or repository override. Automatic pruning protects images used by Rapids deployments.
Registry events
Records push, pull and delete activity with the repository, image reference and actor username.

From a local image to a private repository.

Create an access key
Choose pull-only or push-and-pull access. Save the secret token when it is shown, because it is shown once.
Log in to the registry
Use your key username and token with docker login cr.danubedata.ro on your laptop or build runner.
Tag and push your image
Prefix the image with cr.danubedata.ro and your team namespace. The registry stores its content in Germany.
Run it where you need it
Pull the image from a VPS or Kubernetes cluster, or select your registry credential in Rapids.

More image workflows

Private build artifactsPush pre-release images from your build pipeline to share them with your team.
Base image mirrorsCopy the upstream images your builds use into your own namespace.
Internal toolsDistribute your team’s dashboards, developer tools and demos as private images.

Choose your team’s registry limits.

Storage and repository allowances for your team. Paid plans are billed hourly.

Starter

Free

Storage: 500 MB
Repositories: 1

Create an account

Basic

€3.99/ month

Storage: 5 GB
Repositories: 5

Create an account

Professional

€14.99/ month

Storage: 100 GB
Repositories: Unlimited

Create an account

View pricing. Need different limits? Talk to us about a custom plan.

Registry questions.

Authentication, image cleanup and running private images.

A private OCI-compatible image registry at cr.danubedata.ro. Push images from Docker or your build pipeline, then pull them from Rapids, a VPS, Kubernetes or your laptop. Each team has its own repository namespace.
Link to this answer
Create a pull-only or push-and-pull access key in your team dashboard. Its username and one-time secret token work with docker login. The registry exchanges those credentials for a short-lived signed token. You can revoke the access key when it is no longer needed.
Link to this answer
Yes. An internal pull credential is provisioned when your team creates its first Rapid. Select DanubeData Container Registry as the credential for a Docker-image deployment to pull from your team namespace.
Link to this answer
Image blobs and manifests are stored in our Ceph-backed object storage in Falkenstein, Germany.
Link to this answer
The registry uses CNCF Distribution and works with OCI-compatible clients, including Docker, Podman, Buildah and Skopeo. Kubernetes workloads can pull images with a standard image-pull secret.
Link to this answer
Set a team default or a repository override to keep the newest distinct images. Retention counts image digests, not tag names, and keeps every tag pointing to a retained image. Images used by Rapids deployments are protected from automatic pruning. You can also delete images from the console or API; deleting one removes every tag on that digest.
Link to this answer
Plans set the storage and repository limits for your team. Current plan prices and limits are listed above. For different limits, contact us about a custom plan.
Link to this answer

Explore more solutions

Your images, ready for your next deployment.

Keep private images in your team namespace. Push with your existing tools and pull wherever you run them.

Push your first image Talk to us

Start free

Compute

Storage

Managed apps

Caching

Databases

Messaging

Monitoring

DanubeData CLI

Automation & Agents

Tools

Developer docs

Learn

Support

Private container images, hosted next to your apps.

What customers say

Control who pushes, pulls and keeps your images.

Scoped access keys

Team namespaces

Automatic Rapids credentials

OCI-compatible clients

Image retention

Registry events

From a local image to a private repository.

Create an access key

Log in to the registry

Tag and push your image

Run it where you need it

Choose your team’s registry limits.

Starter

Basic

Professional

Registry questions.

Explore more solutions

Your images, ready for your next deployment.