Pull once from CloudRepo. Then from your own disk.

CloudRepo On-prem Edge is the edge of CloudRepo, extended to your data center: one small cache on your own network, so your builds pull from your own disk. It's not a self-hosted CloudRepo. CloudRepo still runs your repositories and checks every pull, so the Edge needs a connection to it.

Early access is open. We plan to ship it in early 2027.

Register for early access Included with any paid CloudRepo account.

First pull docker pull

app:4.2, an example image

  1. CloudRepo checks your token allowed
  2. Fetched from CloudRepo 1.4 GB
  3. Matches CloudRepo's SHA-256 yes
  4. Kept on your disk yes

Over your internet link1.4 GB

Next pull any machine

the same example image, now on your disk

  1. CloudRepo checks your token allowed
  2. Matches CloudRepo's SHA-256 yes
  3. Served from your disk 1.4 GB
  4. Fetched from CloudRepo 0 GB

Over your internet link0 GBplus one small check

Asked CloudRepo first. Then 0 GB over your link. the next pull, from any machine on your network

An example image, not a customer's. It shows how the Edge is designed to work.

A pull-through cache that asks CloudRepo first

Builds that run on site pull the same images and packages over and over, and every pull crosses your internet link. When a hundred machines start one new image, each one downloads it. And if you run Nexus or Artifactory mostly as a cache, you also patch it, upgrade it and back it up.

Your builds keep one name for CloudRepo. Inside your network, your DNS points that name at the Edge. When the Edge keeps a file on its disk, it checks the whole file against the SHA-256 CloudRepo recorded at upload before any build gets it. Files it passes straight through come directly from CloudRepo.

A registry mirror for Docker, Maven, npm and Python

What the Edge is being built to do, and where each part stands. Nothing here is switched on for customers yet.

What the Edge is being built to do, and where each part stands
What it doesWhere it stands
Pulls Docker images and Maven, npm and Python packages for your builds, after CloudRepo checks each one with the build's own token. Built, not on yet
Keeps each file on your disk, checked against the SHA-256 CloudRepo recorded, and serves the next pull from there. Being built
Fetches once when many machines ask for the same new file at the same time. Being built
Pushes: a Docker image you push goes to CloudRepo first, then stays on your disk for the next pull. Maven, npm and Python uploads go straight to CloudRepo. Being built
Runs as one container on your own Linux server or virtual machine, with a disk and no database. Built, not on yet
Runs on Kubernetes. Planned
Keeps builds working when CloudRepo can't be reached. Not today
Price: included with any paid CloudRepo account. Decided
Transfer: pulls served from your disk won't count toward your transfer. Being built

What you'll need: a paid CloudRepo account, builds that sign in with repository tokens, every member signing in with a second factor or single sign-on, and a DNS name your network can point at the Edge.

Register for early access

Tell us where your builds run and what you use today. Every request helps us decide what to build next.

Do you offer on-prem?

Not as a full install. CloudRepo is a managed service, and CloudRepo On-prem Edge is the part that runs on your network, as a cache. If you need all of CloudRepo on your own servers, or builds that keep working offline, tell us. It helps us decide what to build next.

Rather talk first? Book 15 minutes with Chris, our founder

Email Chris at chris@cloudrepo.io, or book 15 minutes.