Features/Container registries
Deployments

Container registries

Connect a private registry once per team. Every image pull the team makes uses it: a Docker image app, every image in a Compose stack, and the base image a Dockerfile starts from.

How it works

Why it matters

Nothing is configured per app and the token is write-only. GitHub Container Registry, Docker Hub, GitLab or any registry you run yourself.

The good parts, already switched on.

The boring operational parts are already handled. You just have to pick what to deploy.

The good parts, already switched on.

The boring operational parts are already handled. You just have to pick what to deploy.

Simple by design

Nothing new to learn. The dashboard uses the words you already know, and shows what's happening at a glance.

AI ready

Ask your coding agent to deploy, read the logs or roll back. It gets the same access a teammate does.

Who did that?

Deplo knows. Every action has a name and a time on it, and you decide who's allowed to do what in the first place.

Your host, your price

Get a server from one of our hosting partners or use one you already have. Open source, no lock-in, and no bill that grows with your team.

Ten minutes from now,
it's live.

Answer three questions and pick a host, or install Deplo on a server you already have. It's free, and leaving is as easy as arriving. What you do with the money you save is your business.

Container registries - Deplo