Where it runs stays open.
The bottom layer is the machines: Linux hosts running Docker. They can be your own servers, your cloud, or hosted for you, and the seven layers above are the same in each. Where it runs is a decision for your organisation.
What it holds
| Linux | the operating system under everything |
|---|---|
| Docker Engine | runs every service as a container |
| Docker Compose | describes each stack |
| Portainer CE | one console and API for the stacks on each host |
| Named volumes | where the data sits on disk |
What it promises
Three places, one estate
On your own servers, in your cloud, or hosted for you. The platform is the same in all three, so the choice is made on the facts, not up front.
Standard parts
Linux, Docker Engine and Compose. Divan’s estate runs entirely as containers, its database included, so it does not lean on any one cloud’s own services.
Fits the Docker a host already has
The backup runbook covers both the standard Docker install and the Snap package, which keeps its volumes somewhere else. It checks which one a host has first, because the wrong path would back up an empty folder.
Run by us, with you, or handed over
We run it for you or alongside your team, or hand it over with the runbooks.
What people ask
Can it run on servers we already own?
Yes, if they run Linux with Docker, or can. The estate is built there, and the layers above are the same as anywhere else.
Can it share a host with systems we already run?
Yes. Each system is its own stack, and the one proxy in front sends each name to the right one. Hosts we run today carry several stacks side by side.
Are we tied to you?
The estate is standard containers and Compose files, with written runbooks. We can run it, run it alongside your team, or hand it over.