Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience real numbers from our own analytics — open to see them
–Visitors
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · counted by iTechGuides's own first-party analytics, bots removed, every figure rounded down · how we count

Cloudflare Serverless Registry review

Free#54 of 61 in Container Registries

A lightweight, self-operated registry for teams deploying on Workers and R2.

6.0/10Editor score
Cloudflare Serverless Registry6.0 Visit Cloudflare

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Cloudflare Serverless Registry is an open-source container registry implementation for developers and teams that want to run a registry on Cloudflare infrastructure. It uses Cloudflare Workers with R2 storage and supports Docker image push and pull workflows. The project is licensed under Apache 2.0, while deployments run through the user's own Cloudflare account. That makes it a focused option for teams comfortable operating their own registry rather than selecting a separately hosted service.

Deployment is configured and operated with Wrangler, so the setup model centers on Cloudflare infrastructure and user-managed configuration. The registry integrates with Docker, Docker Hub, and Google Container Registry. Authentication options include username/password and public-key JWT authentication. Pull fallback from another registry adds flexibility for images that are not stored locally, with Basic and Bearer authentication supported for registry fallback. This combination suits teams already working with Cloudflare Workers, R2, and Docker-based workflows.

Its scope is narrower than a full enterprise registry platform. Cloudflare Serverless Registry does not provide verified scanning, governance policies, or retention features, and it does not offer broad OCI artifact support. Teams seeking a small, open-source registry implementation with Cloudflare deployment should consider it. Teams that need built-in image security analysis, lifecycle controls, governance, or wider artifact coverage should choose a platform centered on those capabilities instead.

Cloudflare Serverless Registry pros and cons

  • Where it wins
    • Runs on Cloudflare Workers with R2-backed storage
    • Supports Docker image push and pull workflows
    • Offers username/password and public-key JWT authentication
  • Where it doesn't
    • Requires deployment and operation through Wrangler
    • Lacks verified image scanning and governance policies
    • Does not provide OCI artifact breadth or retention features

Cloudflare Serverless Registry fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. We may earn a commission when you click some links. How we rank.

Last updated · How we research and update