---
title: "Deplo vs Dokploy"
description: "Compare Deplo and Dokploy for self-hosted deployment: app builds, Docker Compose, HTTPS, backups and team access on your own servers."
url: "https://deplo.build/comparison/dokploy"
image: "https://deplo.build/api/media/file/og_cover.png"
updated: "2026-10-11"
---

# Deplo vs Dokploy

## No Enterprise tier to unlock.

Custom roles and the activity trail need a licence there. Here they are in the build everyone installs.

[Get started](https://deplo.build/docs/migrations/move-from-dokploy)

[Try the demo](https://demo.deplo.build)

![Deplo dashboard](https://deplo.build/api/media/file/deplo_screenshot-1.png)

## Three things you can't do on Dokploy.

Two are open requests on their tracker. The third is the line in their docs that says Enterprise.

### Roles without a licence key

Custom roles and the audit log are Enterprise there. Here they come with the build everyone installs.

### Environments that can't see each other

On Dokploy every app and database shares one network. Here each environment gets its own.

### One server, every team

On Dokploy a server belongs to one organisation and stays there. Here you pick who deploys on it.

| | Deplo | Dokploy |
| --- | --- | --- |
| **One server, many teams**: Servers are instance-wide. You pick which teams may deploy on each, and they never see each other. | Yes | No |
| **Roles you write yourself**: One capability per action, and roles built out of them. No Enterprise licence. | Yes | Partial |
| **Activity trail in the dashboard**: Who did what, and when, next to the thing it happened to. Included, not licensed. | Yes | Partial |
| **Private network per environment**: Each environment gets its own network. Apps reach their database by name, nothing else does. | Yes | No |
| **Import of your current setup**: A wizard reads your Dokploy over its API and rebuilds it here, volume data included. | Yes | No |
| **Move an app to another server**: Pick the destination and the volumes travel with it. If the copy fails, nothing moves. | Yes | No |
| **Backups encrypted before they leave**: Databases and volumes, encrypted on the machine. The recovery key opens them anywhere. | Yes | Partial |
| **A preview URL for every pull request**: Open a PR and it gets its own URL and environment. Close it and both disappear. | Yes | Yes |
| **MCP server for coding agents**: Off by default. On, an agent works under a token you mint, with the same checks as a person. | Yes | Yes |

## Try Deplo before you leave Dokploy.

Click around a real Deplo on a real server for a few minutes. No email, no password, nothing to migrate yet.

## What you get on day one

Deploys, backups, logs, metrics and TLS, already on. Nothing to buy on top, nothing to hunt down.

### Let AI interact with your infra

Ask, and it's done. Connect Claude, Cursor or any assistant that supports MCP, and it can deploy, read the logs and roll back when you ask in plain words. It works with a key you create and can revoke at any time, and it can never do more than you can. Nothing connects until you create a key, and one switch turns it off for the whole team.

[Learn more](https://deplo.build/use-cases/ai-interact-with-infra)

### Ship on every push

Your whole release process becomes a push. Connect GitHub, GitLab, Bitbucket or Gitea once. Every push to your main branch goes live, every pull request on GitHub gets its own preview link that disappears when it closes, and a bad release goes back to the version that worked.

[Learn more](https://deplo.build/use-cases/ship-on-every-push)

### Control who can do what

Your team works on the same apps without stepping on each other. Give each person exactly the access they need, like "can deploy, can't delete", and hand a freelancer or a client one project and nothing else. The activity timeline shows who did what and when, right in the dashboard.

[Learn more](https://deplo.build/use-cases/control-who-can-do-what)

### Host your Web app

Your app online without touching a setting. Connect the repo and you get a live link, and HTTPS the moment you add your domain. Deplo recognises your framework and builds it for you, and Postgres or Redis sits next to your app in two clicks. Same stack you ran on the cloud. Only the bill changed.

[Learn more](https://deplo.build/use-cases/host-your-web-application)

## Already running on Dokploy?

The wizard reads your Dokploy over its API and rebuilds it here, volume data included.

![Dokploy](https://deplo.build/api/media/file/dokploy-color.svg)

[Read the guide](https://deplo.build/docs/migrations/move-from-dokploy)

## 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.

[Docs](https://deplo.build/docs)

[Get started](https://deplo.build/get-started)

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://deplo.build/#organization",
      "name": "Deplo",
      "url": "https://deplo.build",
      "description": "Deploy apps from Git, Docker images or Compose on your own servers with Deplo. Open source, automatic HTTPS, backups and no per-seat fees.",
      "logo": {
        "@type": "ImageObject",
        "url": "https://deplo.build/api/media/file/og_logo.png",
        "width": 824,
        "height": 824
      },
      "sameAs": [
        "https://ds.deplo.build",
        "https://x.com/deplocloud",
        "https://www.instagram.com/deplocloud",
        "https://github.com/DeploCloud/deplo"
      ]
    },
    {
      "@type": "WebSite",
      "@id": "https://deplo.build/#website",
      "name": "Deplo",
      "url": "https://deplo.build",
      "description": "Deploy apps from Git, Docker images or Compose on your own servers with Deplo. Open source, automatic HTTPS, backups and no per-seat fees.",
      "publisher": {
        "@id": "https://deplo.build/#organization"
      }
    }
  ]
}
```