
Dokploy provides a self-hosted way to deploy applications and services on infrastructure you operate. A compatible InCloudServer Linux VPS can provide the server resources, while installation, application configuration and ongoing management remain your responsibility.
Check the published requirements
Dokploy’s installation guide specifies at least 2 GB RAM and 30 GB disk space. It also requires ports 80, 443 and 3000 to be available during installation. Check the current OS compatibility list and installation instructions before provisioning or changing a server.
The listed 1-GB/20-GB InCloudServer VPS falls below both stated memory and disk minimums. A 2-vCPU/4-GB/100-GB tier clears these published resource floors, but builds and application data still need a measured budget.
| Plan | CPU | Memory | Storage | Reference rate |
|---|---|---|---|---|
| Self Managed VPS 2 vCPU 4 GB RAM | 2 vCPU | 4 GB RAM | 100 GB SSD Storage | $27.00 USD / month |
| Self Managed VPS 2 vCPU 8 GB RAM | 2 vCPU | 8 GB RAM | 100 GB SSD Storage | $41.00 USD / month |
| Self Managed VPS 4 vCPU 8 GB RAM | 4 vCPU | 8 GB RAM | 200 GB SSD Storage | $55.00 USD / month |
| Self Managed VPS 4 vCPU 16 GB RAM | 4 vCPU | 16 GB RAM | 200 GB SSD Storage | $68.00 USD / month |
These are resource references, not workload benchmarks. Choose a supported OS and budget for your build, applications and data. Review billing term, amount due and renewal details in checkout.
Protect existing services
Use a fresh server for a first installation. A panel, proxy or other workload already bound to required ports can cause conflicts. Do not stop an existing production website merely to satisfy an installer’s port check.
Confirm the server’s supported distribution, administrative access, DNS and recovery route. Read the official installation commands and understand the privileges they request. Installation commands and port handling can change; use the current linked reference rather than an old copied script.
Install and secure the management interface
- Apply the supported system setup and establish administrator access.
- Run the documented installer only on the intended compatible server.
- Create and secure the administrator account, then configure the management hostname and HTTPS.
- Review which management endpoints must remain reachable and restrict them using the platform’s supported controls.
- Keep repository tokens and application secrets scoped to the services that need them.
Choose an application deployment method
Dokploy supports application and Docker Compose workflows. Choose the one that matches the project rather than forcing a multi-service backend into a static deployment. Define the intended source revision, build command or image, listening port, domain and environment configuration.
For a single Node process, the Node deployment guide explains the essential runtime checks. For a server-rendered React application, use the appropriate Next.js setup only when the repository uses that framework.
Verify services and persistence
Check that the application’s health endpoint works, that its public hostname reaches the correct service and that internal-only services have no unnecessary public ports. Test a user-level operation, an unauthorized operation and a restart. Keep a record of persistent volumes, database locations and external services.
Recreating a container does not recreate its data. Test backups and restore procedures for application state separately from panel configuration. Avoid casually changing the database version or running a destructive migration during a deployment.
Understand the management boundary
Dokploy does not turn an infrastructure purchase into an InCloudServer-managed application service. If application administration is outside your team’s skills, choose appropriate managed hosting or obtain a separately agreed support scope. See the Coolify guide for another deployment-panel approach.
This page checks documented requirements and the listed VPS resources. It does not claim a completed privileged Dokploy installation on a purchased VPS.