Start Here

1. Install Deku on a Linux server with Docker and root access.
2. Get Started with the dashboard token, your first app, and your first deploy.

Common Guides

• Dashboard Overview covers the web workflows for apps, deploys, routing, and services.
• App templates lists local starter directories you can deploy as-is.
• Architecture explains how the CLI, daemon, dashboard auth, and APIs fit together.
• CLI Reference documents the full deku command surface.
• API Reference points at the live OpenAPI document and Scalar UI.
• deku.toml documents build, deploy, and process configuration.
• AGENTS.md is a copyable coding-agent workflow for operating Deku.

Operations

• Traffic control: maintenance mode and per-path redirects.
• Runtime access: one-off commands and exec into a running container.
• Resource limits: cap memory and CPU per process.
• Backups: on-demand and scheduled datastore backups with retention.
• Diagnostics: deku doctor host checks and log streaming timeouts.

What You Can Do

• App lifecycle: create apps, deploy from source archives or images, inspect deployment history, and roll back.
• Runtime management: manage config vars, domains, port mappings, TLS, process scale, logs, networks, storage mounts, and cron entries.
• Traffic and resources: take an app into maintenance, redirect individual paths, require authentication, and cap memory and CPU.
• Built-in services: provision Postgres, MySQL, MariaDB, Redis, and MongoDB services, link them to apps, and back them up on demand or on a schedule.
• Operational visibility: use deku doctor and the dashboard for app, routing, service, object-store, SSH-key, and plugin workflows.