Current product status (Phase 1)
The running deploy-dock stack today ships Phase 1 foundations (see monorepo README): CRUD APIs, partial runtime adapters, queue-backed deploy hooks, and UI areas where some controls are still disabled. Marketing language below describes intent as well as current direction.
Features
DeployDock aims to make routine hosting operations approachable from a graphical control panel while keeping advanced paths available.
What “GUI-first” means here
- Common tasks (domains, TLS, databases, deploys) should not require memorizing file paths or init systems.
- The panel should link out to the right logs, configs, and docs when something fails.
- Automation hooks (CLI, API) should complement the UI, not compete with it. Inbound webhooks are not implemented yet (Webhooks).