Keep what already works
Discover running containers and import them as managed apps. Their data volumes are preserved.
APP SERVERS
Your server.Your control.
Bring your VPS or get a new VM. Deploy apps, read logs and monitor resources from DADA Cloud — while your code runs on your machine.
Start in the console. Choose an existing server or a new VM there.
HOW IT FITS TOGETHER
Deploy your way
Use Git or your existing docker-compose.yml. No new configuration format to learn.
One view of every server
Deployment, logs and metrics for your own machines and client VMs, in the same console.
TWO WAYS TO START
Already have a server?
Connect your own
Keep the machine at your current provider. We install the agent over SSH and show your existing containers. You decide which ones to manage.
Connection guideStart with a new VM
Choose a configuration, region and OS image in the console. We provision the machine; you deploy applications and manage them alongside your other servers.
GET STARTED
From server to running app.
- 01
Add your server
Connect a machine over SSH or order a new VM. The platform installs Docker and an edge agent. The SSH key is used once and is not stored.
- 02
Choose what to deploy
Connect a Git repository, use your Docker Compose file, or discover existing containers. Discovery is read-only until you choose to import a service.
- 03
Manage it from the console
Deploy updates, read container logs and check CPU, memory and disk usage. Applications stay on your server.
What stays on your side
App Servers manage containers. Hardware, capacity and availability of your own machine remain your responsibility.
The hardware and its failures are yours
Disk, memory and network on a connected machine belong to you: if the box dies at your provider, the platform will show it but will not raise a replacement. If you want resilience without being on call, run the app on the platform, where the hardware is ours.
Resources are shared between containers
Every app on one server shares that machine. A heavy build can take CPU away from the service next to it, so a loaded production workload and CI belong on separate servers.
The agent needs outbound access
The edge agent dials out to the platform, so no inbound ports have to be opened. But if outbound traffic is blocked on the server, deploys and telemetry will not work and a firewall rule has to be added.
Docker is required
Apps run as containers. A service that lives as a systemd unit with no image has to be packaged first — the platform does not manage bare processes.
Managed Postgres lives elsewhere
A database as a managed resource is provisioned on platform infrastructure, not on your server. You can run your own Postgres container on the box, but then the backups and upgrades are yours too.
FAQ
Do you keep permanent access to my server?
No. The SSH key is only needed once — to install Docker and the edge agent. After that the platform manages the server through the agent, and the key isn't stored anywhere.
What happens to containers already running on the server?
Discovery lists them read-only. If you choose to import, each service becomes its own application with its own logs and metrics, and data volumes are preserved.
Can I run multiple clients' servers from one panel?
Yes — that's the main agency scenario: each client's server connects separately, and deploys, logs and monitoring all show up in one panel.
Do I have to migrate my server if it already works?
No. You can connect the existing server as-is — nothing to migrate. Or order a fresh VM from us if you'd rather start clean.
More questions
How is this different from a plain VPS?
A VPS gives you a machine and stops there: deploys, logs, metrics and restarts are all yours over SSH. This is the same server, but with deploys from a repository and logs and metrics in the panel — and no home-grown rollout script to maintain.
What happens if the agent loses contact with the platform?
Containers on the server keep running: the agent is there for management and telemetry, not to serve requests. When the link comes back, state resynchronises and nothing has to be restarted by hand.
Can one server host several applications?
Yes. Each service becomes its own managed application with its own environment variables, logs and metrics, while physically sharing one machine and its resources.
What about MySQL or Redis?
The managed engine is PostgreSQL only. MySQL, Redis and anything else runs as a container on your own server and is managed from the same panel as a regular application.