Security at Dokploy

Last updated: November 19, 2026

Dokploy is used to deploy and operate production applications and databases, so customers trust us with source code access, server credentials and secrets. This page describes how we protect that data on Dokploy Cloud (app.dokploy.com) and how we build and maintain the open source Dokploy platform.

Questions about this page or our security program can be sent to [email protected].

Architecture and scope

Dokploy is available as self-hosted software and as a managed service, Dokploy Cloud.

  • Dokploy Cloud hosts the control plane: the dashboard, API, database and deployment orchestration. Your applications and databases run on servers you own, which Dokploy Cloud manages over SSH. Application traffic and application data stay on your servers and do not pass through Dokploy's infrastructure.
  • Self-hosted Dokploy runs entirely on infrastructure you control. Dokploy has no access to self-hosted instances, their data or their servers. You are responsible for operating and updating the instance.

Data protection

Encryption in transit

All traffic to dokploy.com and app.dokploy.com is served over HTTPS with TLS. Communication between Dokploy Cloud and your servers uses SSH with key-based authentication.

Encryption at rest

Sensitive values are encrypted at the application layer with AES-256-GCM before they are written to the database, so they are not readable in a database dump. This covers environment variables, build arguments and build secrets, SSH private keys and telemetry provider credentials. User passwords are stored as salted bcrypt hashes and are never stored in plain text. Saved AI provider API keys are never sent back to the browser.

Backups

Dokploy Cloud data is backed up automatically twice a day and backups are retained for 30 days. Deleted data is permanently purged once the backups that contain it expire.

Payment data

Payments are processed by Stripe. Dokploy never receives or stores credit card numbers; we only keep the Stripe customer and subscription identifiers.

Access control

Internal access

Access to Dokploy Cloud production infrastructure is restricted to two members of the engineering team, on a least-privilege basis. Multi-factor authentication is required for every account with production access.

Customer account security

  • Email verification is required to sign up on Dokploy Cloud.
  • Two-factor authentication (TOTP) and passkeys are available on every plan.
  • Users can review their active sessions and revoke any of them.
  • Organizations can control access with built-in roles, and Enterprise customers can create custom roles with resource-level permissions.
  • Enterprise customers can sign in through their identity provider with SSO (OIDC or SAML 2.0) and provision users with SCIM.
  • Audit logs record logins, member and role changes, deployments and configuration changes, and can be exported as CSV or JSON.

See Security, Access Control & Governance for details on these features.

Secure development

Dokploy is open source and developed in public on GitHub, so anyone can inspect the code that runs our product.

  • Every change is merged through a pull request that requires an approving review. Direct pushes and force pushes to the release branches are blocked.
  • Every pull request runs automated build, test and type checking jobs.
  • Dependabot security updates and GitHub secret scanning are enabled on the repository.
  • Security fixes are developed privately and shipped as patch releases, so self-hosted users can update before details are published.

Vulnerability disclosure

We welcome reports from security researchers. Please report vulnerabilities privately through GitHub Security Advisories or by email to [email protected], and do not disclose them publicly until a fix is available. Once a fix is released, we publish a GitHub Security Advisory and credit the reporter unless they prefer to stay anonymous. Our full policy is in SECURITY.md, and past advisories are listed on GitHub.

Incident response

When we become aware of a security incident, we:

  1. Investigate the report and contain the issue.
  2. Fix the root cause and release the fix.
  3. Notify affected customers directly by email, with the actions they should take.
  4. Publish a public security notice on our blog with what happened, a timeline, what we changed and what customers should do, and update it as we learn more.

For an example, see our security notice about AI provider API keys on Dokploy Cloud.

Compliance and privacy

  • SOC 2. We are working toward SOC 2 compliance.
  • GDPR and CCPA. We support data subject rights, including access, correction and deletion. Dokploy Cloud accounts can be deleted at any time from account settings. See our Privacy Policy.
  • Subprocessors. We use a small number of third parties to operate the service, including Stripe (payments), HubSpot (product analytics and communications), Google Analytics (website analytics) and ProfitWell (subscription metrics). The full list and what each one receives is in our Privacy Policy.
  • Contracts. Enterprise customers can request an MSA, SLA and compliance documentation by contacting us.

Related resources