finsys/dockhand

Dockhand - Docker management you will like.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 27 seconds ago
Added to GitGenius on September 10th, 2026
Created on December 28th, 2025
Open Issues & Pull Requests: 365 (+0)
GitHub issues: Enabled
Number of forks: 260
Total Stargazers: 6,177 (+1)
Total Subscribers: 21 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Dockhand is a modern Docker management UI that provides real-time container orchestration, Compose stack deployment, and multi-environment host management through a web interface.

The tool addresses the friction of managing Docker containers and Compose stacks through command-line interfaces by offering a visual management layer. It connects directly to the Docker API to enable real-time monitoring and control of containers across local and remote hosts. The interface includes a visual editor for Docker Compose files, allowing users to define and deploy stacks without manual YAML editing. Git integration with webhook support enables automated stack deployments from repositories. Additional capabilities include interactive terminal access to containers, real-time log streaming, file browsing with upload and download functionality, and authentication via OIDC or local users.

Dockhand suits teams managing multiple Docker environments who want centralized visibility and control without leaving a web browser. It is particularly useful for those already using Docker Compose who want to reduce context-switching between editors and terminals. The project emphasizes security and privacy, running as a self-contained application rather than a cloud service. The tech stack uses SvelteKit for the frontend, Bun as the runtime, and SQLite or PostgreSQL for persistence, making it lightweight enough for small deployments while supporting enterprise features like RBAC through optional licensing.

The project maintains active development with regular commits addressing bug fixes and feature refinements. The codebase shows consistent attention to code quality with meaningful commit messages and organized pull request reviews. Development activity indicates ongoing responsiveness to issues and a structured approach to feature implementation rather than sporadic updates.