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].
Dokploy is available as self-hosted software and as a managed service, Dokploy Cloud.
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.
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.
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.
Payments are processed by Stripe. Dokploy never receives or stores credit card numbers; we only keep the Stripe customer and subscription identifiers.
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.
See Security, Access Control & Governance for details on these features.
Dokploy is open source and developed in public on GitHub, so anyone can inspect the code that runs our product.
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.
When we become aware of a security incident, we:
For an example, see our security notice about AI provider API keys on Dokploy Cloud.