Features/Template catalogue
Deployments

Template catalogue

One-click deploy of more than a hundred preconfigured applications: pick it, name it, choose a server, and it comes up with sensible defaults and generated passwords. Every one of them is deployed and checked before it reaches the catalogue.

How it works

Tested, not just listed

Every entry is deployed and checked before it reaches the catalogue, rather than written once and left there. Long catalogues elsewhere are full of things that no longer come up, so for now the count stays around a hundred: we would rather have a hundred that work than a thousand that might.

It is yours afterwards

Nothing about the template stays attached to the app. Edit the Compose before it runs or after, change variables, add domains. Deploying the same template twice into one environment renames what would clash instead of failing.

Anyone can add one

The catalogue takes contributions, and so does the rest of Deplo. A template is a Compose file and a small manifest, which is the shortest way in.

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

Deplo has a clean, intuitive UI that helps you understand what’s happening, without wasting time.

AI ready

Your coding agent can deploy, read logs and roll back for you, with the same access a teammate gets.

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.

Bring your own server

Your hardware, your network, your data. Open source, no lock-in, and no pricing page to keep an eye on.

Ten minutes from now
it's deployed.

Install takes one command on a server you already pay for. What you do with the money you get back is your business.