Why use DeployDock?
In this page
Who it is for
- Teams that want a self-hosted alternative to proprietary panels and are comfortable running Node + Postgres + Redis.
- Operators who value a documented REST API (Swagger) alongside a React UI.
- Contributors extending runtime adapters or installer scripts for their own infrastructure.
What you get
- Single codebase for API, worker, and UI with shared Prisma types.
- Observable defaults: health endpoints, bootstrap status, audit-derived activity feed.
- Docker paths for both dev dependencies and prod-style nginx hosting (
docker-compose.prod.yml).
Honest limitations
DeployDock is early-stage. Many UI actions are still disabled or call APIs that return mock-style data; installer scripts are skeletons. Read the monorepo README Roadmap (phases) and Runtime matrix before betting production workloads on framework-specific automation.
If you need a mature, fully guided installer today, combine Docker Compose from this repo with your own packaging—or wait for Phase 2+ deliverables.