Cloudfleet’s mission is to make Kubernetes and cloud-native computing available to everyone, at the lowest possible cost. We keep improving the platform under the hood, and when those improvements make Cloudfleet cheaper to run, we pass the savings on to our customers.
Today we are announcing the latest result of that work. Since November 16, 2026, Cloudfleet Container Registry (CFCR) has been rolling out a new storage engine that stores your images far more efficiently. Your metered CFCR storage goes down automatically, by up to 50% in some cases. Your images, tags and pipelines stay exactly as they are. You pay less, and you don’t have to do anything.
The same work makes the registry faster too. Pushes and pulls get quicker responses, so builds finish sooner and new nodes start their workloads faster.
What is Cloudfleet Container Registry?
CFCR is a fully managed, private, OCI-compliant container registry built into every Cloudfleet organization. Store Docker images, multi-architecture images and Helm charts in one place, with no infrastructure to provision, scale or patch.
- No image pull secrets, ever. Cloudfleet clusters authenticate to CFCR automatically with short-lived OIDC tokens. There are no registry credentials to create, rotate or leak.
- One access model. CFCR uses the same roles as the rest of Cloudfleet. Administrators push, users pull, and API tokens cover your CI/CD pipelines.
- Isolated by design. Every organization gets its own registry namespace, so your images are never reachable from another organization.
Built for hybrid and multi-cloud
Most registries belong to one cloud. Your Cloudfleet cluster doesn’t. A single cluster can run nodes on AWS, Google Cloud, Hetzner and your own data center at the same time, and CFCR serves all of them the same way.
- Every node pulls the same way. A node in your server room authenticates just like a node on AWS. You don’t need separate credentials per cloud or per site.
- Mixed architectures just work. Multi-architecture images let ARM64 and AMD64 nodes in the same Fleet pull the right image from one tag.
- Close to your workloads. Choose the
europe,northamericaorapacregion. Theeuroperegion runs entirely on EU-based infrastructure for teams with data residency requirements. - One less vendor. Your cluster, network and registry come from one provider, so you’re no longer stitching a third-party registry into a multi-cloud setup.
Get started
The lower storage costs reach every CFCR customer automatically as the rollout completes. If you aren’t using CFCR yet, the getting started guide takes you from your first docker push to a running Pod in a few minutes.
