Open source · Ubuntu-first
Self-hosted Ubuntu control panel. GUI-first. No Linux PhD required.
DeployDock is stack-agnostic where it matters and opinionated where it helps. These are representative targets for the deployment guides.
Run on bare metal, VMs, or common providers. The OSS edition focuses on a self-managed Ubuntu model; enterprise docs cover private deployments and air-gap.
Colo, homelab, or internal infra — keep data where your policy requires.
Bring a clean Ubuntu image and follow the installation guides for your tier.
Use roles and templates so developers and operators share the same workflows.
Reduce toil for common paths while preserving access to logs, files, and APIs.
Documented directories, ports, and environment conventions reduce surprises.
Track changes on GitHub and follow the blog for release notes and migrations.
This marketing site is intentionally calm. The docs contain the authoritative detail.
Model repeatable deployments with sensible defaults and reviewable diffs.
Issue and renew certificates with visibility into failures and retry behavior.
Create managed databases and restore points without bespoke scripts.
Jump to logs and health signals from the same place you configure the service.
Placeholder panels for future UI captures.
Follow Quick install for a guided path, or jump to Manual install for advanced setups.
git clone https://github.com/gwalesh/deploy-dock.git && cd deploy-dock corepack enable && corepack prepare pnpm@9.15.0 --activate pnpm install && cp apps/api/.env.example apps/api/.env pnpm --filter @deploydock/api exec prisma migrate deploy pnpm --filter @deploydock/api exec prisma db seed pnpm dev # UI http://127.0.0.1:5173 → /auth/setup first run
Treat the panel like infrastructure: least privilege, audited access, regular updates, and backups you have actually restored.
Separate day-to-day deploy access from destructive maintenance operations.
Document inbound services and keep management interfaces off the public internet.
Prefer short-lived credentials and central rotation over long-lived passwords.
Need private deployments, air-gap packaging, or a support relationship? Start with the enterprise overview and connect from there.
Short quotes from teams evaluating or running DeployDock-style workflows. These are placeholders until we publish verified case studies.
“We wanted a single place to issue certs, attach domains, and hand a project to junior engineers without SSH rituals. This direction feels right for our Ubuntu fleet.”
“Backups that are visible in the same UI as the app cut our mean-time-to-suspicion during incidents. We are still validating restore drills, but the workflow is calmer than ad-hoc scripts.”
“On-prem packaging matters for us. Having enterprise docs that speak to air-gap and private updates makes it easier to get security sign-off.”
No. It is an independent open-source project with different goals and architecture. See the comparison page for a high-level contrast.
Not necessarily. The docs include Docker-oriented workflows alongside native Ubuntu installs so you can choose what matches your operations model.
Start with the troubleshooting matrix, then search the docs. For broader discussion, use GitHub Discussions on the DeployDock repository.
Install on a non-production host, deploy a sample application, and validate backups before you invite a team.